Documentation UniversalInbox Queue Management

Queue Management

Say when you are available, cap how much each agent carries, and take time off without conversations going unanswered.

On UniversalDesk, service targets, closing, wrap-up and satisfaction come with Business Desk, and there is no Reports page or breach reasons.

Agent status

Each agent picks a status from the inbox header:

  • Available: ready for new conversations.
  • Busy: working, but not taking new conversations. Only you set it; reaching your limit does not.
  • Away: stepped out. It stays until you change it.
  • Offline: not working.

When you close the inbox on every device you show as Offline. Open it again and your last status comes back, so an Away you set before lunch is still Away when you return.

Conversation limits

Each agent has a limit on how many open conversations they are given at once. It starts at 5. The owner and managers change it from the agent's page under Settings → People → Support agents. On Desk the owner sets it on the Teams list under Settings → People → Teams.

A team can set a limit for all its members, and its own limit for one member, for example a lower one for a specialist who also covers another queue. Set both in the inbox settings on the team's page under Settings → People → Teams. On Desk they are on the same page. A member without a limit on the team uses the team's, then their own.

Out of office

Time off is set from Time off in the menu under your name in the dashboard, from the inbox, or on Desk. Owners, managers and admins also find everyone's under Settings → People → Time off. Give it a start, an end if you know it, and a note for your colleagues. You set your own; owners, managers and admins can set anyone's, and a team supervisor can set it for members of their team.

Time off belongs to the person, so it covers both support and lead work. While it lasts:

  • No conversations or leads are handed to you, and you do not count toward your team's capacity.
  • Your status shows Out of office until your return date.
  • Notifications to you, by push and by email, are held back, except a fraud or legal risk alert, which reaches you anyway when no one else who would get it is in.
  • If a flow or channel names you as its default agent or lead owner, the work goes to your team instead.
  • Customers see nothing different. There is no automatic reply.

Hand back my open conversations is on by default. When your time off starts, the conversations you hold go back to their team's queue. Turn it off to keep them; any of them where the customer writes in while you are out goes back to the queue at that moment.

When your time off ends you come back as Offline. Pick your status when you are ready. Conversations that went back to the queue stay with whoever took them.

Handing out conversations

A conversation handed to a team waits in its queue until an agent takes it. Each team chooses how that happens:

  • Push (the default for new teams): handed to the member holding the fewest open conversations, then whoever was last given one the longest ago.
  • Round robin: handed out strictly in turn.
  • Manual: nothing is handed out. Members claim conversations from the queue themselves. Teams created before push assignment was available start on Manual until you change them.

Push and round robin hand a conversation only to a member who is Available, connected, not out of office, and under the limit that team gives them.

There is no accept step: the conversation is theirs at once. A default agent named on the flow or channel gets it first when they are on the team and free: Available, not out of office and under their limit. Otherwise it goes out by the team's own routing.

When nobody can take a conversation it waits, longest waiting first. It goes out the moment someone becomes Available, finishes a conversation, or gets a higher limit. Conversations in a manual team or in no team wait for someone to claim them. Priority, wait limits, escalation and service targets apply to every team, manual ones included.

Conversations from Intercom keep Intercom's own assignment and are never handed out here, unless the Intercom deployment's handoff strategy is Universal Inbox Queue. Then they are handed out like any other channel's, and Intercom shows whoever has them. Someone working in Intercom can still take one there; the inbox follows that change, and it counts toward their limit.

Declining

An agent can decline a conversation handed to them, with an optional reason. It goes to the next agent who can take it, keeping its place in line, and never comes back to the agent who declined. Declines appear in reporting.

Claiming or assigned only

By default members can also claim conversations from their team's queue. Set a push or round robin team to Assigned only and its members take only what is handed to them; they cannot claim, or pick up an unheld conversation by replying to it. Owners, managers and admins can still claim and reassign.

Priority

Each conversation has a priority: Low, Normal (the default), High or Urgent. Waiting conversations are handed out highest priority first, then longest waiting. The inbox list marks low, high and urgent conversations with an icon.

Priority is set by:

  • The Priority setting on the Assign Support node, for example in a trigger that routes each handoff.
  • Marking a contact VIP. Their conversations are High or above, including the ones open when you mark them.
  • Owners, managers and admins, from the conversation in the dashboard or the inbox.

Supervisors

Any member of a team can be made its supervisor, on the team's page. A supervisor leads the team in everything it works on, leads and Social included. Within their teams, supervisors get escalation alerts, reassign conversations, claim from an assigned-only queue, set priority, and set time off for the members of their teams who are not owners, managers or admins. Owners, managers and admins can do all of this in every team.

Supervisors come with the UniversalChatbot Business plan. UniversalDesk has no supervisors. On other plans and on Desk, a team's alerts go to the workspace's owners, managers and admins who hold a support seat.

Business hours

Each team has a weekly schedule in its own time zone, written one line per set of days, such as Mon-Fri 09:00-17:00. Leave it empty and the team is always open. Add holidays, one date per line with an optional name, to close the team all day.

