MITHUNAI Team · Beta. Access on request.
MITHUNAI Team: work that waits for a person’s approval
Beta. Access on request. Each employee, for Support, IT service desk, DevOps, Marketer, Sales and Finance work, proposes what to do; a person approves, edits or rejects it, and every step is recorded. Reading runs at once; anything with an effect outside MITHUNAI waits for a person.
Last updated
What it is built to do
Propose, then wait
Every action with an outside effect needs a person’s approval by default, and identity, install and remediation actions always do.
Answer from your knowledge, with sources
An employee answers from your organisation’s knowledge through the same answer engine, and hands off to a person when that engine declines.
A record of every step
What was proposed, who approved or rejected it and what was done is kept, and a person’s edits are shown beside the next action of the same kind.
The six employees
Each one reads what it needs, proposes the next step and waits. What it may do, and what it never does, is on its card.
Support
Answers a customer’s question from your knowledge with sources and drafts the reply, or hands the conversation to your team with a summary of what was asked and tried when your knowledge does not cover it.
Works in
- Zendesk, Freshdesk or Intercom, one at a timeBeta
- One Slack channel, for messages outBeta
Each Beta tool is connected with a credential your organisation creates, and is not yet tried against a real account. An email inbox is not connected yet.
Waits for you. A reply is a private note by default, and nothing reaches the customer until a person approves it.
IT service desk
Sorts an IT request, answers how-to questions from your knowledge and records each request as a ticket. It can prepare access changes, password and MFA resets, onboarding and offboarding in your identity provider.
Works in
- Jira or Jira Service ManagementBeta
- Okta, Google Workspace or Microsoft Entra IDBeta
- One Slack channel, for messages outBeta
Each Beta tool is connected with a credential your organisation creates, and is not yet tried against a real account. Requests arrive from the console or the API; it does not read a chat channel yet.
Waits for you. Every access, password, MFA and account change waits for a person, and no policy can lower that. Offboarding suspends an account and never deletes it.
DevOps
Reads an alert’s logs, metrics, errors and recent deploys, writes the likely cause with numbered evidence and a stated confidence, and drafts the incident note and the postmortem.
Works in
- Grafana, for Prometheus metrics and Loki logsBeta
- Sentry, Datadog and PagerDutyBeta
- GitHub deploymentsBeta
- Jira, for the incident noteBeta
- Signed Sentry and PagerDuty webhooks, coming inBeta
Each Beta tool is connected with a credential your organisation creates, and is not yet tried against a real account. It proposes fixes; it never runs one. Incoming webhooks are off until your organisation switches them on, and no vendor has yet sent one.
Waits for you. A rollback or restart is never sent, even when approved. The incident note and the postmortem wait for a person.
Marketer
Drafts an article and social posts from your knowledge, posts each one a person approves to X or LinkedIn, finds pages that lost search clicks, and checks your site’s titles and descriptions.
Works in
- WordPress, for drafts and publishingBeta
- X and LinkedInBeta
- Google Search Console, read onlyBeta
- Your own website, read only
Each Beta tool is connected with a credential your organisation creates, and is not yet tried against a real account. The search check runs when asked, not on a schedule, and a social token that lasts 60 days is replaced by hand.
Waits for you. Nothing is published or posted without a person: each social post is approved on its own, and publishing a saved draft on your site takes a second approval.
Sales
Checks a lead against the qualification rules you write, briefs an account with each fact’s source, and drafts the CRM update and the follow-up email.
Works in
- HubSpotBeta
- Gmail or Microsoft Outlook, one mailboxBeta
- The lead’s public company website, read only
Each Beta tool is connected with a credential your organisation creates, and is not yet tried against a real account. Nothing watches the mailbox yet: a reply or a meeting reaches it as a task a person files.
Waits for you. Every CRM update waits for a person. A follow-up is a draft until a person approves it, and is sent only where your organisation has switched sending on.
Finance
Answers expense and invoice policy questions from your knowledge, reviews card spend and receipts, drafts a bill or invoice and re-codes a bill line, keeps the month-end checklist, and reminds the approvers and close owners your books name.
Works in
- QuickBooks Online or Xero, for the booksBeta
- Ramp or Expensify, card spend and receipts, read onlyBeta
- Stripe, invoices and payments, read onlyBeta
- One Slack channel, for messages outBeta
Each Beta tool is connected with a credential your organisation creates, and is not yet tried against a real account. Concur is not connected yet, and Expensify is read only.
Waits for you. It never moves money: nothing it does pays, transfers, refunds, approves or changes a card. A draft bill, an invoice or a re-coded line waits for a person.
One rule for all six
Reading runs at once. Anything with an effect outside MITHUNAI waits for a person to approve, edit or reject it, and every step is recorded.
How approvals work
Approvals you control
Beta. Access on request. Built and tested; none of this has yet run on a live deployment, and approval rules stay off until your organisation turns them on.
Deny, Allow once or Always allow
Every proposal waits on a card that reads Deny or Allow once. With approval rules on, Always allow lets one employee repeat one kind of action with one tool, and it is never offered for money, deleting, publishing or access.
Exactly what was read, and a second person
An approval holds for the action exactly as it was shown, and nothing else runs. A rule can ask for a second, different person, and an approval left waiting in the background expires after a day.
Try Support on solved tickets first
Run the Support employee over up to ten of your latest solved tickets, reading only, and set a confidence threshold: below it, a reply becomes a hand-off to a person.
Qualification rules you write for the Sales employee
You decide which leads are worth a salesperson’s time. On the Sales employee’s page, an owner or administrator writes rules on three facts — industry, company size and country — and chooses what a lead that fails each rule is: not qualified, or needs review.
A lead that meets every rule is qualified, and only then is a follow-up email drafted, for a person to approve. A fact the lead’s CRM record does not hold makes the lead needs review, never a pass. What the lead wrote and what its website says are shown to whoever approves, and never decide the verdict.
Beta. Access on request. The rules are built and stored with your organisation, and the CRM connection a lead is read from is not yet tried against a real account.
How a piece of work moves
1Hand it over
Give an employee a piece of work from the console or the API.
2Review
It reads what it needs and proposes each action; you approve, edit or reject.
3Done, and recorded
Only an approved action is carried out, once, and the record shows each step.
Who it is for
Support, IT, DevOps, marketing, sales and finance teams that want work drafted for them and nothing done without their say.
Where it stands today
- Access is on request. It is built and tested against stand-ins; its connections to helpdesk, ticketing, identity, monitoring, CRM, mail, website, social, search, accounting and payment tools are not yet tried against a real account. Microsoft Teams as an employee’s chat tool, ServiceNow and Concur are not connected yet. Deciding an approval on a Microsoft Teams card is in Beta, off until set up, and has not yet run against a real Teams tenant.
- Its address will be team.mithunai.com.
Questions people ask first
The other MITHUNAI products, on the same account
- MITHUNAI RAG
Live
Cited answers from your documentation, on your site, over an API and over MCP.
- MITHUNAI Chat
Live
A chat workspace for your team, with cited answers from your own knowledge.
- MITHUNAI Gateway
Live
One OpenAI-compatible endpoint in front of your model providers.
- MITHUNAI AI search visibility
Beta. Not yet run against a real AI search engine.
How AI search engines answer your buyers’ questions, and whom they cite.
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.