An inbox that answers itself — with you in control.
inxo reads the mail your customers send to your shared mailbox, drafts a reply from the whole conversation and what your business knows, and queues it for your team. You stay the sender — every reply goes out as your own address, after your approval. Nothing migrates; your mailbox stays where it is.
Triage.
Everything inbound is threaded into conversations and classified, so the queue reads like a queue — not a pile.
Teach.
Upload documents, paste FAQs, or point inxo at pages on your site. Each workspace has its own knowledge base; nothing is shared between brands. → Knowledge base
Draft.
AI drafts from the full thread and your knowledge base — not just the last message. Grounded drafts show their sources. One rule is enforced on every send: no personal data beyond what the writer provided. Promised fixes, timelines and promotional phrasing are steered, with your reviewer as the control. When neither the conversation nor your knowledge base contains the answer, inxo is instructed not to invent one — and the sources show you what it did use.
Review.
Edit it, regenerate it, or reject it with a reason. Drafts wait for you. Approving is the deliberate moment — the product treats it that way.
Send.
Approve, hold to send, done. The reply is delivered from your own address and reconciled — you'll see it confirmed, not assumed. Every send carries its approval record.
Hard rules, not suggestions.
Replies stay transactional in character. Personal data beyond what the writer provided is blocked on every send. Promotional content, promised fixes and timelines are steered, with your reviewer as the control — which is which is written down, not left to be assumed. Bounces and auto-replies don't generate drafts. Inbound mail — including text addressed to the AI — is treated as material for drafting a reply, not as instructions to follow. Documents in your knowledge base are treated the same way. And underneath all of it, the one rule that doesn't depend on the model being right: nothing sends without approval.
When your team is ready for more Coming
Agent auto-send is designed in from the start: an explicit, per-workspace policy with its own gates and audit trail — never a default, never a surprise. Approval-first is the product today.
Access is scoped to the mailboxes you connect and verified before anything activates. → Security & trust
"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.