Email in. Answers out.
An inbox that answers itself — with you in control.
Built for Microsoft 365. Connect the shared mailbox you already own, add what your business knows, and the customer mail your team would have written by hand arrives with a reply drafted, grounded, and waiting for your approval. Priced per mailbox — not per seat.
Free during early access.
Why inxo
Drafts that answer.
Grounded in the whole conversation and your own knowledge base — pricing, policies, hours, how-tos — with the source shown on every draft.
A review step you trust.
Nothing sends until a person approves. Edit, regenerate, or reject with a reason. Every send carries its record.
No per-seat tax.
inxo runs on a shared mailbox you already own. One mailbox, one price, the whole team.
How it works
- 1Connect. A scoped, verified grant to one shared mailbox — never your whole tenant. Nothing migrates: your mailbox stays where it is.
- 2Teach. Add the documents, FAQs, and pages your team answers from. Three entries is enough to start.
- 3Review. Eligible customer mail arrives with a draft and its sources. Edit, regenerate, or reject — in the Console or over the API.
- 4Send. Approval is the deliberate moment. The reply goes out as your own address, and it's on the record.
"How long does a warranty repair take, and do I need the original receipt?"
Warranty repairs are finished within five working days of arriving at the workshop. You don't need the original receipt — the serial number on the base plate is enough for us to find your purchase.
The draft cites what it used. If the knowledge base doesn't contain the answer, inxo is instructed not to invent one — and the sources show you what it did use.
Every inbox you run — answered by AI, in one place.
One account. A workspace per brand — its own mailbox, its own voice, its own knowledge base, its own team. One rollup across all of them.
› "Any messages for any of my products?" → 3 awaiting approval: 2 in Brand A support, 1 in Brand B sales — oldest 42 minutes.→ See the portfolio story
DEVELOPER TIER
Everything your team does in the Console, as an API and an MCP server.
Every capability is a REST endpoint and an MCP tool. Your systems and your agents run the same loop your team does — under the same approval policy.
Built like infrastructure, because it is.
Access scoped to the mailboxes you connect, and verified before anything activates. A person approves outbound by default. Every draft, approval, and send is audited. Replies stay transactional — the drafting rules steer away from promotional content, with your reviewer as the control.
"How is this different from Front or Help Scout?"
They are shared inboxes priced per agent seat. inxo is built for Microsoft 365, priced per mailbox, drafts your customer replies from your own knowledge base with the source shown, and keeps a person on every send by default. And everything it does is also an API and an MCP server, for when your systems want in. → Compare
"Doesn't Copilot already do this?"
Copilot helps the person composing a reply in Outlook — and it's good at that. inxo is the whole loop around the shared mailbox: triage, draft, review, approve, send, audit — with a record for each step and no per-person license. If you want help writing individual replies, Copilot is fine. If you want the shared inbox handled, that's inxo.
"Do I have to move my email?"
No. Your mailbox stays in Microsoft 365. inxo connects to it with a scoped, verified grant and sends as your own address. Disconnect stops the sync, tears down our access and erases what we hold — and hands you a record of exactly what was removed, plus the one step only your Microsoft administrator can take.