The customer record · designed, being built
Every customer, one record.
Support tickets by email, contacts and companies, leads and the pipeline — for every product, with nothing to install in any of them.
$ dig +short MX support.example.com10 inbound.postmarkapp.com.$ purser workspace ensure example --inbound support@example.comworkspace example: ready · inbound address verifiedticket #1 opened · from a customer · 'Hi, I can't sign in'What it is
What Purser owns.
The design in six lines. The full version is in the docs.
Email-first support
support@your-product arrives as a ticket; replies go out from the same address with the threading headers that keep conversations whole.
Contacts and companies
A contact the moment someone writes in, keyed so it converges with their identity the day they sign up. Companies hold the contacts.
Leads and the pipeline
A lead is a conversation with a stage: lead → qualified → demo → proposal → negotiation → won. Activities and follow-ups hang off it.
Internal or to the customer
Every message says which it is. An internal note can never leak; a reply is always deliberate.
Zero integration
Onboarding a product is DNS for its support address and a workspace row. No SDK, no widget, no code in the product.
Everything is an event
Status history, response times and the pipeline are projections over the event log — analytics without schema work.
How it goes
Three steps.
- 01
Point the mail
Set the MX for support@your-product and verify the address; inbound mail becomes tickets.
- 02
Answer from one inbox
Every product's queue, filterable by workspace, one sign-in through Latchkey.
- 03
Grow the record
Add companies, stages and activities as sales needs them; wardroom mirrors it all as threads.
Questions
Asked already.
Do my customers need an account?
Where do the tickets show up?
Know who is writing.
Tickets, contacts and leads in one record, for every product, from the first email.