Phone number verification is the least noticed line in a product budget. While you have a hundred users, nobody counts it. Once there are tens of thousands, it turns out the company pays millions of tenge a year just so people can sign in to their own accounts.
The most frustrating part is that it pays out of habit. Almost every verification integration in Kazakhstan starts and ends with one channel: SMS. Yet a code can be delivered by voice 2 times cheaper, and by a missed call 6 times cheaper.
What “just sending a code” really costs
On the popular discounted AutoCall.kz plan, one SMS costs 23.25 ₸. Multiply it by your monthly volume and the number gets unpleasant:
| Verifications per month | SMS only | Per year |
|---|---|---|
| 1 000 | 23 250 ₸ | 279 000 ₸ |
| 10 000 | 232 500 ₸ | 2 790 000 ₸ |
| 50 000 | 1 162 500 ₸ | 13 950 000 ₸ |
And this cost grows in step with the product’s success. The more users you have, the more you pay for the right to recognize them.
The first thought is usually: “SMS is expensive, so let’s replace it entirely with something cheap.” That is a trap. Any cheap channel delivers a bit worse than an expensive one, and saving on verification turns into lost sign-ups, which cost far more than the price difference.
The right question is “in what order to try the channels”, not “which channel to choose”. The cheap channel goes first, the expensive one last. And you pay for the expensive one only when the cheap one really failed.
Three-step verification
The idea is simple: the user gets the code the cheapest way. If the code does not arrive, they tap “Send again” and you move one step up. This continues until SMS, which is almost certain to arrive.
The key point is that only a minority reaches the upper steps. The business pays for the first step for everyone and for the expensive one for just a few.
The user gets an incoming call that hangs up right away. The code is the last digits of the caller’s number. There is no need to answer, nothing for the contact to pay, and it arrives in 3–10 seconds. It is the cheapest way to deliver a code, period.
A robot calls and reads the code aloud twice. It works where Flash Call did not: the user did not see the screen, has an anti-spam filter on unknown numbers, or simply did not understand what the missed call was. It is also the only method available to visually impaired people and convenient while driving.
The most expensive and most reliable channel. The message stays on the phone, it can be reread and copied, and iOS and Android fill in the code automatically. That is exactly why SMS is a safety net for when everything else failed, rather than the first step.
Step 1: Flash Call
One request. The response contains code: save it on your side and compare it with what the user enters.
Authorization: Bearer {your_token}
Content-Type: application/json
{
"number": "+77010000000",
"digits": 4 // code length, 3–6 digits
}
{
"id": 11223,
"code": "7482", // this is the code, save it on your side
"number": "+77010000000"
}
The user sees an incoming call from a number like +7 708 123 7482 and enters the last four digits. That’s it.
Use the auto code. There is a second mode where you set the code yourself ("code": "7482"), but then we have to find a free number in the pool that ends in exactly those digits, and we may not find one. The auto code always works and costs less.
Step 2: voice call
The user tapped “Resend code”, so we move one step up. Here we synthesize a short recording with the code and call.
Authorization: Bearer {your_token}
Content-Type: application/json
{
"name": "OTP verification",
"type": "regular",
"audio_id": [{
"type": "synthesis",
"data": {
"text": "Verification code: 7 4 8 2. Once again: 7 4 8 2."
}
}],
"list_id": [
{ "number": "+77010000000" }
]
}
Note the text: the digits are listed separately and repeated twice. This way the synthesizer pronounces them one by one, not as the number “seven thousand four hundred eighty-two”, and the user gets a second chance to hear them.
What the price is made of: ~7 seconds of call time at 0.56 ₸ plus 5 ₸ for synthesizing the recording. Synthesis is a separate line because each user has their own code, so the recording has to be generated anew for every call.
Step 3: SMS
If the code did not get through by voice either, we send an SMS. There is no point saving at this step: what matters is that the person finally signs in.
Authorization: Bearer {your_token}
Content-Type: application/json
{
"name": "OTP verification",
"text": "Verification code: 7482. Do not share it with anyone.",
"list_id": [
{ "number": "+77010000000" }
]
}
Watch the text length. An SMS in Cyrillic holds 70 characters; anything longer is billed as two or more messages. “Verification code: 7482. Do not share it with anyone.” fits into one, but a long greeting with the company name no longer does.
Calculating the savings
Plug in your own numbers. The shares are easy to measure in your analytics: how many users tap “send again” at each step.
The default values are just round numbers for the example, not our statistics. But even with pessimistic shares the cascade wins: at the first step you pay a few tenge for everyone, and tens of tenge only for a small remainder.
What it looks like in code
The logic lives entirely on your side and fits into a few lines:
- When a verification request is created, start an attempt counter for that number (in Redis, in the session, wherever is convenient).
- Attempt 1 →
POST /api/v1/flash-calls. Savecodefrom the response. - Attempt 2 →
POST /api/v1/autocallswith the same code. - Attempt 3 and later →
POST /api/v1/bulks. - The code lives 3–5 minutes, with no more than five entry attempts. After that, start over.
A couple of practical details that save you headaches:
- Lock the “send again” button for 60 seconds. Otherwise the user will tap it three times in a row and you will pay for three steps for one verification.
- Do not change the code between steps. The person may have spotted the Flash Call number after all and be typing exactly those digits. A new code will confuse them.
- Flash Call has a limit: no more than 3 requests per number in 5 minutes. It protects against brute force, and it will also save you from a buggy retry in your own code.
- Explain to the user what is happening. “You will get a short call, no need to answer. Enter the last 4 digits of the number” removes almost all questions about the first step.
When you do not need a cascade
To be honest, not everyone needs it. If you have a couple hundred verifications a month, the savings will not pay for a developer’s day of work, so stay on SMS. The cascade starts paying off at around a few thousand verifications a month, and at tens of thousands it becomes the obvious choice.
Another case for skipping the first step: your audience is not technical at all and a call from an unknown number scares them. Then start right away with the voice call. It is still cheaper than SMS.
Conclusion
Verification is a sequence, not a “channel”. The same code can be delivered for 3.5 ₸ or for 23.25 ₸. The only question is whether you start with the cheap one or the expensive one.
In AutoCall.kz all three methods live in one service, behind one API token and on one balance. No need to connect three providers and reconcile three invoices: just switch the endpoint depending on the attempt number.
Each method is described in detail on the verification codes page, and the full specification is in OpenAPI.