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 first. With a single queue every request has someone responsible for it, and you can see how far it has got and when it is due.
The problem today
A customer writes to office@, someone replies from their personal address, and afterwards nobody knows whether the question was dealt with. The customer calls again and explains everything from the start to a different colleague. And if someone asks how many requests came in last month, there is nowhere to look.
What you get
You get one place for every incoming request, whatever channel it arrives on. Automatic steps take care of the dullest part of the work.
- A single queue with requests from email and the website form, plus phone calls you log by hand.
- Automatic routing by topic and a suggested reply that a person approves.
- States and deadlines that make it obvious which request is sitting still.
- Customer history, so whoever picks up the phone 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 is for companies where the same question arrives several times a week, such as repair shops, online retailers, accounting firms or subscription service providers. It is most useful when your customers write more often than they call.
How it starts
We start with a description of how you work today: which addresses customers write to, and who answers which questions and how quickly. You set the topics, states and deadlines to match the way you already work. A first working version is usually ready within days, and colleagues sign in with roles, so some see every request and others only their own.
- If you want an assistant to answer on the site and only pass to the help desk what needs a person, see AI chatbot for your website.
- Repeating steps after a request is closed, such as a notification or a record in another system, can be automated too; see Automation.
The data is yours
Requests, replies and customer history sit in your organisation’s isolated space, in the European Union, and you can export them as a table at any time. Every significant action is recorded in an audit log showing who did what and when. The source code goes into your own GitHub repository.
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. That is how most companies prefer to start.
Does it work with our existing mailbox?
The help desk works with your existing mailbox: requests are collected from the address your customers already know.
Will customers notice a change?
They will notice that you reply faster. We will not make them create an account or write through somebody else’s portal.
How much does the help desk cost?
You can start the help desk for free, without entering a card. After that you pay with prepaid credits according to how much it is used, with no subscription and no per-user fee, so inviting colleagues costs nothing extra. Each active project also has a daily hosting fee. Credit pack prices are on the Pricing page.
Bring the requests together
Start with the shared queue, and after a month you will see how many requests actually pass through you.