Live; the Support employee is in beta
Answer support questions before they become tickets
Put a cited assistant where your customers ask, built on your help centre, documentation and the answers your team has already written. When it cannot answer, it says so, and the customer reaches a person. For the tickets that arrive anyway, the Support employee drafts each reply for a person to approve. Beta. Access on request.
Last updated
The problem
Most support questions already have an answer somewhere in your help centre. The ones that do not are the ones your team should spend its time on, and an assistant that guesses at them makes the queue longer, not shorter.
How MITHUNAI does it
Built on what your team already wrote
Connect a public help centre, a community forum, your documentation, and your own question-and-answer pairs for the questions you want answered word for word.
Says when it does not know
When your content does not support an answer, the assistant declines and says so, so the widget can hand the customer to your team rather than invent a policy.
Shows you the questions it could not answer
Coverage gaps groups the declined questions, and Doc proposals drafts the missing article from your own sources for a person to review before it is used.
Limit: Grouping similar questions is not yet tuned on live questions. Doc proposals is in beta.
Replies drafted, never sent unseen
The Support employee drafts a reply with its sources in Zendesk, Freshdesk or Intercom, which are not yet tried against a real account, and a person approves it before the customer sees it. When the answer is not in your knowledge it hands off with a summary instead.
Limit: Beta. Access on request.
Tried on past tickets first
Run it over your latest solved tickets to read what it would have said and how sure it was, and set the confidence below which every reply goes to a person.
Limit: Beta. Access on request. It has not yet run on a real helpdesk.
What does this job
In the documentation
Grounded answers from your own knowledge, a chat workspace for your team and one model gateway, on one account.
A 30-minute walkthrough on your own use case: connect a source, ask it questions, check the citations and see what it does when the answer is not there. Or ask the public playground now, with no account.