Chat is live; the IT service desk employee is in beta
Internal IT help, answered from your own runbooks
Colleagues ask how to get set up, reset something or request access. MITHUNAI Chat answers the how-to questions from your own IT knowledge, with sources. The IT service desk employee records each request as a ticket and prepares the change, which always waits for a person. Beta. Access on request.
Last updated
The problem
An IT team answers the same how-to questions every week, and the requests that do need them arrive without the details. Automating access changes without a person in the loop is not an option most security teams will accept.
How MITHUNAI does it
A chat workspace on your own knowledge
MITHUNAI Chat gives your colleagues threads, saved prompts and attachments, and any thread can ask your knowledge for an answer with its sources.
Your runbooks and past requests
Upload runbooks and connect internal sites; Confluence pages and resolved Jira Service Management requests can be connected too, and are not yet tried against a real account.
Requests recorded as tickets
The IT service desk employee sorts a request, answers it from your knowledge when it can, and records it as a Jira or Jira Service Management ticket, which is not yet tried against a real account.
Limit: Beta. Access on request.
Access changes prepared, never made alone
It can prepare an access change, a password or MFA reset, onboarding or offboarding in your identity provider. Every one of them waits for a person, and no policy can lower that.
Limit: Beta. Access on request. The identity connections are not yet tried against a real account.
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.