Customer support where a ticket can turn into a call.
Email, chat and messaging channels land in one ticket inbox. Warren answers what your docs already cover and hands the rest to your team with the conversation so far. When typing is too slow, the customer is one click from a voice or video call.
One desk for every way customers reach you.
The inbox, the assistant and the calls are the same product, not three tools wired together.
Ticket inbox
Every channel, one inbox
Emails to your support address, chats, WhatsApp, Messenger, Instagram DMs, Telegram and SMS all become tickets. A reply goes back the way the customer came in.
AI assistant
Answers first, hands over cleanly
Warren is trained on your website, docs, questions and answers, and solved tickets. When a customer asks for a person, a ticket opens with everything said so far.
Calls and screen sharing
A call when chat is not enough
The customer calls from the widget and shares their screen from a desktop browser, so you see the problem instead of reading about it. Ask a teammate to join the same call.
Skills and MCP
Actions, not only answers
Skills let the assistant do things, like refund a Stripe invoice, inside limits you set and after a clear yes. Connect your own AI over MCP and it can work tickets too.
One problem, start to finish.
The chat, the ticket, the call and the reply stay on one desk and one customer.
The question
A customer asks in the chat. Warren answers from your sources, or opens a ticket when they want a person.
The ticket
It lands in the inbox with the whole chat. The copilot sums it up, suggests the next move, or writes a reply from your notes.
The call
If it needs a look, they call from the widget. From the call, one click opens every conversation that customer has had.
The follow-up
Your reply goes out by email or the channel they used, and their answer comes back onto the same ticket.
Customer Support, in questions.
The things teams ask before they switch. If yours is not here, the widget in the corner answers from the same training our own desk runs on.
Email sent to your inbound address or forwarded from your own support address, the chat widget, WhatsApp, Facebook Messenger, Instagram DMs, Telegram and SMS. Each lands in the same inbox, and a reply goes back on the channel it came from.
No. When a customer asks for a person, however they put it, Warren hands the conversation to your team and a ticket opens with everything said so far.
Choose solved tickets and NewDesk turns your team's own answers into questions and answers Warren learns from. The questions he could not answer are listed under Gaps, so you know what to write next.
Yes. The whole ticket inbox is in the mobile app, and call requests ring there too.
On the desk and in the mobile app, and in Slack, Discord or Microsoft Teams if you connect them. Webhooks send the same ticket events to your own systems.
The other ways teams use it.
The same desk, set up for different work. See all NewDesk solutions.
Answer every channel from one inbox, and take the call from it too.
Start with 30 days free. Point your support address at NewDesk, paste your website so Warren can learn it, and switch on calls when you are ready.