SMS Credit Allocation for Review Requests
Text-based review requests only work if the credits behind them reach the right client at the right time. Where a review-request platform offers SMS credit allocation, that balance stops being one undivided figure for the whole account: credits are assigned to named clients and locations, usage is tracked per recipient, and extra credits can be added before the period closes. This guide explains the mechanics and how to plan a split. Whether your platform supports it, and on which plans, is a question for the provider — see the owner-supplied details below.
What SMS credit allocation does
Where the capability is available, allocation lets you decide manually how many SMS credits each client and each location may draw on. Rather than a single balance covering the whole account, you set a share per recipient based on how many review requests they typically send. Each client then works from its own allowance, so a busy location cannot quietly consume credits another client needs.
The same view also shows how many credits each client or location has used. That makes it possible to see who is running ahead of plan and to add credits to those accounts before the period ends, rather than discovering the shortfall after requests have already failed to send.
These behaviours are described from the captured feature announcement. Confirm current availability, plan inclusion and the definition of a credit with the platform owner before relying on them.
Choosing an allocation model
There is no single correct split. The right model depends on how predictable each client's sending is and how much freedom you want to keep in reserve. Use this checklist to pick one:
- Even split. Divide the balance equally across clients. Simple to explain and fair when sending volumes are similar, but it can starve a client with a genuinely larger customer base.
- Usage-based split. Give each client a share that matches its recent sending pattern. Better fit for mixed portfolios, but it needs a usage review before each period.
- Hybrid. Set a baseline for every client and hold a small unallocated reserve for spikes. This keeps the shared-balance risk low without freezing the whole amount.
Whichever model you choose, record the basis for each allocation. When a client asks why its allowance differs from another's, the answer should be a usage figure, not a guess.
Worked example: two clients, one heavy sender
Suppose an account holds a single SMS credit balance and serves two clients, A and B. Client A sends review requests to a large customer list each week; client B sends a smaller, steadier volume. Without allocation, A can draw the balance down early in the period and B's later requests have nothing behind them.
With allocation in place, you assign A a larger share and B a smaller one, both based on their typical usage. Mid-period, the usage view shows A has nearly exhausted its allowance while B is comfortably within its own. You top up A's allocation before the period ends. B's credits are untouched, so its review requests continue as planned. The point of the example is not the specific numbers but the sequence: allocate, watch usage, top up the client that needs it, and leave the others alone.
Three different reasons a review request does not go out
Teams often treat every failed text as a credit problem. It helps to separate the causes:
- The client's allocated credits are exhausted. The account balance may still hold credits, but this client's share is used up. The fix is a top-up to that client's allocation, not a change to the whole account.
- The account balance is exhausted. Every client's allowance has been drawn down and there is nothing left to allocate. The fix is at account level, before any per-client adjustment.
- Credits are available but no request was sent. Allocation is not the cause here; the campaign itself did not produce a send. Check the campaign setup rather than adding credits.
Naming the right cause first avoids the common mistake of buying more credits when the real issue is an allocation that was never set.
What the allocation view needs to show
A workable allocation screen answers five questions per client and location:
- Client. Which account owns this allowance?
- Location. Which specific location draws on it, where a client has more than one?
- Allocated amount. How many SMS credits this recipient may use in the period.
- Used amount. How many have actually been consumed so far.
- Remaining and top-up. What is left, and how many extra credits have been added mid-period.
If any of these is missing, the person managing the account is guessing. The used-versus-allocated comparison is the one that drives the mid-period top-up decision.
Frequently asked questions
Who sets the SMS credit allocation?
Where the feature is offered, allocation is manual: you assign credits to clients and locations yourself, based on their typical usage. The platform does not decide a split for you. Confirm the exact behaviour with your provider.
When should I top up a client's credits?
Watch the usage figures during the period. When a client or location is close to using its full allocation, add credits before the period ends so its review requests are not interrupted.
Can credits be allocated per location rather than only per client?
The captured announcement describes allocation at both client and location level, so a multi-location client can have separate allowances per site. Verify this against your provider's current documentation.
Does allocation remove the shared balance entirely?
No. Credits still sit in an account-level balance; allocation controls how much of that balance each client and location may draw on. That is why a client can hit its own limit while the account still holds credits.