Subscription mail is a genuinely hard triage problem, and it is a problem of proportion rather than volume: out of forty messages a week, two matter — a price increase and a trial about to convert — and thirty-eight are marketing. The Universal Inbox exists to make those two findable.
Every message in the inbox carries three fields that make triage possible. A category places it in one of seven buckets: Billing, Marketing, Product update, Renewal, Security alert, Required action, or Other. An action-required flag marks the messages that need a human decision. And an optional confidence value records how sure the classifier was about the category it assigned. All three are first-class parts of the API, not display-only decorations.
The screen is built around them. Category tabs filter the stream, an unread toggle narrows it further, and an action-only filter collapses everything to just the messages that need you. Open a message and, when a confidence value is present, you see it rendered as a labelled meter — high, moderate, or low — so a category the classifier was unsure about looks visibly different from one it was confident in. That is deliberate: a triage surface that hides its own uncertainty trains you to over-trust it.
Messages arrive through ingest channels you register and verify yourself, and each message can be linked back to the Relationship it concerns, so context is inline — which subscription this is about, what it costs, when it renews next. Ingest is metered against your plan, so a runaway connector cannot silently consume your quota.
The honest state: the classifier is not built. Category, confidence, and the action-required flag are supplied when a message is ingested, which means today they come from whatever registers the channel rather than from a model reading the message body. The full end-to-end contract is in place and the UI already renders confidence properly, so when the classifier ships it fills existing fields instead of forcing a schema migration and a UI rewrite — but until then, treat automatic categorisation as designed rather than done. The same applies to the upstream half of the story: mailbox and statement connectors that would populate the inbox without you doing anything are on the roadmap, and the product documentation says so plainly.
Do it yourself
Build the triage surface end to end — register an ingest channel, verify it, log a message with a category and confidence, then filter the stream down to only what needs a decision.
Open the Universal Inbox to see every subscription message in one stream, with category tabs across the top.
You should see: Billing, Marketing, Product updates, Renewals, Security alerts, Required actions, and Other are each one click away.
Ready to make this your story?
