Price it against your
support reality
Start from the tickets you open and the money you spend today. Set the resolution rate you believe — 95% is our average, not your promise. The bill comes first; the savings claims come with their assumptions attached.
Tickets your team actually opens and handles — not raw question volume.
Your fully-loaded support budget — that's ≈ €3.00 per ticket at this volume.
Share of would-be tickets resolved before your team sees them. 95% is our measured customer average — set the rate you believe until a pilot proves it.
Starter includes 5 seats, Engagement 10. Extra seats are €100 / seat / month.
Advanced assumptions
One ticket's worth of demand often takes more than one answer. Each AI response bills one cent — this sets how many.
Tickets that still reach your team skew complex, so we cost them above your current average.
Used only for the released-capacity estimate, never for the savings math.
Your estimated Theymes bill
≈ € / year plan commitment. The 20% annual discount applies to the plan base — seats and AI answers bill on usage.
Month-to-month, cancel anytime. Annual billing cuts the plan base by 20%.
- Starter plan base
- € / mo
- Extra seats ( × €100)
- € / mo
- AI answers (≈ / mo, first included)
What changes operationally
- Tickets resolved before your team sees them
- / mo
- Tickets still reaching your team
- / mo
- Capacity released — yours to redeploy, not automatic savings
- h / mo ≈ FTE
The budget picture
- Support spend today
- € / mo
- Theymes bill
- € / mo
- Remaining tickets, human-handled (incl. % complexity uplift)
- € / mo
- Projected cost base
- € / mo
"Up to" is deliberate: this is the ceiling if released capacity converts to cost. Whether it becomes budget savings, avoided hiring, or better service on complex cases is your operating decision.
At these inputs Theymes doesn't beat your current spend on cost alone — the case would rest on response times and CX. A pilot is the cheapest way to test that: talk to us.
A pilot runs on your real volume and reports resolution quality, handoff reliability, and actual answer costs — the three things this page can only estimate.
Enterprise is priced on your volume — with a real number to compare
We don't hide Enterprise behind "contact us" theatre. Bring your ticket volume and we'll return a concrete bundle — seat count, AI answer volume, in-ticket AI Agents, integrations, SLAs — with a price you can put next to the Starter and Engagement tabs on this page.
At your inputs: ≈ tickets resolved before your team sees them, ≈ still human-handled each month.
Estimates from your inputs only — nothing here is a quote. AI answers €0.01 each beyond your plan's included volume, extra seats €100 / seat / month. Implementation is guided onboarding (included); your knowledge-base upkeep and QA time are not in this math — full pricing details.
How the math works — and where it stops
A savings calculator you can't argue with is a sales brochure. Every assumption below is adjustable above, and we name what the model deliberately leaves out.
- Your tickets and spend are the baseline
- We start from the tickets you open and the money you spend today — we never multiply raw question counts by a ticket price. Questions that already self-serve or would never have become tickets don't inflate the opportunity; your savings are bounded by what support actually costs you now.
- What “resolved” means
- A question counts as resolved when the customer got their answer and no ticket was opened. If the same customer comes back, that's a new question — it shows up in the AI answer count and the bill, not hidden inside a resolution rate.
- Why the default isn't 95%
- 95% is our measured average across customers, but your result depends on your issue mix, channels, and knowledge quality. The calculator defaults to the Expected scenario (85%) and lets you set any rate — the honest way to find your number is a pilot on your real volume.
- One cent per AI answer
- One AI answer is one response to one customer question — €0.01, billed beyond your plan's included volume (5,000 on Starter, 10,000 on Engagement, then €10 per 1,000). A conversation with three questions is three cents. We never bill per resolution, so a hard question that takes a few turns doesn't multiply your cost.
- Remaining tickets cost more, not less
- When AI absorbs the easy questions, what reaches your team skews complex. The calculator prices remaining tickets above your current average — +25% by default, adjustable — instead of pretending your cost per ticket stays flat.
- Capacity released is not cash saved
- Your payroll doesn't fall because ticket volume did. We report released capacity in agent-hours and full-time equivalents, separately from the budget math. Whether that becomes avoided hiring, faster responses, or more time on complex cases is your operating decision. We also don't count your time maintaining the knowledge base or reviewing AI quality — plan for both.
Don't take the calculator's word for it
Validate these assumptions against your real support volume in a pilot. You'll see demonstrated resolution quality, how human handoffs behave, and what the bill actually looks like — before you commit to anything.