Before you start
Before you start, sign in to the dashboard and select the organization you want to work in.- You need a live-chat seat. See Live-chat overview and seats.
- Assignment strategy, timing, and working hours are Admin settings on each inbox. See Set up inboxes.
- Manual assignment of other human agents is Admin-only. Every seat holder can take over an unassigned conversation or reassign one to themselves.
Set your availability
Your availability control sits at the bottom of the views rail in Conversations, above Notifications and Settings. It shows a colored dot and your current status label.1
Select your status label at the bottom of the views rail
A menu opens with Online, Busy, and Offline.
2
Choose Online or Offline
The change applies immediately and the menu closes.
3
For Busy, pick a duration
Selecting Busy expands four options: Indefinitely, For 15 minutes, For 30 minutes, or For 1 hour.
While a Busy timer runs, the label shows the time left, for example Busy · 12m left. When the timer ends, your status returns to Online on its own.
Set auto offline
The menu ends with a Set auto offline switch. Its tooltip reads “Let the system automatically mark you offline when you aren’t using the dashboard.” The switch is on by default. With the switch on, closing the dashboard marks you offline, and opening it again restores your chosen status. With the switch off, your status stays exactly as you set it, even when the dashboard is closed. Turn it off only if you want to stay assignable while you work in another tool.How automatic assignment picks a human agent
Automatic assignment runs when an agent hands a conversation to live chat, for example through a Live Chat gambit or an AI Agent handoff. It only considers human agents who pass every one of these checks:- They hold a live-chat seat.
- They are a member of the inbox that owns the conversation.
- Their status is Online.
- They are below their conversation capacity. The cap is 30 open conversations per human agent. It is fixed, and no dashboard setting changes it.
An Admin sets the default Strategy on the inbox’s Routing tab. A Live Chat gambit can override it in the builder. Its Assignment section has its own Assignment Strategy select and an Allowed Agents picker that restricts assignment to specific human agents. The Priority select there stamps the conversation without changing who gets it.
The end user sees an Assigned to Alex Morgan system chip in the thread when assignment succeeds. The assigned human agent gets an Assignment notification. See Live chat notifications.
When nobody is available
If no human agent passes the checks, the conversation is parked as unassigned and waits for a human. The end user sees a notice in the thread. Tars picks the first of these that exists:- The inbox’s Out-of-hours message, only when the handoff happens outside the inbox’s working hours.
- The Live Chat gambit’s No Agents Available message.
- A default notice that says no agents are available right now and the team will get back shortly.
Find parked conversations
Parked conversations appear in two places in Conversations:
To take one, open it and select Take over conversation under the thread. The conversation moves to your Mine tab and the composer unlocks. See Work the inbox for the queue tabs and views.
Outside working hours
Working hours are set per inbox on the Availability tab, in your organization’s timezone. When Enable working hours is off, the inbox counts as open around the clock. When a Live Chat gambit hands off outside working hours, Tars does not look for a human agent at all. The end user sees the Out-of-hours message, and the conversation is parked as unassigned. It stays in the Unattended view and the Unassigned tab until a human agent takes it over, or until the inactivity timeout marks it abandoned. If the gambit’s No Agents exit is connected, the flow continues there instead of parking the conversation. Human agents who are Online outside working hours can still take over parked conversations manually.When an assigned human agent goes quiet
Two safeguards keep an end user from waiting on a human agent who stepped away.The gambit’s Wait for agent window
A Live Chat gambit has a Wait for agent select with 1 minute, 3 minutes, and 5 minutes. If the assigned human agent sends no reply inside that window, the gambit’s No Agents exit fires. The conversation returns to the agent, and the end user sees the No Agents Available message if one is set.The inbox’s Agent response timeout
Each inbox has an Agent response timeout in the Timing card of the Routing tab. When an assigned human agent has been away from the dashboard for longer than that window, Tars reassigns the conversation. Another eligible human agent is picked with the inbox strategy, and only a human agent with the dashboard open counts as eligible here. A system chip in the thread records that the previous human agent disconnected and whether someone else picked the conversation up. If nobody else is eligible, the conversation returns to the agent flow or waits unassigned. It is never handed back to a human agent who has no dashboard open. For the timeout ranges and the inactivity and reopen windows, see The Routing tab.Assign or reassign manually
You can move a conversation between human agents at any time.From the details rail
1
Open the conversation and expand Assigned Agent in the details rail
Admins see a combobox with the placeholder Unassigned. Other members see only the assignee name.
2
Pick a human agent from the list
Type in Search agents… to filter. Each row shows the status dot for Online, Busy, or Offline.
3
Or select Unassigned to release the conversation
The conversation returns to the Unassigned tab, and any seat holder can take it over.
