NewDesk team5 min read
Two products, one customer, the story told twice
The normal setup is a bot on one side and a help desk on the other. The bot talks until it gives up, then it "transfers" you, and a ticket shows up somewhere with none of what you just said. You start again from the top. Everyone hates this moment, and it only exists because the two halves were built by two different teams.
So I made it one thread
In NewDesk there is one conversation and both the AI and your team answer in it. The AI goes first, from your own pages, and shows its source. When the customer wants a person, or the AI admits it does not know, the same thread carries on. Your teammate opens it and reads what was asked, what the AI tried and what the customer said about it. Nobody gets asked anything twice.
The customer sees one chat the whole way through. The AI's lines are signed as the AI. Your teammate's lines are signed with their alias.
The human gets a copilot, not a replacement
When a person picks the thread up, the inbox hands them the gist of it and a drafted reply from the same training. Edit it, send it, or bin it and type your own. Notes with an @ reach a colleague by email and push. Voice messages, files and GIFs sit in the same thread as text.
Your own AI can work the thread as well
Over MCP, the AI your team already uses can read the queue and act in it as you, through fifteen named tools. Reply to a ticket, add a note, look up a customer's billing. The two tools that move money or end a service ask a person first and stick to the limits the owner set. Every run is written on the ticket.
Why this is the whole product
A handover is where you lose the customer. Merging the bot into the human thread is not a nice touch on top of a help desk. It is the reason the customer is still there when your teammate shows up.