Kazakhstan A2P SMS: Sender ID Registration, Compliance and Delivery Guide

Kazakhstan appears in most SMS platforms as a single destination, but sender approval is handled per network. Branded senders are registered with individual mobile operators, and approval on one network tells you nothing about the others.

This guide covers what to confirm before you send A2P SMS into Kazakhstan: sender registration, consent, language, scheduling, encoding and testing.

A large mobile market, with an operator map that recently changed

Kazakhstan's Bureau of National Statistics reported 28.004 million cellular subscriptions in September 2026, including 23.8496 million with internet access. These are subscriptions, not people, and they are not a measure of business message volumes. (Bureau of National Statistics.)

What matters for a launch is who runs which network:

Beeline Kazakhstan. VEON's 2025 annual report records 11.8 million mobile customers at year-end. (VEON annual report.)

Kcell and activ. Kcell reported 9.05 million subscribers for the first half of 2026. Counting activ as a separate operator is a common mistake. (Kcell H1 2026 results.)

Tele2 and Altel. Both brands run on Mobile Telecom-Service, which Kazakhtelecom sold to PIH Communication LLC. The sale completed on 14 January 2025, so an operator map that still lists Tele2/Altel under Kazakhtelecom is out of date. (KASE transaction summary; Interfax.)

Number portability is available, meaning a number's original prefix does not guarantee which network currently serves it. Use MNP (Mobile Number Portability) lookup to identify the current destination operator, improve routing accuracy, apply the correct pricing and sender ID requirements, and analyse delivery performance by actual network. (messaging guidelines; country regulations.)

Register the brand, then confirm where it is active

Provider documentation for Kazakhstan consistently describes pre-registration for branded alphanumeric senders on Beeline, Kcell, Altel and Tele2. (country documentation; destination guide; messaging guidelines.)

Per network:

Beeline. Request confirmation that your exact brand name is approved and enabled on the route you will actually use.

Kcell and activ. Provider documentation describes unregistered names being replaced with a default sender, so confirm your registered identity will be preserved. (country documentation.)

Tele2 and Altel. Name both destinations in the activation request. Approval for one of them does not prove the other.

Provider approaches to shared senders differ. One provider describes a common fallback sender that gets used when no registered signature applies; another forbids generic and numeric sender IDs outright. Neither "shared senders always work" nor "shared senders are always blocked" applies universally across the country. Confirm what recipients on each network will actually see. (sender ID documentation; country regulations.)

Prepare the registration pack before you set a launch date

A typical registration workflow for Kazakhstan asks for the sender identity, company and contact details, use case, monthly volume, opt-in description and message samples. When the link between your company and the requested sender is not obvious, expect to provide evidence of brand rights. (registration guide.)

Exact sender spelling. One provider accepts 3 to 11 alphanumeric characters; another takes the same length but allows some punctuation and requires at least one Latin letter. Check the rules of the provider you actually submit to. (registration guide; sender ID requirements.)

Company identity. Legal name, company or tax ID, registration country, address, website and a responsible contact. At least one provider also asks for your field of activity. (registration guide; country documentation.)

Authority to use the brand. If you send on behalf of another company, prepare written permission. Providers may ask for a letter or contract authorising use of the company name. (sender ID requirements.)

Use cases and representative messages. Keep authentication, service notifications and promotion distinct, and describe how consent is actually collected. (registration guide.)

Destination networks and activation status. Some providers let you choose which operators to connect a personal sender to, and separate their internal review from operator registration. Ask for an explicit record of where your identity is enabled. (sender ID documentation; registration workflow.)

At least one provider's workflow states that international companies can skip its local-company section. That is a statement about that provider's own form. It does not remove provider-specific documentation elsewhere. (registration guide.)

Submission is not activation

Provisioning estimates in current provider documentation range from three weeks to about 30 business days, and some providers count working days rather than calendar weeks. Whatever the number, treat it as an estimate: gate your launch on explicit activation confirmation rather than on the calendar. (messaging guidelines; destination guide; registration workflow.)

