Solution
No request goes missing
When support runs through a shared mailbox, whether a customer gets an answer depends on who happened to open the email. With a single queue each request has someone responsible for it and a status everyone can see, plus a deadline.
How things stand now
Customers write to info@, someone replies from their own address, and a few days later nobody is sure the reply ever went out. So the customer rings back and goes through the whole story again with someone else, and at the end of the month you could not say how many requests came in.
What you get
One place where every request ends up, whichever channel it came through, with a few automatic steps that take the repetitive part of the job off your hands.
- A single queue from email, the website form and manually logged phone calls.
- Automatic routing by topic and a suggested reply that a person approves.
- Statuses and deadlines, so you can see straight away what has stalled.
- Customer history: whoever picks up next sees everything so far.
- A report of how many requests arrive, on what topics, and how long they take to close.
Who it is for
It helps wherever the same question comes back several times a week: repair centres, online shops, accountancy firms, anyone selling a service on subscription. Broadly, any business whose customers write more often than they phone.
Getting started
You can build it yourself in the studio by explaining in plain words how you work now, or we can do it together (details in Services). A first usable version is normally ready within a few days.
- You define the topics, statuses and deadlines to match the way you work.
- Every team member comes in with their own role, and every change leaves a trace in the audit log.
- There is no monthly fee and no charge per user: you top up credits and they are used as you go. Details on Pricing.
When the questions come from the website
If a lot of requests repeat themselves, an AI assistant on the site can answer from your own documents and pass on to the queue only what needs a person. See AI chatbot for your website; the steps after the answer run with process automation.
Frequently asked questions
Does the AI answer customers on its own?
Only if you decide it should. By default it drafts a reply and a person sends it, which is the boundary most companies want at the beginning.
Does it work with our existing mailbox?
Yes. Requests are collected from the address your customers already know.
Will customers notice a change?
They will notice faster replies. We will not make them create an account or write through somebody else’s portal.
What happens to our data if we stop?
You export it. Requests, customers and history are yours and come out as a table at any time; the data stays in the European Union.
Bring the requests together
Begin with the shared queue, then look back after a month at how many requests you actually handled.