Tajikistan SMS Guide - sms-compliance -

Frequently Asked Questions

Partner with an authorized provider with direct connections to local carriers like MegaFon Tajikistan, Tcell, ZET-Mobile, and Babilon-M. A2P SMS delivery requires this partnership to ensure reliable message delivery across the country's mobile network.
For large-scale messaging, use queuing systems (Redis, RabbitMQ), exponential backoff for retries, schedule campaigns off-peak, and monitor delivery rates. Adjust sending speed as needed and keep batch sizes between 500-1000 messages. The daily limit is 100,000 messages, with a rate limit of 30 per second.
Tajikistan supports concatenated messages (segmented SMS) up to 160 characters for GSM-7 encoding or 70 for Unicode, and alphanumeric sender IDs. Two-way SMS is available via registered long codes and short codes. MMS is not widely supported for A2P communication; instead, send an SMS with a URL.
Pre-registration ensures sender ID preservation and prevents messages from being blocked or replaced. Register through authorized partners connected to Tajik carriers to maintain consistent branding and avoid deliverability issues.
Explicit consent is mandatory before sending commercial messages. Support STOP, CANCEL, and UNSUBSCRIBE in Latin and Cyrillic scripts, plus Tajik, Russian, and English. Process opt-out requests within 24 hours and send a confirmation message.
Use the +992 country code followed by the recipient's mobile number. Number portability is not implemented, so routing depends on the original carrier prefix. SMS to landlines is not supported, so validate numbers before sending.
The recommended time is between 9:00 AM and 8:00 PM local time (UTC+5). Avoid sending during religious holidays and observances. Emergency messages outside these hours should be limited to truly urgent situations.
Restricted content includes religious content (requiring special approval), political messaging, gambling, adult content, cryptocurrency, and unauthorized financial services. Avoid excessive punctuation and special characters in messages.
Yes, with explicit consent. Obtain consent through double opt-in, provide clear information on frequency and content, and maintain records of consent. Respect local regulations on content and timing to avoid message blocking.
Several providers like Twilio, Sinch, MessageBird, and Plivo offer APIs with direct connections to Tajik carriers. Use their documentation and code examples for integration, ensuring proper number formatting and sender ID registration.
Use GSM-7 for Latin characters and UCS-2 (Unicode) for Tajik or Russian characters. This ensures proper display on recipients' devices and avoids character corruption during transmission.
Comply with regulations from the Communications Service under the Government of Tajikistan, particularly regarding content, consent, and data protection. Consult local legal experts and review the resources provided in the article for compliance.
Loading...