Template requirements also vary. One registration workflow asks for message samples during registration, while another provider states that template approval is not required for its service. Ask your provider whether you face a one-time sample review, ongoing template registration, or neither. (registration guide; destination guide.)

Consent: the law is specific, and providers cannot approve it for you

The June 2026 amendment to Kazakhstan's communications rules allows advertising messages when the subscriber has submitted a written application or provided consent through an automated service system using biometric identification. Refusal works the same way under paragraph 65-1: written application or automated service system. Neither "biometrics are always required" nor "any checkbox counts" matches the wording. (Official communications-rules amendment.)

Before you send promotion, have your consent and withdrawal process reviewed against the current text, and keep evidence of both. A provider accepting your registration form is not a legal review of your consent design.

Keep authentication and promotion separate in your product as well. Permission to send a requested login code is not permission to append an offer to it. The advertising rules get their own review. (Communications-rules amendment.)

Language is a legal question for promotion

Article 6(2) of the Advertising Law requires advertising in Kazakh, with Russian and other languages additionally at the advertiser's discretion, subject to listed exceptions. The provision does not expressly mention SMS. Including Kazakh is therefore the defensible starting point for promotional SMS, subject to review of the actual campaign. Recommending Russian-only promotion on the grounds that "everyone understands it" ignores the statutory requirement. (Advertising Law, Article 6.)

Informational messages are a separate matter. Article 37(3-1) of the Communications Law addresses the cellular operator's duty to transmit informational short messages in the state and Russian languages. That operator-facing duty does not, by itself, settle the format of every private OTP. Confirm your implementation with the operator or qualified counsel. (Communications Law, Article 37, legal mirror.)

Schedule in UTC+5, and check whose quiet hours apply

Kazakhstan has used UTC+5 nationwide since 1 March 2024. Set schedules and monitoring in the current local time, not the GMT+6 that still appears on some provider pages. (Official government announcement.)

Provider promotional windows differ. One provider lists a Tele2/Altel advertising restriction from 22:00 to 09:00, with an outdated GMT+6 reference; another's country table lists 21:00 to 09:00 for all networks. Neither is a national curfew; both are provider guidance. Confirm the current window for your provider, product and destination network. (messaging guidelines; country regulations.)

The statutory wording is narrower than either. Paragraph 57(27) of the communications rules, as reproduced in the consolidated legal mirror, requires operators to set a limit on previously unrequested advertising SMS and MMS between 22:00 and 06:00, with exceptions for emergency services. It does not ban all A2P traffic at night, and it does not authorise unsolicited advertising outside that window either. Keep the legal provision and provider policy separate in your planning. (Communications rules, paragraph 57(27), legal mirror.)

Check content acceptance and data flows separately

Provider content restrictions can be broader than the law. Provider country tables commonly list adult, gambling, gaming, political and religious content among restricted categories. Treat these as provider policies: some track statutory bans, such as the Advertising Law's prohibition on bookmaker advertising to subscriber devices, and some are simply house rules. You need both legal review and provider acceptance before launching a sensitive campaign. (country regulations; messaging guidelines; Advertising Law, Article 13, legal mirror.)

Data architecture is its own workstream. The consolidated Personal Data Law mirror describes domestic storage requirements in Article 12(2) and cross-border transfer conditions in Article 16. This research verified the consolidation through a legal mirror, not a complete retrieval of the official text, so have counsel assess what you store, where, and on what legal basis before routing Kazakhstani subscriber data through any overseas platform. Neither "foreign platforms are banned" nor "consent makes any foreign processing fine" matches the evidence. (Personal Data Law, legal mirror; official law reference.)

Test the message the customer will receive

Kazakh and Russian use Cyrillic characters, which generally require UCS-2 encoding: up to 70 characters per single SMS segment and 67 characters per segment in concatenated messages, compared with 160 and 153 characters respectively for GSM-7. (segment documentation; GSM-7 encoding.)

