Inbox zero is the default.
Inbox is one queue for email, support, shared inboxes, and DMs. Every message is triaged, linked to the deal or project it is really about, and pre-drafted in your voice. You arrive to a sorted shelf, not a 400-message wall.
Five things, in priority order.
An exec sees 200 to 600 messages a day across mail, support, Slack DMs, and shared inboxes. Inbox compresses that into the 12 to 20 that need them, with drafts attached.
Five capabilities, in order of value
- Unified queue across surfacesEmail, Slack DMs, support, shared mailboxes, in-app notifications. One queue. One sort.
- Auto-triage with explainable scoringEvery message gets a priority and a one-sentence reason. You can read why before you trust it.
- Pre-drafted replies in your voiceDrafted against your prior writing style and the relevant context. Edit and send, or send as-is.
- Threads attach to the right workThe customer email links the deal. The bug report links the task. The contract reply links the agreement. No filing.
- Rules and auto-actionsCalendar invites for status reviews accept themselves. Newsletters batch to a daily digest. Sales outreach declines with a polite explanation.
confidence: 0.94
signals
· open deal: $284k (CRM)
· sender: procurement reviewer
· DPA was sent 4d ago
· last reply latency: 11h
action
draft ready, deal+task linked.
Three loops, no rules engine.
Inbox does not ask you to write filter rules. The loops are pre-configured from your actual behavior and the work graph.
Pull from every surface
Email, support tools, DMs, in-app, and shared inboxes ingest into one stream. Threading is cross-surface, so a Slack reply to an email reply stays in the same thread.
Score, sort, and explain
Priority is derived from sender, thread state, related work, deadline, and your historical response patterns. Every score has a one-sentence reason.
Reply, defer, or auto-act
Send the draft, edit and send, defer the thread, or let an auto-rule handle it. Everything lands in audit. Nothing happens without a clear actor.
Nine things, all built in.
Each item below is on by default and works for every surface Inbox connects to.
Snooze with intent
"Until they reply." "Until the deal moves." "Until Tuesday 8am their time." Not a timer, a condition.
Shared inboxes
support@, billing@, contracts@. Assigned, watched, SLA'd. Per-team views without forwarding spaghetti.
Auto-actions
"Decline sales outreach with a clear no." "Auto-accept all-hands invites." "Forward legal threads to counsel."
Outbound checks
Catches the wrong recipient, the missed attachment, the phrase you regret. One-click rewrite.
Search inside threads
Finds "the password we agreed" across 4 years of mail, attachments included. Respects retention rules.
Cross-language drafts
Reply in EN, JP, DE, FR, ES, PT. Source language preserved as a hover. Tone matched per market.
Encrypted end to end
TLS 1.3 in transit and encryption at rest on every message and draft. Your mail content is never used to train shared models.
Out-of-office that means it
OOO auto-deflects to the right deputy by topic, with a real ETA grounded in your calendar.
Audit and retention
Every action is logged and exportable. Per-thread retention, legal hold, and eDiscovery export.
Threads know the work.
Inbox does not live in isolation. Every thread links to the deal, task, project, or contract it actually concerns.
Six modules read the same thread
A support email becomes a Tasks ticket. A deal reply updates CRM. A signed redline closes a Contracts step. A meeting recap auto-files to the Meetings room. Nothing requires copy-paste.
Programmatic triage.
Subscribe to every triaged thread. Override the model when you need to.
# Listen for every NOW-priority thread, ship a 2-line summary to Slack. from wrxstack import Wrx wrx = Wrx(token=os.environ["WRX_TOKEN"]) async for ev in wrx.inbox.stream(priority="now"): summary = ev.thread.summary(max_sentences=2) await wrx.slack.post( channel="#exec-inbox", text=f"{ev.thread.subject} · {ev.score.reason}\n{summary}" ) # Or override the model for a specific kind of message. await wrx.inbox.rules.add({ "name": "contract_redlines_always_now", "match": { "subject_contains": ["redline", "DPA"] }, "set_priority": "now", "link": { "object": "contract", "by": "latest_open_with_party" } })
Inbox vs. Front.
Front is a shared inbox with rules. wrxstack Inbox is a queue that reads the work graph and writes drafts.
wrxstack Inbox vs. Front
| Capability | Front | wrxstack Inbox |
|---|---|---|
| Cross-surface threading | Mail + a few channels | Mail, DMs, support, in-app, shared |
| Triage signal | Manual rules | Behavior + work-graph model |
| Pre-drafted replies | Snippets | Voice-matched, context-grounded |
| Link to CRM / contracts / tasks | Manual or via plug-in | Native, same workspace |
| Outbound checks | Not built in | Wrong-recipient + tone catch |
| Audit and retention | Basic export | Per-thread log + export |
| Trains on your mail | Policy varies | Never, per model-provider terms |
Common questions.
Six things people ask in the first hour of trying Inbox.
Does it read my mail? Where does the content go?
Inbox processes message content on the platform's managed hosting, encrypts it in transit with TLS 1.3 and at rest, and never uses your content to train shared models. Drafts are generated by a dedicated per-tenant inference layer. Audit logs record every model call with a stable hash of the input.
How does it learn my voice without me writing examples?
The voice model fits on your sent mail and your written docs (read-only) for the last 90 days. It captures sentence length, idiom, sign-off style, and politeness gradient. The first day, drafts are conservative. They sharpen as it sees more of your sent mail.
What if it triages something important as later?
You can pin senders, topics, deals, or projects to "always now". Every misprioritization you correct trains your view, not the shared model. The default model also reads back from the work graph, so a deal in late stage gets escalated even from a new sender.
Can a shared inbox be split across multiple teams?
Yes. support@ can route by topic (billing, security, integration) to different team queues, with their own SLAs and escalation rules. Each routed thread keeps a unified history that any authorized agent can see.
Does Inbox replace my mail client, or sit alongside it?
Both modes are supported. You can run Inbox as the primary client and let your mail client handle archive search. Inbox writes its actions back to the underlying mailbox so a teammate on Outlook sees the same state.
What about calendar invites and scheduling?
Inbox handles invites natively. Auto-accept patterns, conflict resolution, and "find a time" replies are built in. Scheduling can be delegated to Meetings, which has a fuller booking surface and AI prep notes.
Pairs well with.
Inbox is sharpest with CRM and Meetings live. Tasks is the natural escalation target.
Who this is not for.
Inbox brings shared email to zero by default. If your team runs a high-volume support desk that lives on SLA timers, CSAT surveys, macros, and tiered queues, a dedicated helpdesk will serve you better. Inbox is built for teams handling shared conversations, not a full contact center.
Get your morning 90 minutes back.
Free to start, no credit card. Connect Gmail or Outlook. The first triaged queue lands inside 20 minutes.