Chatbot or service desk: what each one does in your inbox
They are two different jobs on the same inbox. A plain look at where the chatbot stops and the desk begins.
People often ask whether they need the chatbot or the service desk. They are not alternatives. They do different jobs in the same Inbox, and the best way to understand them is to follow one message through.
What the chatbot does
The AI Chatbot is the first reader. A customer writes on SMS, WhatsApp, e-mail or your website chat. If your own knowledge answers the question, the assistant replies. If it does not, the assistant does not guess: it hands the conversation over.
That is the whole job. It does not manage your team, does not remember who is on holiday and does not decide what counts as urgent. It turns a stream of questions into two piles: the ones your material settles, and the ones a person should read.
What the service desk does
The service desk is everything that happens to the second pile, and to any conversation a person handles from the start. It turns the Inbox into a place a team can work in together:
- Queues and assignment. Conversations are routed to a team or a person, and you can see what is open, pending, snoozed or resolved.
- Notes and canned replies. Internal notes stay in the thread. Canned replies are inserted with a shortcut and the contact's name filled in.
- Response targets. You set a first-response target per channel. A conversation past its target is flagged and alerted to the team.
- Reports. Volume by channel, response and resolution times, hand-off reasons and the questions nobody could answer.
None of this needs the chatbot switched on. A team can use the desk with the bot off.
How they meet: the hand-off
The seam between the two is the hand-off. When the assistant hands over, three things happen in order: the people you chose are told, the customer gets a sentence you wrote, and the conversation appears in your queue with the question already in the thread. Outside opening hours the customer gets your away message instead, so nobody waits in silence.
From that moment a person owns the conversation. The assistant stays quiet while someone is handling it, and it only answers again if a person hands the conversation back.
Choosing where to start
Which one you start with depends on where your problem is:
- Many repeat questions, a small team. Start with the chatbot and its knowledge. Keep shadow mode on for WhatsApp and e-mail so you read every draft first.
- Messages already pile up and get lost. Start with the desk: queues, assignment and response targets fix the "who has this" problem without any AI.
- Both. Run them together. The bot trims the repeat questions, and the desk makes sure the rest has an owner and a clock.
An honest limit
The chatbot has not been measured on real customers, so we do not claim how many conversations it will settle or how much time it saves you. What we can say is that it is designed so a wrong turn is visible: answers show their sources, drafts wait for approval where you want that, and every hand-off lands somewhere a person will see it.
Where to read more
Setup is covered in the service desk docs and review and hand-off. If you want the bot first, add it to your website.