12. Plans, Usage & Billing
Plans determine limits, feature gates, and how much end-customer answer volume is included. Billing settings are managed in the Studio under Settings -> Plan & Billing.
Assumption: Pricing and plan packaging can change. Treat the in-app billing page as the source of truth for the current commercial offer. This chapter explains the operating model.
What Klariton Measures
Section titled “What Klariton Measures”Klariton tracks usage against organization limits, including:
- BIQ count,
- persona count,
- touchpoint count,
- monthly end-customer answers,
- supported locales,
- team seats,
- AI provider usage and budget caps.
The most important runtime limit is monthly answer volume. An answer is a response served to an end customer through a touchpoint, such as FAQ, Chat Advisor, or Infobox.
Plan Gates
Section titled “Plan Gates”Common gates include:
| Capability | Typical gate |
|---|---|
| More BIQs, personas, and touchpoints | Higher plan tiers |
| Multi-locale touchpoints | Growth or higher |
| Custom branding and powered-by control | Higher plan tiers |
| API keys for public read API | Pro or higher |
| BIQ Voice and compliance tuning | Pro or higher |
| Advanced analytics | Pro or higher |
| Enterprise controls | Custom enterprise agreement |
If a feature is locked, Klariton should show the current setting and explain which plan is required. Locked settings do not silently change behavior.
Usage Caps
Section titled “Usage Caps”Different plans can use different cap behavior:
- Free or trial plans can enforce hard caps.
- Paid plans can allow soft overage, warnings, or top-ups depending on configuration.
- Enterprise plans can use custom contractual limits.
When you approach a limit, check whether the constraint is answer volume, BIQ count, touchpoint count, locales, or team seats. Upgrading the wrong resource will not solve the issue.
Billing Settings
Section titled “Billing Settings”The billing tab shows:
- current organization plan,
- subscription state,
- invoices when available,
- usage or quota context,
- upgrade or downgrade actions when available.
Current product state from the app: Plan and subscription data exist in the Studio. Payment-provider flows, invoice delivery, and commercial migration details may be environment-specific and should be checked in the live billing tab.
Provider Budget
Section titled “Provider Budget”AI provider budgets are configured separately under Settings -> AI provider. This is not the same as your commercial Klariton plan.
Use provider budgets to control:
- daily AI spend,
- provider-specific usage,
- generation and chat cost exposure,
- whether expensive operations should continue when limits are reached.
See Settings for provider configuration and Analytics & Insights for usage reporting.
Best Practices
Section titled “Best Practices”- Start with one live touchpoint and measure real answer volume before scaling.
- Review LLM budget after bulk generation, translation, and chat testing.
- Upgrade when usage repeatedly approaches the limit; use top-ups only for temporary spikes.
- Keep at least two owners/admins who understand billing and API key management.