DeskDay to day
My queue and all conversations
The left rail has My queue and All conversations. My queue holds what needs you now; All conversations is for the whole team's conversations, with search and filters.
My queue #
The queue has two parts: Customer waiting and Ongoing. It holds:
- conversations you are serving;
- conversations transferred to you and waiting for you;
- transfers in the team queue that are not assigned to anyone yet;
- conversations to follow up: a transfer nobody picked up, or a request made while nobody was online. Any teammate can take these;
- "Ailo asks you": the ones nobody has taken, and the ones you hold.
Customers who are waiting come first, follow-ups first among them, then by how long the customer has waited, longest first.
Press J for the next conversation and K for the previous one. Press ⌘/ (Ctrl+/ on Windows) for all keyboard shortcuts.
When the queue is empty, the page says "No one is waiting" and lists Assist tickets in the pool and conversations where Ailo is serving, up to 3 of each. Opening one only shows it; it does not claim anything.
Ailo asks you #
When Ailo is not confident enough about a reply, it holds the reply and asks the team in the queue: "Can this reply go to {name}?" The first teammate to respond handles it:
| Button | Result |
|---|---|
| Approve | Sends Ailo's draft as it is |
| Edit & send | Sends your edited version |
| Give the answer | Sends a reply you write yourself; you serve after sending |
| Start serving | Drops the draft and you take over the conversation; works only when held |
If the customer writes again in the meantime, the draft is out of date: the card no longer offers Approve and shows Discard instead.
Auto-send on timeout #
An organization can have an unanswered "Ailo asks you" send itself after 30, 60 or 120 seconds. It is off by default. When it is on, the card shows "Auto-sends in {time}". It never auto-sends when:
- who serves has changed, or the site has turned Ailo off;
- the customer wrote again, or a teammate has already taken it;
- the reply has a number that was not verified;
- Ailo's confidence is too low;
- it involves an action that changes data, or a promise about time, money or an outcome.
For now an admin sets this through Orbit or the CLI (ailo settings handoff --auto-send); Desk settings do not have it yet.
How new conversations reach you #
When a site has Ailo on, new conversations go to Ailo first and reach the team queue only when Ailo transfers. When assigning to teammates:
- only teammates who are online and below their limit get new conversations;
- each person serves up to 3 conversations at once by default, which you can change under Serving capacity in Settings › My account;
- when loads are equal, the person who has gone longest without a new conversation gets it.
Your status is in the avatar menu: Online, Focus on tickets or Away.
All conversations #
All conversations has three parts: For you, Needs support and All.
- Needs support holds what the team has to follow up on: follow-ups, transfers waiting to be picked up, customers waiting, "Ailo asks you", and conversations with an assist ticket that is not done.
- Each row shows how long the customer has waited, or the last activity when they are not waiting. Waiting starts when the customer asks for a transfer and still counts after a teammate starts serving, until their first public reply.
- The list loads 50 at a time and loads more when you scroll to the end.
Search and filters #
Press / to search customers, messages or IDs.
Filter narrows by time, who served, outcome (Done, Answered, Unresolved, No action needed) and customer rating. More filters lets you pick one state: Ailo serving, Specialist serving, Waiting, Follow up and Ended.
Related #
Admins can set each member's capacity in Settings › Members and the site default in Settings › Routing. Members without their own setting follow the site default.