Support inbox

Backed by: @pithy-sh/support. Scopes: support:threads:read · support:threads:reply · support:threads:archive · support:threads:reclassify · support:threads:flag · support:threads:assign.

One inbox, two intakes

Mail arrives with provenance already decided; feedback is the other intake and needs none. Classification sorts both, and running a support inbox is the capability walkthrough.

Mail claimed on the SMTP envelope recipient, and in-app reports from signed-in users.

Same table, same classifier, same taxonomy, same console — because a support person with two consoles has the whole conversation in neither.

channel rides on the thread and on every message, so one app thread can hold an answer that was mailed and one that was not.

Finding a thread

The index opens on the open inbox, and on the threads assigned to you where sharing the inbox is on. Below Team it opens on every open thread. Done is one choice away: the Status filter is Open or Done, and Done asks your Worker for the threads marked done.

Every filter is sent to your Worker, and answered over the whole inbox, not over the page already read: status, assignee, channel, category, declared category, priority, sentiment and inbox. Category, declared category and inbox offer the values the threads read carry. The inbox reads a page at a time, and More reads the next. The overview is how the filter panel works.

Unread is not a filter. Read state belongs to the credential this connection shares, not to the person looking, so it is never drawn.

Render the provenance, not a boolean

accountLinkSourceMeans
sessionAn authenticated request proved it
email_addressMatched from a From: header nobody proved
nullThe address belongs to nobody with an account

Triage on the disagreement

declaredCategory is what the submitter chose. category is what the model decided. They never share a column.

Filter on either, independently. Filtering on both asks for the threads where they agree — and they filed it as billing, the model calls it a bug report is the most useful row on the screen.

Three sortable axes from one classification

Category answers what is this. Priority answers how fast. Sentiment answers who is about to churn.

angry and frustrated are the ones worth sorting an inbox by.

With AI off

category is uncategorized forever, and the declared category is the only one anybody stated.

Which is exactly the deployment that made two columns necessary.

Replying

A mailed reply to an app thread is recorded as email — and the submission was minted a message id on the way in, so the customer’s answer threads back rather than opening a new conversation.

Threading is on In-Reply-To and References, never the subject.

Reading a thread

Open a row and the record reads that one conversation from your Worker, under support:threads:read: every message oldest first, who wrote it, from and to, and when. The newest three are open at the foot. Anything older folds under a count, and so does quoted history.

A body is drawn inert. Plain text stays text. HTML is rebuilt from an allowlist and never injected, so no script runs and no remote image loads; an image leaves its alt text. The thread’s attachments are listed by name and size, each a link only where your Worker signed one.

The conversation is read again on every open and cached nowhere. It lives in the record that asked for it, and goes when that record does.

What you can do from a thread

Reply. Mark it done, or reopen it. Classify it again. Mark it read or unread. Each spends its own scope — support:threads:reply, :archive, :reclassify and :flag — because a credential that can mail your customers from your domain is a different blast radius from one that can tidy the inbox.

A reply is written under the last message, on the record itself. Before anything is sent it shows who the reply goes to, what it comes from, the subject, and the name it is signed with. Send asks once more on the same screen, with the draft still in view, and only Send it spends support:threads:reply. Send and mark done spends :archive too, and is offered only where that scope is granted. An in-app thread may be answered in the app, with no mail sent.

It is signed with your name. Where your name could not be read, the reply goes unsigned and the record says so before you send.

Your draft is kept in this browser, one per thread, until you send, sign out, or leave it for seven days. It holds your words and when you wrote them, and nothing read from your Worker.

All four are part of Solo. Below it each is drawn locked and says what the plan buys, and your Worker answers the same routes on any plan.

Sharing the inbox

Assign a thread, narrow the inbox to who has it, and see who else has it open. Assigning asks first and spends support:threads:assign: it hands the conversation to a member of your organization, or to nobody, with an optional note, and everyone who can read the thread sees who has it.

The index’s Assigned to filter narrows the inbox to you, to nobody, or to one member by name, and Any is everyone. Your Worker answers that read, so the rows are its answer rather than a cut of the ones already on screen. Below Team the filter is drawn locked, naming the plan.

Open here lists who else has the thread open, and whether they are viewing it or replying, including people working it from your own app’s admin UI, marked in their app. It is a presence room on your Worker, joined with the scope that already reads the thread, support:threads:read. A Worker that serves no room for a thread, or a connection not granted that scope, says so instead.

Both facts live on your Worker, not here. The assignment is in your D1 and presence is a room in your Worker, so your own admin UI and your agents see what this pane sees. Each of our people reaches your Worker as a display name and a ref our server computes for that one connection, never an address, so two customers comparing notes cannot tell they share a person.

All three are part of Team. Below it each is drawn locked, names the plan that buys it, and sends nothing.

What you own

The mail, the database, the bucket, and the inference. No Pithy-operated service in the path.

ESC