Pricing
Per person on your team. Not per customer.
Support shouldn’t become more expensive because customers talk to you. Nothing here is charged per conversation, per ticket, per AI request or per automation.
Start
For small teams who want nothing to fall through.
Per team member, per month. Minimum two.
Two to about eight people handling customers alongside other work.
- Shared inbox with customer context
- Cases, owners and the full timeline
- Customer memory and service history
- Promises — every commitment tracked
- Verified knowledge and a help centre
- AI suggestions on every reply
- Unlimited AI — never metered, on any tier
Grow
For teams where support has become somebody's actual job.
Per team member, per month. Minimum four.
Roughly five to twenty people, usually with one support lead.
- Everything in Start
- Customer health with explained states
- SLAs, response targets and breach warnings
- The customer portal, on your own domain
- Routing by responsibility, skill and availability
- Insights: demand, gaps and repeat contact
- Approved AI actions, per category
Scale
For teams who now get asked to evidence things.
Per team member, per month. Minimum ten.
Twenty people and up, several brands or sites, or regulated service obligations.
- Everything in Grow
- Incidents, problems and root-cause tracking
- Customer success plans and renewals
- Customer voice and feature demand
- Advanced permissions and sensitive-case controls
- Full audit trail with export
- Multiple brands, mailboxes and teams
Enterprise
For requirements that do not fit a tier.
Quoted against your requirements.
Specific residency, retention, contractual or integration requirements.
- Everything in Scale
- Data residency commitments
- Custom retention and legal hold
- Named subprocessor list in the agreement
- Bespoke integrations and migration support
- Defined service levels
- A named contact who knows your setup
Billing is per team member per month — somebody who works cases. Customers, their contacts, and colleagues who only receive a notification or approve the occasional internal action are never counted, because counting them is how a per-seat price quietly becomes a per-customer one. Nothing is charged per conversation, per ticket, per AI request or per automation: support should not become more expensive because your customers talked to you, and a product that charges you per question is a product your team stops asking. What moves the figure is how many people work cases, which tier you need, and whether you are on an annual agreement. Ask and you will get a number, not a discovery call.
What is not charged for
Three things you will not find on the invoice.
Conversations
A busy month costs the same as a quiet one. Per-ticket or per-conversation pricing charges you most precisely when your customers need you most.
Your customers
Billing counts people who work cases. Customers, their contacts, and colleagues who only approve the occasional internal action are never counted.
AI requests
Never metered, on any tier. A team that rations asking about its own customers is a team getting no value from the AI at all.
Questions
About pricing.
What size of company is this for?
Roughly five to a hundred people, with anywhere from two to twenty handling customers. Below that a shared mailbox genuinely works. Above it you will start wanting things this deliberately does not do — workforce management, call-centre routing, enterprise ITSM. The sweet spot is a company that has outgrown the mailbox and does not want a contact centre.
How is it priced?
Per team member per month — somebody who works cases. Customers, their contacts and colleagues who only approve the occasional internal action are never counted. Nothing is charged per conversation, per ticket, per AI request or per automation.
Is the AI metered?
No, on any tier. Charging per AI request means your team rations asking, which defeats the purpose, and it means a busy month costs more precisely when you can least afford it. Which model handles which task is our problem and is not a line on your bill.
Can we get our data out?
Yes, as a matter of course rather than as a negotiation. Cases, conversations, customer records and knowledge are exportable on every tier, throughout the term and during any wind-down. A support platform that makes leaving difficult has made its problem into yours.
Anything else, write to [email protected] and you will get a number rather than a discovery call.
Start with the mailbox you already have.
Connect the mailbox your customers already write to, and the first conversations arrive with their history attached.
Keep the mailbox you already use · The AI is never metered · [email protected]