Outside business hours decides what a visitor gets when the flow reaches a handoff while the team is closed:

  • Hand over and hold in the queue until the team opens: the visitor gets the team's held message in place of the handoff message, and waits in the queue. The bot stops answering, and the conversation is handed out once the team opens.
  • Let the bot keep answering instead of handing over: no handoff happens. The visitor gets the team's bot keeps answering message in place of the handoff message, and their next message carries on with the flow. The conversation is tagged Asked for a person after hours, so agents can filter the inbox by that tag and follow up once the team is back. Nothing is handed over automatically when the team opens.

Either way the visitor gets one message. A visitor who keeps writing while held gets no further replies, and when the team opens nothing is sent automatically: agents pick the conversation up from the queue. UniversalDesk has no bot, so its teams always hold.

After-hours messages

Each team has two optional messages. Leave either empty to use the default, which says when the team opens again:

  • Held message: "We're closed until Monday at 9:00 AM WAT. We've passed your message on and someone will reply here when we're back." On UniversalDesk it is "Thanks for your message. We're closed until Monday at 9:00 AM WAT and will reply here as soon as we're back."
  • Bot keeps answering message: "Our team is offline until Monday at 9:00 AM WAT. I can keep helping until then, so tell me what you need."

Your own text can include these placeholders, filled in from the team's business hours and time zone:

  • {{opening_time}}: when the team next opens, such as 9:00 AM WAT later today, tomorrow at 9:00 AM WAT, Monday at 9:00 AM WAT within the week, or Monday 26 October at 9:00 AM WAT further ahead. It reads well after "until". Times always name the team's time zone, so a visitor elsewhere can tell when that is.
  • {{closing_time}}: when the team closes again after it opens, such as 5:00 PM WAT. Hours that run past midnight close when they end the next day.
  • {{team_name}}: the team's name.

Anything else in double braces is sent as typed. Intercom conversations follow Intercom's own routing unless their deployment uses the Universal Inbox Queue strategy. There, a conversation the bot keeps answering after hours also gets an Intercom tag, ucb-handoff-requested unless the deployment names its own.

Wait limit and escalation

A team can set a wait limit in minutes, counted in business hours. A conversation still waiting for an agent then escalates:

  • At the limit, the team's supervisors are alerted. If none is in, the workspace's owners, managers and admins are.
  • At twice the limit, it moves to the team's overflow team, if one is chosen, keeping its place in line. Overflow comes with the UniversalChatbot Business plan, and UniversalDesk does not have it.
  • With Raise priority at each escalation on, each step also raises its priority one level.

Each step happens once for each wait. A conversation that goes back to the queue later starts a new wait.

Service targets

On the Pro and Business plans, each team can set service targets for each priority, in minutes, counted in the team's business hours or around the clock:

  • First response: from the handoff to the first agent reply. When no bot answered first, it counts from the customer's first message.
  • Next response: from each later customer message to the next agent reply.
  • Resolution: from the handoff to the close.

Time the bot spends with the customer never counts. Moving a conversation to another team keeps the time already run and switches to that team's targets. Reopening a conversation picks its resolution time up where it stopped.

Each conversation in the list shows its most pressing target as a countdown that turns amber at 75% and red once missed. At 75% the agent holding it is nudged; once missed, the team's supervisors are alerted, and the team can choose to raise its priority or move it to the overflow team. Every missed target is recorded with the time it ran out. Everyone in the inbox can open the Breaching soon list to see which of the conversations they can see need attention first; a snoozed conversation stays off it until it wakes.

Waiting on customer

Mark a conversation Waiting on customer when you have asked them something. Its resolution time pauses, and it goes back to open as soon as the customer writes. Snoozing does not pause it.

Only the agent handling a conversation, or a supervisor of its team, can mark it waiting on the customer. Owners, managers and admins count as supervisors of every team. It has to be held by an agent first: a conversation the bot is answering cannot wait on the customer.

Marking it adds a note to the thread with your name. The thread also notes how the wait ended: the customer replied, someone reopened or snoozed it, or the bot took the conversation back. Handing a waiting conversation back to the bot reopens it. If the agent handling it lets it go, the wait ends and the conversation goes back to the team's queue. Closing it ends the wait with no extra note, since the close already shows in the thread.

A team can set Remind after (days) in its inbox settings, from 1 to 3 days. It is off until you set it. Marking a conversation waiting on the customer counts as activity, and a conversation with no activity for 7 days closes on its own, so both reminders fall due before that. Once a conversation has waited that many days, the agent handling it is reminded; after twice as long, the team's supervisors are reminded too, or the workspace's owners, managers and admins when the team has no supervisor in. Each reminder goes once for each wait, and one that reaches nobody, such as while the agent handling it is out of office, is sent once someone can receive it. Someone due both reminders at once gets one. Anyone can turn these off with Conversations still waiting on the customer in their notification settings.

The wallboard shows how many of each team's conversations are waiting on the customer and how long the oldest has waited, and each agent's load says how many of theirs are waiting. The Waiting on customer report counts how often conversations were marked, how the waits ended and how long they ran.

