Every thread has one owner
Not "whoever saw it first". Agents route by content; the team sees who's accountable, in Gmail.
Sortd is the shared inbox your team already runs on Gmail — now open to your AI agents. Your team works the board, your agent works the API, and nothing ships without the permissions you set.
Agents triage, draft and chase follow-ups on support@ and orders@ — your people approve and stay accountable.
Point Claude, Cursor or your own agent at a real shared inbox — REST + MCP, scoped, audited. 5-minute setup guide.
Managed email workflows on your customers' Google Workspace — no separate agent email stack to run.
Your agent composes Sortd's MCP with every other MCP it already has — in one session. We didn't build these integrations, and we don't have to maintain them: your agent brings them.
Sortd Agent triages the shared inbox, classifies, sets status, assigns Maya with a deadline and drafts the reply. Maya reviews and sends. Alex invoices. Nobody left Gmail.
SORTD AGENTThis is the part nobody else has. Agent platforms make you build a supervision UI; helpdesk tools make your team leave Gmail. Sortd is one workspace with two front doors: your agents call the API, your team works the same threads natively inside Gmail — desktop and mobile. Same data, same statuses, same audit trail. That's why it actually gets adopted.
Email was designed in 1971 for messages between two people. It has no construct for "who owns this", "when is it due", "where is it in our process", or "hand this to Maya with context". Teams fake it with forwards, labels and CCs — and agents can't work with that at all. Sortd adds the missing layer: every thread becomes a structured object both humans and agents can operate on.
Not "whoever saw it first". Agents route by content; the team sees who's accountable, in Gmail.
Due dates, follow-up timers and SLA rules on email itself. Nothing rots unread; escalation is automatic.
Open → Working on → Waiting for approval → Done. Your process, as board columns both interfaces share.
order_id, refund_policy, deal_size — typed fields agents read, write and classify into. Fields API →
Agent → human → agent, with notes, history and next steps attached. No forwarding, no "see below".
Contacts, companies, pipelines and history — the context agents ground their drafts in.
Giving an agent safe Gmail access yourself means a Google Cloud project, OAuth consent screens, restricted-scope verification (a CASA security audit), token refresh plumbing and months of review. Sortd already carries Google-verified access — you inherit it.
Add Sortd to Gmail — one click from the Workspace Marketplace. Shared inboxes like support@ and orders@ connect the same way.
Pick board columns for your process, add custom fields, set SLA rules. Your team keeps working in Gmail the whole time.
Create a scoped API key, point Claude / Cursor / your stack at the MCP server, and it starts working the board — drafts only, until you grant more.
Boards, assignment, custom fields, SLA rules — the visible place where agent work is inspected, approved and measured. Native in Gmail, desktop and mobile.
REST endpoints and a full MCP server for threads, tasks, boards, fields and CRM. Your agents work the same workspace your team does.
drafts.write by default. email.reply and drafts.send only when granted. Circuit breakers, throttles and loop detection under everything.
Who acted — human or agent — on what, when, and why. Agent-activity reporting your ops lead can actually read.
Full API + MCP on Business. Your agent and its brain stay yours — portable prompts, knowledge and model choice. No credits, no per-resolution charges — ever. No action allowances. Bring your own agent — flat seats, fair use.
Most work starts and ends in email. Every agent tool that asks your team to move to a new app dies in week three — the tab gets closed, the agent goes unsupervised, the pilot fails.
Sortd's interface is inside Gmail — the tab that's already open, on desktop and mobile. Supervising an agent is the same motion as reading email. Zero migration, zero retraining, zero "please check the other tool". That's why the human-approval loop actually happens.
Connect your Gmail or Google Workspace inbox, shape your first workflow, and hand your agent a scoped key — all before your next standup.