AI assistant and SMS monthly quotas
Every subscription plan carries two monthly allowances: tokens for the Dibee AI assistant and SMS messages the platform sends on an organisation's behalf. This page lists the allowances, what counts against them, and what happens when one runs out.
Overview#
A plan sets two monthly caps: one on AI assistant usage, measured in tokens, and one on SMS messages. The platform counts usage per organisation (a tenant or a merchant) per calendar month and refuses further use once the cap is reached. A blank cap means unlimited. Quotas limit use; they are never billed and there is no overage charge. For which modules a plan unlocks, see Subscription plans and features.
Allowances per plan#
| Plan type | AI assistant tokens per month | SMS per month |
|---|---|---|
| Professional (tenant or merchant) | 2,000,000 | 2,000 |
| Enterprise (tenant or merchant) | Unlimited | Unlimited |
The same figures apply to tenant and merchant plans of the same type. No free plan is set up. The caps belong to the plan, so a platform operator who changes a plan's caps changes them for every organisation on that plan.
Rules#
Who is counted#
- AI assistant usage counts against the user's organisation and notification SMS against the recipient's: the tenant, or the merchant when the person belongs to no tenant. E-voucher SMS always count against the tenant that runs the campaign.
- The cap comes from the plan of the organisation's Active subscription; allowances apply only while a subscription is Active.
- Usage that belongs to no organisation, such as a message to a platform staff member, is sent and not counted.
- Unlimited plans are counted too, so usage is recorded even when it is never refused.
The month#
- The month runs on Vietnam time (UTC+7). Usage at 23:30 on 31 August counts towards August; usage at 00:30 on 1 September starts September's count at zero.
- Nothing carries over: an unused allowance does not roll into the next month.
SMS#
| Message | Counted? |
|---|---|
| Verification code (sign-in, transaction confirmation or password reset) | Never counted, never refused |
| Notification sent by SMS | Counted against the recipient's organisation |
| E-voucher code sent to a beneficiary | Counted against the tenant that runs the voucher campaign |
- Each message counts as one, and it is counted before it is sent. When the month's allowance is used up, the message is not sent.
- If the SMS provider fails to deliver the message, the count is given back, so a provider outage does not use up the allowance.
- Verification codes are exempt so that a used-up allowance can never lock anyone out of their account.
AI assistant#
- Each reply is counted after it finishes, as all the tokens the AI provider processed to produce the reply, including the conversation so far and any look-ups the assistant made.
- Because a reply's cost is only known once it is complete, the reply that crosses the limit is finished and counted, and the next question is refused. An organisation can therefore go over its cap by up to one reply.
- A reply that is cut off part-way (a timeout, or the user leaving the page) is counted for the tokens it used up to that point.
- Platform staff who belong to no organisation are never limited.
What users see#
| Allowance | When it runs out |
|---|---|
| AI assistant | The chat box is disabled and shows "Your organisation has used all of its Dibee allowance for this month. It will reset next month." The notice has no retry option. The box stays disabled until the allowance is available again: at the start of the next month, or sooner if the plan's cap is raised; a page that was already open must be reloaded. |
| SMS (notification) | The SMS is not sent, so the recipient gets nothing by SMS. |
| SMS (e-voucher) | The voucher code SMS is not sent; on the campaign page, the voucher's Last Delivery under Vouchers & Delivery shows Failed. |
No warning is given before an allowance runs out: the first sign is the refusal itself.
Edge cases#
- A message at exactly the limit. At 2,000 of 2,000 SMS used, the allowance is spent and the next counted message is refused.
- A user who belongs to both a tenant and a merchant. Their usage counts against the tenant.