Answer the 23:40 support thread before breakfast

Twelve minutes of retrieval, then two of writing

The companion opens the thread, reads the timeline, and goes looking.

GitHub is a native integration too, so it searches the issues and the commit that changed the retry behaviour. The docs and the changelog it reads in the browser like anyone else.

What comes back is a draft with three links in it and a sentence saying which one answers the question. You read it, fix the tone, send. On a team where the person answering is also the person shipping, that is replying tonight instead of replying on Thursday.

What does staged rather than sent mean here?

Replying to a Plain thread sends an email.

No draft state on the customer’s side, no undo. So the companion composes, shows you exactly what will go out and to whom, and waits. Creating a thread is the same.

Customer records get the same treatment for a duller reason. Upserting by external id or email either creates or updates a record other people rely on. Approve it once as a batch, with the diff visible, and a silent rewrite of fifty display names stops being possible.

Who is asking, and what did they hit last time?

A companion searches customers by email, pulls the record, and lists that customer’s threads, so your reply arrives knowing this is the third time they have hit the same edge and that someone already promised a fix. Prep like that is the research habit applied to a queue.

When the record is wrong or missing, the classic case being a company that signed up with a personal address, it upserts the customer so future threads land against the right account. Reconciling records that way is the operations pattern, and you see the changes first.

The tickets where the answer is not written down

The questions whose answer is spread across a commit, a changelog entry and a closed issue, where getting it wrong in public costs more than replying an hour later. Retrieval across your code, docs and history, then a person willing to put their name on the answer.

The high-volume question with one settled answer stays on a snippet in Plain. A companion takes the ones where the answer has to be found first.

Frequently asked questions