Closing and dispositions

On the Pro and Business plans, owners, managers and admins keep two lists for the workspace: dispositions, how a conversation ended (such as Refund issued or Answered), and breach reasons, why one missed a service target, which come with the Business plan. On Desk the owner keeps these lists under Settings → Support → Dispositions and tags. Each team chooses which dispositions apply to it, or offers them all, and whether closing asks for one:

  • No: closing asks nothing.
  • Optional: the close sheet offers a disposition and a note.
  • Required: a disposition must be chosen, and a breach reason too when the conversation missed a target.

You can close several conversations at once only when they all get the same disposition. Closes nobody made, when a conversation expires, the bot finishes it, or it is closed in Intercom, ask nothing and show as Closed automatically or Closed in Intercom; anyone on the team can add the disposition afterwards. Once a disposition is given, the person who closed it and the team's supervisors can change it.

Reopening and closing again records a new close. Reports use the latest one.

Wrap-up

On the Pro and Business plans, a team can give its agents a wrap-up window, in seconds, after each close. Until it passes or the agent presses Done, the closed conversation still counts toward their limit, so no new one is handed to them while they finish their notes. The time counts as handling time in reports.

Reports

On the Pro and Business plans, Reports under Support shows how the queue is doing over any date range, by team, agent, channel, priority, flow or deployment. Owners, managers and admins see the whole workspace; supervisors see their own teams. Each report downloads as CSV.

  • Volumes: conversations that reached a queue, how many closed, and how many are still open.
  • Waiting and queue time: how long conversations waited for their first agent, and how many wait now.
  • Handling time: from first assignment to close, with wrap-up time shown and included in the total.
  • Service target attainment: the share of first response, next response and resolution targets met.
  • Missed targets: breaches by target, with the breach reasons agents gave.
  • Dispositions: how closed conversations ended, from each one's latest close.
  • Declines: conversations agents turned down, and how many gave a reason.
  • Waiting on customer: how many times conversations were marked waiting on the customer, how many of those waits ended with the customer replying or with a close, the median and longest wait in hours, and how many are still waiting. By agent, a wait counts for whoever marked it.
  • Availability: hours in each status. Out-of-office time is left out of the availability share.
  • Satisfaction (Pro and Business plans): customer ratings, how many were satisfied, neutral and unsatisfied, CSAT, and the share of surveys answered. See Customer satisfaction.
  • Sentiment: the share of each mood before conversations closed and when they closed, and how many ended better or worse than they were before. The handoff columns count each conversation once, from its latest reading at a handoff or by a Conversation Insights step in your flow. The close columns count each conversation's latest close. By agent, only the close columns are filled in, since an agent is judged on how their conversations ended.
  • Issues: how many conversations each issue tag was found on, at a handoff, at close or by a flow step, with the customer's mood when it was last found.
  • Risks: how many conversations each risk was raised on, at a handoff, at close or by a flow step, with the emotion that stood out when it was last raised. A conversation counts once per risk, however often it is raised. See Mood and risks.

Sentiment, Issues and Risks fill from Insights and the Conversation Insights step. Insights at handoff feeds the handoff columns of Sentiment, and Issues and Risks. Insights at close feeds the close columns of Sentiment, the share that got better or worse, and Issues and Risks. A Conversation Insights step that saves to the conversation counts like a handoff. While no deployment has either switch on, these reports say so instead of showing an empty table.

Wallboard

The Wallboard shows the support floor as it is right now. In the dashboard it is under Support; on Desk it is in the sidebar on Business Desk. Owners, managers and admins see every team, plus conversations waiting with no team. In UniversalChatbot, supervisors see the teams they supervise. Other agents do not see it. Pick a team at the top to show only that one.

  • Teams: for each team, how many conversations are waiting and the longest wait. The wait shows the real time the customer has waited, but it turns amber at 75% of the team's wait limit and red past it counting only the team's business hours, the same way the wait alerts count, so a conversation left overnight is not red when the team opens. Each team also shows whether it is open and when that changes, how many agents are available, busy, away or offline, how many conversations are at risk of missing a service target or have missed one, and today's figures: conversations closed (by agents or automatically), average wait, the share of service targets met and targets missed. Today starts at midnight in the team's time zone. When any of a team's conversations are waiting on the customer, the tile shows how many and how long the oldest has waited.
  • Agents: each agent on those teams with their status, how long they have been in it, how many conversations they hold against their limit, how many of those are waiting on the customer, and their teams.
  • SLA risk: the conversations closest to missing a target, or already past one, with their team, the agent holding them and the time left. A conversation counts as missed once a target that is still running is missed, and stays listed while it is open. While you wait on the customer its paused target leaves the board, and the conversation comes back when that target runs again. A snoozed conversation leaves the board until it wakes. The 25 most urgent are listed, with a link to the rest.

The board refreshes every 10 seconds; today's figures can be up to a minute behind. For a screen on the wall, TV view shows the board without the rest of the page, with a Full screen button.

Talk to sales
This form is running on UniversalChatbot.