Desk can do the routine work for you. Open Desk settings → Automation to set it up. Everything here needs the owner or an administrator of the workspace.
Automation rules
A rule says when it runs, which conversations it is about and what it does.
When a rule runs
| Event | Runs when |
|---|---|
| A conversation starts | The first message arrives. It runs once per conversation. |
| A customer writes | The customer sends a message, the first one included. Your replies and private notes do not count. |
| A conversation changes | The status, priority, assignee, queue or labels change. |
| A resolved conversation is reopened | A resolved conversation is open or pending again, for example because the customer wrote back. |
Which conversations
Add conditions to narrow a rule down. Each one looks at one thing:
- Channel, Status and Priority - pick from the list.
- Label, Assignee and Queue - is one of these, is not, is set or is not set.
- Subject, Message text and Sender email - contains, does not contain, is, is not. Type several words separated by commas to match any of them. Text is compared without regard to upper or lower case.
- Sender domain - for example
acme.example. - Custom attributes - any custom attribute of the conversation or the customer, with checks that fit its type (greater than for numbers, before and after for dates).
Choose whether all conditions must hold or any one of them. A rule with no conditions applies to every conversation. The same conditions are available in routing rules.
What a rule does
Actions run in the order you list them, each kind once:
- Assign to a teammate or unassign, and Move to a queue (the conversation goes to the next available agent of that queue).
- Add labels or Remove labels.
- Set status, Set priority or Snooze.
- Add a private note and Send a reply. Both can use placeholders such as
{{contact.first_name}}. They are written as the person who created the rule (or the assignee, or the owner if that person has left), and show an "Automatic" badge. A reply needs an address to write to; without one it is skipped and the log says so. - Notify teammates by email, with an optional message and a link to the conversation.
- Send to a webhook - posts the conversation as JSON to an address you choose. Add a signing secret and every request carries an
X-Formspring-Signatureheader (t=<unix time>,v1=<signature>), the same way other Formspring webhooks are signed. Only public addresses are allowed.
One action that cannot be done is skipped and never stops the others.
Waiting before acting
Under Wait before running, choose a delay from 5 minutes to a week. When the wait is over the conditions are checked again, so a conversation that someone picked up in the meantime is left alone. That makes "if nobody has taken it after 30 minutes, assign it to Ben" work.
Staying out of loops
- Whatever a rule changes never starts another rule.
- Tick Once per conversation and a rule never runs twice on the same conversation.
- Whatever else happens, a rule stops after five runs on one conversation within ten minutes, and the log says why.
The log
The Recent activity list shows every run for the last 30 days: when, which rule, which conversation, what it did, what it skipped and why, and runs that are still waiting. Each run also leaves a line in the conversation ("Automation ran the rule ..."), followed by a line for every change.
Resolve quiet conversations
Under Resolve conversations by themselves, choose a number of days. A conversation that has had no activity for that long is resolved. Optionally:
- Send a closing message to the customer as it is resolved, for example "Just write back if you still need help."
- Add a label so you can find what was closed automatically.
By default only conversations your team has already answered are closed, so a customer who is still waiting for you is never closed on. Untick that to close those too. A customer who writes again reopens the conversation. Snoozed conversations are left alone.
Waiting conversations go to free agents
A queue can limit how many open conversations one agent holds. When everyone in a queue is full or away, new conversations wait in the queue unassigned. They are handed out, oldest first, as soon as an agent has room again: when one closes a conversation, when someone returns from being away, and every few minutes as a safety net. A round-robin routing rule can have its own Open limit per agent too.
Merge conversations
When a customer writes twice about the same thing, or on two channels, merge the two conversations. Open the one you want to get rid of and click Merge in its header (or press Cmd/Ctrl + K and choose Merge into another conversation), then pick the conversation that should keep everything.
- The messages move over in time order and say which conversation they came from.
- Both conversations get a line saying what happened.
- Labels and followers are combined, the higher priority is kept, and a resolved conversation is reopened if the customer was still waiting in the other one.
- The merged conversation shows as resolved, leaves your lists and counts, and no longer has a service-level clock. Opening it, or answering it, goes to the conversation you kept. A reply from the customer to any earlier email lands in the kept conversation. A first reply already given counts for the kept conversation.
- Only conversations with the same customer (the same contact or reply address) and in the same project can be merged. A live chat can be the one you keep, but not the one that is merged away.
- Merging cannot be undone.
Search what was said
The search box in the conversation list looks through the subject, the customer's address and the text of every message and private note. Every word has to appear somewhere in the conversation; put words in "quotes" to keep them together. A matching conversation shows a short excerpt of the message that matched.
