A service desk that already knows your documentation

Support

Playable below - no signup

Support is a surface of the workspace rather than another subscription: shared inboxes, statuses, assignment, tags and an audit trail — with assistants drafting replies from the same knowledge base your team already maintains. The draft is a starting point a human sends, never an answer that goes out on its own.

Try it below

Live demo

Eight tickets, four statuses, one mailbox

Filter by status, open a thread, change a priority, ask for a draft. The internal notes and the non-support bucket are both there, because a real inbox has both.

Sample tickets only. No mailbox is connected, nothing is sent, and the draft button assembles a canned reply rather than calling a model — it says so in the text it produces.

Why it lives here

The knowledge is already in the building

Drafts grounded in your own material

The assistant answers from the knowledge bases you already maintain for everything else, so support stops being a separate copy of the documentation that drifts out of date.

A person still sends it

Drafts land in the composer for review. Nothing is auto-sent, because the ticket where an automated reply is wrong is exactly the ticket where it matters.

One audit trail

Support actions land in the same trail as automations and admin changes, rather than in a second system somebody has to be given access to.

How a ticket moves

From an email to a resolved thread

Mail arrives and is triaged

A connected mailbox becomes a queue. Marketing and invoices get tagged out of the way so the awaiting-agent view is only work.

Gmail or Microsoft 365, OAuth per mailbox

An assistant drafts an answer

Grounded in the knowledge bases attached to that inbox, with the passages it used attached. If it has nothing to go on, it says so instead of improvising.

draft → review → edit → send

A person sends, and the trail records it

Status moves, the assignment stands, and the exchange stays in one place — including the internal notes, which the customer never sees.

awaiting agent → awaiting customer → resolved

What it is not

Said before you evaluate it

This is a team inbox with AI drafting, not a full ITSM platform. There is no CMDB, no change management and no customer-facing portal — if you need those, we integrate with Jira, ServiceNow, Zendesk, Freshservice and TopDesk rather than pretending to replace them. Support Inbox is enterprise, opt-in, and gated per member as well as per organisation.

FAQ

Worth knowing

Does it reply to customers automatically?

No. Drafts go to the composer and a person sends them. Auto-reply is the feature everyone asks for and then switches off after the first wrong answer reaches a customer.

Which mailboxes can we connect?

Gmail and Microsoft 365 through OAuth, per mailbox. The integration acts as the account that authorised it, so it can never read more mail than that account could.

Does it replace our ITSM?

No, and we would not suggest it. It is a shared inbox with drafting and an audit trail. For change management and a CMDB, keep the tool you have — five of them are built-in integrations.

Who can see the tickets?

Access is per member as well as per organisation: someone needs the support permission on top of the licence. A colleague with a workspace account does not get the inbox by default.

Point it at one mailbox and see what it drafts

The useful test is a real question your documentation already answers. If the draft finds it, the rest follows.