Features
One inbox for every channel, with the agent and the team in one thread
Web messenger, Telegram, Bale and email in one place. The agent answers, the team takes over whenever it wants, and everything stays in the same conversation.
The problem
Customers write at 1am. Every night the queue grows, and every morning starts behind.
- 01
Filter, order, views
"Mine", "unassigned", "escalated"; the "longest waiting" order says what to answer right now; a set of filters saved under a name is a view you can send a teammate.
The inbox: list, filters and views. - 02
Inside a conversation
The full thread with read receipts, the customer's details, and the trace: which sources the agent used, which tools it called, how sure it was, which skill fired.
A conversation: the thread, the customer's details, the agent's trace. - 03
Take over and hand back
"Take over from the agent" silences it and the conversation is yours; "hand back" is the reverse. "Enhance" tidies your rough draft without sending anything.
- 04
Tasks the agent records for the team
A request a person must handle becomes a task: claim it, do it, mark it done. Then the agent drafts the message to the customer and sends nothing until you say so.
- 05
Tags, teams, hours
Tags you defined, and the agent applies only those; routing rules to teams; working hours and what happens outside them; a response deadline on each conversation.
Tags: each with its meaning and the "agent applies" switch.
Typical chatbot
A chat window on the site, and Telegram messages somewhere else.
goya24
Every channel in one queue, with the reason for each of the agent's answers beside it.
The rest of the product
Your first agent is ten minutes away
Free while you evaluate. Bring your own model keys if you'd rather.