AI Credits & Billing
RapiDesq meters AI usage in credits — a single unit you can see, budget for, and control. Every plan includes a monthly credit allotment; you can top up when you need more, and auto-refill keeps things moving with a monthly cap you set. Crucially, unused credits from your subscription allotment roll over for one month, so a quiet month earns you a buffer instead of being lost. This guide covers everything about how credits work: what they're consumed for, how rollover works, how to purchase more, how auto-refill is configured, what happens when you run out, and how to monitor usage.
Overview
RapiDesq uses a credit-based AI billing model instead of the per-resolution, per-seat, or per-token models common among other contact center platforms. The design goals:
- Predictable. You know what a month will cost before it starts. No surprise invoices when traffic spikes.
- Transparent. Every AI operation's credit cost is visible in real time on the usage dashboard, broken down by bot, feature, and conversation.
- Customer-favorable on rollover. A quiet month shouldn't punish you. Unused subscription credits roll over one month.
- Under your control. Auto-refill has a monthly cap you set. You cannot be surprised into spending more than you authorized.
- One meter for everything AI. Bot conversations, AI analysis, ticket description generation, and any future AI features all draw from the same credit pool — no juggling separate budgets.
Most AI-enabled contact center platforms (Intercom Fin, Zendesk AI, Gorgias AI, Freshdesk Freddy) bill either per-resolution with strict monthly resets or per-seat with no carry-over. Unused capacity in a quiet month is simply forfeited. RapiDesq lets unused subscription credits roll over one month so a slower period builds up a buffer for the next one. Details below.
What Uses Credits
Any AI-driven operation in the platform consumes credits from the same pool:
| Operation | Description |
|---|---|
| AI bot conversations | Every turn in a customer-facing bot conversation. The bot reads the conversation context, searches the knowledge base, and generates a response. Cost scales with conversation length and complexity. |
| AI analysis on tickets and conversations | Sentiment scoring, urgency scoring, key-point extraction, and classification run as tickets and conversations progress. |
| Ticket description generation | The GenerateTicketDescription node in conversation flows, which produces an AI-authored summary of the conversation before an agent picks up the ticket. |
| AI analyze nodes in flows | Classification, entity extraction, summarization, and routing recommendation inside conversation flows. |
| Conversational flow authoring (when available) | Describing flows in plain language and having the system generate them. Tracked as its own line on the dashboard. |
Everything AI-driven uses credits. Non-AI operations — agents handling tickets, conversation flows running without AI nodes, routing decisions, reporting — do not consume credits.
Plan Allotment
Every paid plan includes a monthly credit allotment. The allotment is tied to your billing cycle — on the first day of each cycle, your account receives the full allotment for that month. The specific allotment depends on your plan (details in your plan's pricing page once pricing is published).
Your plan allotment is the baseline. Most customers never need to think about more than the allotment — AI usage in a typical month fits within it, and rollover absorbs the variance. Top-up purchases and auto-refill are there for customers with higher usage or unusual spikes.
One-Month Credit Rollover
Unused credits from your plan allotment carry over into the next month, once. This is the most unusual part of the RapiDesq credit model and worth understanding in detail.
How it works
- On day 1 of each billing cycle, your account receives your plan's credit allotment.
- Throughout the cycle, you consume credits as AI operations happen. Credits are consumed oldest-first — any rolled-over credits from last month are spent before this month's allotment is touched.
- At the end of the cycle, any credits remaining from this month's allotment roll over into the next cycle and are available during that cycle.
- Rolled-over credits expire at the end of the following cycle if they weren't used — one month carry-forward, not indefinite accumulation.
Example
Imagine a plan with 10,000 included credits per month.
| Month | Allotment received | Credits consumed | Rolled into next month | Notes |
|---|---|---|---|---|
| January | 10,000 | 7,000 | 3,000 | Quiet month; 3,000 of this month's allotment unused. |
| February | 10,000 + 3,000 rolled over = 13,000 usable | 12,000 | 1,000 (from February's allotment, since rolled-over credits were spent first) | Busy month; the rollover from January absorbed the spike. No top-ups needed. |
| March | 10,000 + 1,000 rolled over = 11,000 usable | 6,000 | 4,000 (plus the February carryover is now forfeited if unused) | Quiet month again; February's carryover is gone, but March's own unused credits roll into April. |
The net effect: you get a one-month buffer against usage variance. Months where you use less than your allotment earn you a reserve that absorbs spikes in the following month. A quiet December doesn't forfeit your unused budget; it prepares you for a busy January.
What does and doesn't roll over
- Subscription allotment credits: roll over one month.
- Top-up purchase credits: do not expire at the end of a cycle. Purchased credits stay in your account until used (subject to a longer expiration window, typically 12 months, shown on the usage dashboard).
- Trial credits: expire at the end of your trial. They do not roll over into your paid plan.
- Promotional or bonus credits (from referrals, launch bonuses, etc.): individual expiration dates apply per promotion, shown on the dashboard.
For most customers, rollover means you never need to think about credit budgeting month-to-month. Variance that would force others to over-provision or pay surprise overages just gets absorbed by the buffer. Usage averages out over 2–3 month windows rather than requiring you to match the spikiest month every month.
Top-Up Purchases
When your plan allotment plus rollover isn't enough for a month's usage, you can purchase additional credits at any time.
How it works
- Navigate to Admin > Billing > Credits and select Purchase Credits.
- Choose a credit pack size — packs are offered in several sizes, with larger packs at a slightly lower per-credit rate.
- Complete the purchase using the payment method on file. Purchased credits are available immediately — there's no delay.
Top-up credit lifetime
Top-up credits don't expire at the end of your billing cycle. They stay in your account until used, with a long expiration window (typically 12 months from purchase). This means an occasional large top-up can cover several months of overages without penalty.
Consumption order
When you use credits, the system consumes them in this order:
- Trial credits (if any, until they expire)
- Promotional credits that expire soonest (to avoid waste)
- Rolled-over subscription credits from the previous month (to avoid waste when the current month ends)
- This month's subscription allotment
- Top-up credits (longest expiration window, safest to consume last)
This order means the credits closest to expiring are always spent first. You never lose a credit to expiration when another credit would have expired sooner.
Auto-Refill
Auto-refill automates top-up purchases so you don't have to intervene every time credits run low. Configuration is under Admin > Billing > Credits > Auto-Refill.
How it works
You configure four things:
- Enable / disable. Auto-refill is off by default. You turn it on explicitly.
- Threshold. The credit balance at which auto-refill triggers. For example, "when my balance drops below 500 credits, buy more."
- Refill amount. How many credits to purchase when the threshold is hit. Usually one of the standard top-up pack sizes.
- Monthly cap. The most auto-refill will spend in a single billing cycle. Once the cap is hit, auto-refill stops until the next cycle, even if the balance drops below the threshold again.
Partial purchases near the monthly cap
If a refill would exceed the monthly cap, auto-refill purchases whatever portion of the refill amount fits within the cap, rather than either blowing through the cap or skipping the refill entirely. For example, if your cap has $50 remaining and the standard refill is $100, auto-refill purchases $50 worth of credits.
Notifications
Auto-refill triggers send notifications to billing admins:
- Every successful auto-refill (so you have visibility; there's never a silent purchase)
- When approaching the monthly cap (typically at 80% and 95%)
- When the cap is reached and auto-refill stops
- If auto-refill fails (payment method declined, card expired, etc.)
Auto-refill will not spend more than the cap in a single billing cycle. If usage exceeds what the cap can cover, the account enters the depletion behavior described below rather than silently purchasing more. This is deliberate — a misconfigured bot or a traffic spike should never result in a surprise bill larger than you authorized.
Depletion Behavior
If you run out of credits with auto-refill disabled (or with the monthly cap hit), AI operations enter a graceful depletion mode. This keeps the platform running for non-AI features while preventing surprise charges.
Sequence of events
- Balance warnings. Billing admins receive notifications as the balance approaches zero (typically at 25%, 10%, and 5% remaining).
- At zero credits. New AI operations are deferred. Bot conversations gracefully hand off to humans with a context note; AI analysis runs on tickets only if credits are available; ticket description generation and other in-flow AI features are skipped.
- Non-AI features continue normally. Agents handle tickets, flows run their non-AI nodes, routing works, reporting works. Only AI-specific features are affected.
- Customer-facing experience. If a bot was about to respond when depletion hits, the conversation smoothly transitions to the team that the bot would have escalated to. Customers don't see an error; they see a handoff message.
- Replenishment. At the start of your next billing cycle, the plan allotment is replenished and AI operations resume automatically. If you've purchased top-ups in the interim, those are applied immediately as soon as the purchase completes.
Agent and admin visibility
The usage dashboard shows clear warnings when the balance is low or depleted. Agents see a banner indicating that AI analysis may be skipped on incoming tickets; supervisors see a signal that bot conversations may be routed to humans sooner than usual. There's no silent degradation — your team knows when AI features are paused.
The Usage Dashboard
The usage dashboard is where you see credit consumption in real time. Navigate to Admin > Billing > Credits > Usage.
What the dashboard shows
| Panel | What it shows |
|---|---|
| Current balance | Total credits available right now, broken down into: this month's subscription allotment (remaining), rolled-over credits from last month (remaining), top-up credits (remaining), and promotional or trial credits if any. |
| This cycle's usage | Running total of credits consumed in the current billing cycle, projected forward based on current pace. Gives an early warning if the month is trending hot. |
| Usage by feature | Credits consumed broken down by feature: bot conversations, AI analysis, ticket description generation, flow AI nodes, flow authoring. Helps you understand where spend is going. |
| Usage by bot | If you run multiple bots, consumption per bot. Useful for seeing which bot is the biggest consumer and whether any are behaving anomalously. |
| Historical trend | Consumption over the past several months, with rollover and top-ups overlaid. Useful for identifying trends and seasonal patterns. |
| Auto-refill status | Whether auto-refill is enabled, the threshold, the refill amount, and how much of the monthly cap has been used. |
| Upcoming expirations | Credits approaching expiration and when, so you can prioritize using them or plan for the replenishment. |
Per-conversation credit breakdown
Any individual bot conversation shows its credit consumption in the conversation detail view. Agents who pick up an escalated conversation see what the bot consumed; supervisors reviewing conversations see the same. This ties credit consumption to specific customer interactions so spikes can be traced to specific causes.
Practical Guidance
Most customers don't need to think about it
For typical usage patterns, the plan allotment plus rollover absorbs month-to-month variance. You don't need to set up auto-refill, you don't need to watch the dashboard closely, and you don't need to purchase top-ups. Check the dashboard monthly as part of a regular billing review and that's usually enough.
High-volume customers
If your AI usage consistently exceeds your plan allotment (even accounting for rollover), auto-refill is the right configuration. Set the monthly cap to a number you're comfortable with and let it run. The cap ensures you can't be surprised, and the automation means you don't get interrupted by depleting balances.
If your usage is consistently far above the plan allotment, consider moving to a higher-tier plan. The per-credit rate in higher tiers is typically lower, so if you're going to use a lot of credits regardless, the included allotment in a higher plan is usually cheaper than repeated top-ups.
Spiky usage
If your usage varies a lot month-to-month — for example, a seasonal business or a product with event-driven traffic — rollover works in your favor. A light month builds a reserve that absorbs the next busy month. You may not need auto-refill at all if the pattern stays within the rollover buffer.
When to monitor closely
- In the first 1–2 months after launching a new bot or rolling out AI to a new channel, to understand what its baseline usage looks like
- During any significant product change, marketing campaign, or traffic spike
- When auto-refill approaches the monthly cap, to decide whether to raise the cap
- When the usage-by-feature breakdown shows something unexpected — a 10x jump in flow authoring usage might indicate an admin experimenting, for example
Frequently Asked Questions
Why credits instead of per-resolution pricing?
Per-resolution pricing (charging for each customer question the bot answers) aligns incentives to make the bot resolve things, but it's also highly unpredictable — traffic spikes produce invoice spikes. Credits are a stable unit that can be budgeted in advance. The platform's incentive to make bots resolve well is still there (customers stay if bots work), just without imposing unpredictable costs on you.
What happens if I use more credits than my plan allotment and rollover allow?
If auto-refill is enabled, additional credits are purchased up to the monthly cap. If auto-refill is disabled or the cap is reached, AI operations gracefully pause (bots hand off to humans, AI analysis is skipped) until the next billing cycle or a manual top-up purchase.
What happens if I forget to enable auto-refill?
Nothing catastrophic. You'll receive balance warnings as you approach zero. If you do run out, AI features pause but the rest of the platform keeps working. You can purchase a top-up at any time and credits are available immediately.
Can I change the auto-refill cap mid-cycle?
Yes, at any time. The new cap applies from that moment onward in the current cycle. Past auto-refill purchases count against the new cap (so raising the cap mid-cycle effectively gives you headroom for the rest of the cycle).
What about trial credits?
New accounts start with a trial credit allotment to let you evaluate AI features before committing. Trial credits have their own expiration (typically at the end of the trial period) and don't roll over into paid plans.
How much does one AI operation cost in credits?
It depends on the operation's complexity and the model used. A simple bot response (a short question with a short answer) costs less than a long multi-turn conversation that involves knowledge base searches and complex reasoning. The credit pricing table is published in your admin settings and broken down per operation type, so you can always look up what you're being charged.
Can unused credits roll over more than one month?
No. The rollover is one cycle only. This is a deliberate design choice: the point of rollover is to absorb month-to-month variance, not to allow accumulation. If you consistently use far less than your allotment, you should consider a smaller plan.
Related Topics
- AI Bot Configuration — how to set up the bots that consume credits during customer conversations.
- Knowledge Base — what content the bot searches; directly affects how efficiently credits are used.
- Conversation Flows — how AI-driven flow nodes (BotConversation, AiAnalyze, GenerateTicketDescription) consume credits.