Help Scout

Promptfree, for everyone, and the only version there is

Open the prompt in Claude CodeOpen the prompt in CodexOpen the prompt in Cursor

Copy

Build me a shared support inbox where threading actually holds.

STACK
- Node with Fastify, SQLite via better-sqlite3, server-rendered HTML
- IMAP or a provider webhook in, SMTP relay out

THREADING, THE PART THAT DECIDES EVERYTHING
- Match on Message-ID, In-Reply-To and References headers first
- Fall back to subject matching only as a last resort, and log when it happens
- Store the raw MIME source, so a threading bug stays fixable years later

CONVERSATIONS
- Status of open, pending or closed; assignee; tags
- Internal notes visibly distinct from customer-facing replies, and sending a note as a reply must be hard to do by accident

COLLISION
- A short-lived viewing lock showing who else has the conversation open, refreshed by polling

REPLIES
- Sent from the support address with correct In-Reply-To headers, so the customer's client keeps the thread
- Every outbound message appended to the conversation log

SPEED FOR THE PERSON ANSWERING
- Saved replies with variable substitution
- A keyboard-driven queue: j and k to move, r to reply, a to assign

REPORTING
- First-response and resolution time computed from the event log, never stored as fields

Include a test with three real-world quoted-reply formats, proving threading holds on all of them.