Resources
How to actually do this.
Most of what makes support work is not software. It is deciding what a good answer looks like, who owns what, and when to tell a customer something has gone wrong — so these are written to be useful whether or not you ever buy anything.
Guides
Setting up support that does not lose things.
ReadKnowledge playbook
Writing answers a team and an AI can both trust.
ReadCustomer health playbook
Spotting a relationship going wrong, early.
ReadIncident playbook
One problem, fourteen customers, one message.
ReadAI & customer data
What AI should and should not do with a customer record.
ReadGlossary
Case, incident, problem, promise, health — defined.
ReadHelp Centre
Setup, mailboxes, routing, knowledge and pricing.
ReadDevelopers
The API, the events and what is never exposed.
ReadTrust Centre
Security, customer data, AI permissions and audit.
ReadTake better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]