Solution
No request goes missing
When support runs through a shared mailbox, whether a customer hears back depends on who happened to open the message. With a single queue every request has someone responsible for it and a deadline the whole team can see.
What usually happens
A customer writes to office@, a colleague replies from a personal address, and after that nobody is quite sure the matter was closed. The customer rings again and explains it all from scratch to someone else. If anyone asks how many requests came in last month, there is no easy way to tell them.
What you get
Every incoming request ends up in one place, whichever channel the customer used, and the most tedious steps of the job happen automatically.
- 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 spot straight away which request 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
Businesses that get the same question several times a week, such as repair shops, online retailers, accounting firms or subscription services. Broadly, it suits anyone whose customers would rather write than phone.
How it starts
You open an account for free, without giving card details, and tell us where requests come from now, which topics keep coming back and who answers what. The first version collects requests from the address you already use. Routing rules and reports are added once you have seen what really arrives.
Where the requests are kept
Requests, replies and each customer’s history are stored in your own application’s database, in the EU by default, with automatic backups. The code goes to your own GitHub repository, and you can export everything to a spreadsheet whenever you like.
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 where most companies prefer to draw the line at first.
Does it work with our existing mailbox?
Yes. Requests are collected from the address your customers already know.
Will customers notice a change?
What they will notice is quicker replies. They won’t have to create an account or write to you through somebody else’s portal.
How much does it cost?
Nothing is charged per user, so the whole team can join at no extra cost. Charges come out of prepaid credits, depending on how much the system is used; the packs are under Pricing.
Bring the requests together
Start with the shared queue, and a month from now you will know how many requests really go through your hands.