Core
$500 / month · USD
Monthly estimate
2,500–10,000
customer messages / month
1× capacity · shared workspace usage
Discuss Core← Monthly usage packagesSee how much work
Usage guide
See how much work
your package could handle.
From answering customers to taking care of routine requests, put your monthly capacity into everyday terms.
Explore customer support estimatesCustomer support
Thousands of messages.
A clearer starting point.
Estimated monthly ranges when your workspace dedicates its package to customer support. Actual capacity depends on the work each reply needs.
Growth
$5,000 / month · USD
Monthly estimate
25,000–100,000
customer messages / month
10× capacity · shared workspace usage
Discuss GrowthScale
$10,000 / month · USD
Monthly estimate
100,000–400,000
customer messages / month
40× capacity · shared workspace usage
Discuss ScaleThese are planning examples, not measured benchmarks or guaranteed message allowances. Growth and Scale extend the Core example using the same workload assumptions and their capacity multipliers.
What counts as a message here?
One incoming customer message handled with one AI reply. A conversation can contain several messages; each follow-up is another exchange. This example does not count unique customers or promise a resolved ticket.
Why show a range?
A short FAQ reply can take less work than an answer that reads a long conversation, checks records and takes follow-up actions. Your mix of requests determines how far capacity goes.
Beyond the inbox
Use capacity for the work
that keeps repeating.
The same package can support routine operations. Estimate these by the request completed, with a range based on the steps your workflow actually needs.
Ticket triage
Keep requests moving.
Read an incoming request, identify its topic and urgency, then route it to the right person.
Plan around tickets processed.Long threads, attachments and extra lookups can use more capacity than a short classification.
CRM and follow-up
Keep records up to date.
Read an email, update the relevant record and prepare a follow-up or confirmation.
Plan around completed requests.A request that updates several systems takes more work than a single record change.
Document processing
Turn documents into usable information.
Read a form or document, extract the important fields and flag items that need review.
Plan around documents processed.Length, scanned pages and the checks required affect consumption. Documents are not interchangeable with messages.
One package, shared across your work
Choose your mix.
Keep the value in view.
Support replies, CRM updates and document processing draw from the same workspace capacity. If you use some of it for routine tasks, less remains for support messages. Separate workload examples are not extra allowances you can add together.
We use your request mix to refine the estimate, then review consumption and cost drivers. Where AI adds too little value, we recommend simpler automation or removing that workload.
Plan around your business
What does a typical month
look like for your team?
Share your message volume, recurring tasks and a few representative examples. We’ll help estimate the capacity your workload needs.
Estimate my workload