Test the final approved language versions on real handsets: sender preservation, text integrity and multipart reassembly. Concatenation is supported by at least one provider in Kazakhstan with sender-type caveats, and limitations reported on Beeline networks in neighbouring markets should not be assumed here. (messaging guidelines.)

Do not assume replies work. One provider reports two-way SMS as unsupported through its Kazakhstan offering, while another lists short-code replies as available but describes alphanumeric senders as one-way. If your flow depends on customers replying, confirm support before you build it. (destination guide; messaging guidelines.)

Monitor the customer outcome, not only the provider status

What you can do is measure your own flow:

1. Record submission, provider acceptance, delivery receipt and application outcome as separate events, so a problem can be located instead of averaged away.

2. Track verification completion: successful verifications divided by sessions where at least one code was sent. Log resends separately, because retries change the denominator.

3. Measure time at each stage. Time to provider receipt, time to handset in a controlled test, and time to completed verification are different numbers.

4. Compare results by network and by message version. A sender ID that gets rewritten on one network, or a template that segments differently in Kazakh, will hide inside a country-level average.

5. If you build a fallback, test it. An alternative route needs its own sender approvals, and a backup channel needs to actually work for your users.

A low completion rate can have causes other than SMS delivery. Correlate before you diagnose.

Your Kazakhstan launch checklist

1. Document your destination map: Beeline, Kcell/activ and Tele2/Altel, plus any other networks your audience uses.

2. Confirm your exact brand identity and its activation status on every intended provider and network path.

3. Prepare the company, brand-authorisation and use-case pack, and get the current checklist from your provider.

4. Separate sender approval, sample review and template registration. Confirm which of the three applies to you.

5. Get legal sign-off on your promotional consent and opt-out process as implemented, rather than as described in a form.

6. Approve language versions and scheduling windows, in UTC+5, against current provider and network policies.

7. Clear content restrictions and data architecture as two separate reviews.

8. Run handset and end-to-end tests on the final message versions.

9. Define monitoring, escalation and fallback, and keep the activation record for your production route.

Frequently asked questions

Do branded sender IDs need pre-registration in Kazakhstan?

Confirm activation for your intended destinations and route before production, and remember that a shared sender being available is not the same as your own brand being approved. (country documentation; sender ID documentation.)

How long does sender registration take?

There is no national approval deadline. Provider estimates range from three weeks to around 30 business days, sometimes counted in working days. Use your provider's current estimate for planning, then wait for explicit activation confirmation. (messaging guidelines; destination guide.)

Does every SMS template need approval?

It depends on the provider. One registration workflow requests message samples during registration; another states that template approval is not required for its service. Confirm the rule for your product and use case. (registration guide; destination guide.)

Can a foreign company register a sender in Kazakhstan?

At least one provider's workflow accommodates international companies and says they can skip its local-company section. That does not remove provider-specific documentation elsewhere, and it does not replace a review of how you handle subscriber data. (registration guide.)

Can customers reply to a branded SMS in Kazakhstan?

Do not build on that assumption. One provider reports two-way SMS as unsupported through its Kazakhstan offering, while another lists replies on short codes but describes alphanumeric senders as one-way. Confirm product support before designing reply-based flows. (destination guide; messaging guidelines.)

Which language should a campaign in Kazakhstan use?

For promotion, start from the Advertising Law's Kazakh-language requirement and get the actual campaign reviewed. For private informational or OTP formats, confirm how the operator-facing language duty applies to your case. (Advertising Law, Article 6; Communications Law, Article 37, legal mirror.)

Planning a Kazakhstan SMS launch?

Contact Scarpel Telecom to discuss your destination networks, sender registration and test plan: contact@scarpeltele.com.

Scarpel Blog. News and insights

Scarpel Blog. News and insights

Guide to Kazakhstan SMS market

Contact us

Scarpel Blog.
News and insights