Appearance
Escalation
Escalation hands a conversation to a named person or team in your help desk when a rule matches, or after Overdesk sends a reply that passes the customer's question on or says they will hear back, with a note on the conversation saying why. The right person finds the conversation already in their queue, with the draft and the reason beside it. Apart from sending replies, which your workspace turns on separately, it is the one part of guardrails that changes anything in your help desk, and all it changes is who owns the conversation.
What happens when a rule hands over
When a rule with a target under Hand over to matches a new draft:
- The conversation gets a note naming the target and giving the rule's reason, such as "Escalate to Billing team. Billing questions always go to a person." When the rule escalates because the reviewer found the draft does not fully answer the customer, the reason also says what is missing and the one check that would settle it, such as a test on the test site, a file in your product's code, or a fact only the customer can give. With note delivery, that line sits at the top of the draft note. With draft replies, Overdesk posts it as a separate note headed "Overdesk escalation", because anything in the composer would go to the customer.
- Overdesk assigns the conversation to the target, using who you chose for the target on that conversation's help desk. The note always comes first, and if it cannot be posted, nothing is assigned.
- An alert titled "Handed to" the target's name, with the conversation number, appears on Alerts and goes to wherever you send alerts. See Alerts. When nothing is being assigned, because the target has nobody chosen on that help desk or the conversation already has an owner, the alert is titled "Escalate to" the target's name instead.
Overdesk never takes a conversation away from someone who already owns it. If it has an owner, the note still names the target and the alert still fires, but the assignment is left as it is. On Zendesk, a ticket counts as owned when it has an assignee. On Intercom, a reply assigns the conversation to whoever sent it, so the teammate your access token belongs to is not counted as its owner when only a reply from Overdesk put them there.
When a sent reply makes a promise
With sending on, a reply that tells the customer their question was passed on, or that they will hear back, can be sent, and Overdesk then hands the conversation to the person who has to keep that promise. It goes out only when every other check on Sending passes, and when:
- its only promises are passing the question on, or that the customer will hear back or be followed up, with or without a day. A reply that also promises a fix, a change or an outcome, says something was done that the conversation doesn't show, makes the promise wait on a condition ("if it still fails, I'll pass this on", "send me the link and I'll check", "otherwise, our developers will get back to you"), asks for a way into the customer's site or accounts or for a secret such as a token, or offers to look at their site waits for your team. For a reply written in English, Overdesk also checks for the condition, the way in, the secret and the offer itself, and a secret named anywhere in the reply, even in a how-to step, holds it, though not a word that names no secret there, such as clearing cookies, a cookie banner or blurring a token out of a screenshot;
- each sentence Overdesk reads as saying what someone will do, is doing or has done, when, or what the customer will get is worded as one of the plain promises Overdesk knows: passing the question on, that the customer will hear back, or that someone will check in with them. Such a sentence worded any other way, money mentioned outside the promise, a secret named anywhere, or a question to the customer beside it keeps the reply for your team. So does another language when Overdesk spots it: one of its common words, or three or more words between two punctuation marks with no common English word among them, not counting capitalised words after the first, which read as names. Overdesk does not spot every language this way. Overdesk reads the reply as written and again as the customer will see it, and either reading can hold it;
- it answers everything else the customer asked. A part answered with a guess, or one the writer says they will look into or find out themselves ("I'll look into whether that works and get back to you"), is not answered: only a part passed to your team counts. For a reply written in English, Overdesk also looks for such a part itself and holds the reply when it finds one. A reply that can answer none of it goes out only when it says the question was passed on, never just to say the writer will get back to the customer, and, written in English, never when it mentions money or an entitlement;
- someone can be handed the promise. A reply whose only promise hands the question to one of your targets goes to that target; "the team" or "our team" alone names none. Any other reply goes to the first person ticked Keeps the promises replies make, and waits for your team until someone is ticked. Such a reply written in English also waits when it mentions money or an entitlement anywhere, even outside the promise: a refund, a credit, a discount, a price, a payment, an invoice, a licence, a renewal, a subscription, a trial, an upgrade or a cancellation;
- that target is a person, with someone chosen under Assign to for the help desk the conversation is on;
- nobody else owns the conversation, before drafting or since.
To choose who keeps these promises, tick Keeps the promises replies make on their target and press Save targets. Only a person with someone chosen under Assign to can be ticked. On each help desk, the promise goes to the first person ticked who has someone chosen for that help desk.
The promise goes out in Overdesk's words, not the reply's. Overdesk sends the reply exactly as written up to where its first promise starts, so the greeting and any answer before it are kept, and in place of the rest one fixed sentence:
- "I've passed your question to our team, and Dana will get back to you." when the reply handed the question to one of your targets and called that person by their first name, spelled as on your targets (one with a hyphen or an apostrophe, such as Anne-Marie, keeps the reply for your team). A reply that named the team, or the person only by another name, says "I've passed this on to our team, and they will get back to you." instead, and one whose promise names anyone else on your targets waits for your team;
- "I've passed this on to our team.", "Our team will get back to you." or "I've passed this on to our team, and they will get back to you." when it passed the question on, said the customer will hear back, or both;
- "We'll check in with you to see how it went." when it said someone will check in to see how things went. A check-in beside any other promise, or in a reply handed to one of your targets, waits for your team, and one that owes the customer an answer ("I'll check back with you with an answer") gets "Our team will get back to you."
A day the reply named is not sent. What follows the first promise may be only promises, an apology, thanks, a hope that it helps, being glad to help, an offer to answer more questions, and a sign-off; your help desk adds your signature. Anything else after it, such as another answer, a recommendation, or a promise inside a list, a quote or a table, keeps the reply for your team. Overdesk reads the answer before the promise too: a promise, a question, money, a secret, a fix ("If you have any other questions while we fix this…") or words asking for someone's personal details, such as "your phone number", keep the reply for your team, and so does a link whose title, # part or email subject would show your customer words the reply doesn't. Overdesk knows these by their common wordings, not every wording, and reads the words that name a detail, not the detail itself. The answer before the promise is the reply's own words, and the review checks it as it checks any answer. A reply kept for your team keeps its own words on Agent drafts; one Overdesk sent, or may have sent, shows there as it was sent.
After the reply goes out, Overdesk hands the conversation over as a rule does: a note headed "Overdesk escalation", the assignment, and a "Handed to" alert. For a reply that hands the question to one of your targets, the note says the reply told the customer their question was passed on. For any other, it quotes the sentence the customer was told, word for word, so the person knows what they have to keep; the alert never quotes it. The reply leaves the conversation in your team's queue, whatever you chose under After Overdesk sends a reply, because your team owes the customer the next step: Active on Help Scout and FreeScout, Open on Zendesk, and open on Intercom. On Intercom the reply itself first assigns the conversation to the teammate your access token belongs to, and Overdesk then assigns it on to the person who keeps the promise. If the note or the assignment fails after the reply has gone out, the alert is titled "Needs a human" and says the hand-over did not finish. The same alert comes when someone takes the conversation in the moments after the reply goes out (they keep it), and when your help desk does not confirm the reply was sent.
Any other reply with a promise waits for your team as before.
When a reply asks for access to a site
Overdesk never logs in to a customer's site, and never sends a reply that asks for a way in. A reply that asks the customer for access, such as their login details, a temporary login link, a temporary admin user or a collaborator request, or that says the writer will log in to their site or store, always waits for your team.
Overdesk writes these replies the safe way. It never asks for login details in the ticket. On WordPress it asks for a temporary login link from a temporary-login plugin, or a temporary admin user the customer deletes afterwards. On Shopify it says your team will send a collaborator request for the store owner to approve. It says what will be checked and that access is removed afterwards, and if the customer already sent their login details, it suggests they change them once the work is done.
To hand these replies to whoever does the logging in, tick Logs in to customer sites on their target and press Save targets. The first person ticked who has someone chosen for the conversation's help desk gets each one: a note headed "Overdesk escalation" saying the reply asks for access and is waiting for them to review and send it, then the assignment. Overdesk then sends nothing more in the conversation until the issue is resolved, as with any hand-over. This hand-over raises no alert of its own; your help desk tells the person it was assigned to.
The reply waits on Agent drafts without being handed to anyone when:
- a rule already handed the conversation to one of its own targets, which keeps it;
- someone else owns the conversation;
- nobody ticked has someone chosen for that conversation's help desk;
- only Overdesk's reviewer recognised the request, such as one written in another language. It is still held.
Only a person with someone chosen under Assign to can be ticked.
When a customer posts a login link
A customer sometimes posts a link that logs in to their site, such as a temporary login link from a temporary-login plugin, a WordPress reset link or a magic login link. Overdesk hides the link's secret from everything it stores, from the model and from its logs, in the shapes it recognises (see How customer data is handled), and sends no reply in that conversation on its own until a reply from your team has reached the customer. An automatic reply from your help desk, such as a workflow's or a trigger's, does not count. The draft shows on Decisions as Customer posted a login link, and no rule can send it.
The conversation goes to the person ticked under Logs in to customer sites, the same way and on the same conditions as a reply that asks for access, with a note headed "Overdesk escalation" saying the customer posted a link that logs in to their site. Overdesk writes the draft to tell the customer the link was hidden from its records and that a teammate will take it from here, and to ask them to revoke the link once your team confirms it is done. When the conversation can't go to them, because nobody ticked has someone chosen for the conversation's help desk, someone else already has it, or the help desk can't assign conversations, the draft asks the customer to revoke it now.
Overdesk also raises an alert titled "Login link posted", whether or not sending is on, naming the person ticked under Logs in to customer sites who has the conversation, if one does. It is raised once until it is acknowledged. A link posted before the last reply from your team that reached the customer, or quoted from an earlier message in a later one, does not hold a reply or raise an alert again.
While a conversation is with your team
Once a rule, a sent reply, a reply asking for access or a customer's login link hands a conversation to a person or team, Overdesk sends nothing more in it until that issue is resolved, even with sending on. This holds whether or not it could assign the conversation, including when someone already owned it. It keeps drafting each new customer message, so whoever holds the conversation still finds a draft waiting.
Before each later reply, Overdesk's reviewer reads what your team has written since the hand-over and who holds the conversation now, and decides whether the issue has been dealt with. A reply Overdesk sent itself never counts as your team dealing with it. When your help desk didn't confirm a reply Overdesk sent, the reviewer isn't asked at all until someone on your team adds a note or replies in your help desk (on Intercom, only a note counts). A reply in the first 30 minutes after it doesn't count, because it could be Overdesk's own, and neither does a note or automatic reply from a workflow or another app. Until it says yes, Overdesk holds; when it cannot tell, it holds too. It reads everything written since the hand-over or nothing: when more has been written than it reads at once, it cannot tell, and the conversation stays with the person who has it. Once the issue is resolved, the conversation is back to normal and a reply your rules approve can be sent again. A new hand-over starts the wait again. See Sending.
What each help desk can assign
| Help desk | Can be handed to |
|---|---|
| Help Scout | People and teams |
| Zendesk | Agents and groups |
| Intercom | Teammates and teams |
| FreeScout | People. FreeScout has no teams, so a team is only named on the note there |
A target has its own Assign to for each help desk you connect, and a conversation is only ever assigned to who you chose on its own help desk. A target with nobody chosen for that help desk is still named on the note, and nothing is assigned.
Set up a target
- Open Guardrails → Escalation.
- Press Add target.
- Enter a Name. This is what your team reads on the note and in the alert, so use the name they know, such as "Billing team".
- Set Kind to Person or Team. The lists below offer only people or only teams to match, because a person's ID and a team's ID are different numbers, and changing Kind clears the IDs already chosen.
- There is one Assign to for each help desk you have connected. In each, pick the person or team from the list Overdesk reads from that help desk. If the one you want is missing, choose Someone else, enter an ID and type their ID from that help desk. When a help desk's list could not be read just now, the tab says so and you type the ID. Choose Do not assign if you want the note to name the target without assigning anything there.
- Press Save targets.
- Open the Rules tab, choose the target under Hand over to on each rule that should use it, and press Save changes.
A target receives nothing until a switched-on rule points at it, or until it is ticked under Logs in to customer sites or Keeps the promises replies make (see When a reply asks for access to a site). The Escalation tab warns you when none does, and under each target it lists the rules that hand conversations to it.
You can keep up to 20 targets. Only admins can change them. Renaming a target later keeps every rule that points at it working.
Rules without a target
Under Hand over to, a rule that holds a draft back offers two ways of choosing nobody, and they do different things:
- Nobody assigns nothing and raises no alert. The draft waits on Agent drafts with its badge, and the decision is in the log. Every starter rule ships this way.
- Nobody, just alert the team assigns nothing but raises an alert on every draft the rule matches, titled "Needs a human" with the conversation number.
A rule under Escalate when alerts by itself, so it offers only the second: an escalation always tells someone.
If you delete a target that a rule points at, that rule falls back to alerting only. It never guesses at someone else.
Be careful with broad rules
A rule that matches much of your queue hands much of your queue to whoever you pick. Before pointing a rule at a person, check how many drafts it decided in the last 30 days, shown under the rule on the Rules tab. Narrow rules such as Bug reports or Refunds and cancellations make better hand-offs: "bug reports go to engineering" is the kind of routing escalation handles well.