Azerbaijan SMS Guide - sms-compliance -

Frequently Asked Questions

Use a reputable SMS provider like Twilio, Sinch, MessageBird, or Plivo, ensuring compliance with local regulations. Alphanumeric sender IDs are recommended, and two-way SMS is generally limited to local businesses.
Alphanumeric sender IDs are fully supported and recommended for best delivery rates. Avoid generic terms like "INFO" or "SMS" to prevent filtering. Short codes are not supported, and domestic long codes aren't available, but international long codes are fully supported and offer a viable alternative for specific use cases like 2FA.
The article does not explain why Azerbaijan doesn't support short codes, it only notes they are not currently supported. Use alphanumeric sender IDs or international long codes instead.
The best practice is between 9:00 AM and 9:00 PM AZT (UTC+4), avoiding religious holidays and late nights. Limit marketing messages to 2-3 per week, spread across different days, and be mindful of Ramadan.
No, sending SMS to landlines in Azerbaijan is not supported and will result in delivery failure with a 400 response and error code 21614. Messages to landlines won't appear in logs and are not charged.
Concatenated messages are supported, with GSM-7 encoding allowing up to 6 segments (918 characters) and UCS-2 allowing up to 3 segments (201 characters). Standard GSM-7 allows 160 characters per segment, while UCS-2 allows 70.
Process opt-out requests (STOP, DAYANDIR, ????????????) within 24 hours, regardless of script (Latin, Cyrillic, Arabic), confirm with a final message, and maintain opt-out lists for at least 5 years. Responses to HELP/K??M??K should provide service information in the requested language.
Explicit written or electronic consent is required before sending marketing messages. It's crucial to clearly state the messaging purpose during the opt-in process, with double opt-in recommended, and maintain consent records for at least two years. Documentation should include timestamp, consent source, acquisition method, and specific services the user agreed to.
While longer messages can be sent using concatenation, aim to keep messages under 160 characters whenever possible to avoid segmentation and ensure the clearest communication.
Prohibited content includes gambling, adult material, unauthorized pharmaceuticals, and political campaigns without authorization. Regulated industries like finance and healthcare have specific requirements for sender identification and confidentiality.
Avoid using URLs from unknown domains, excessive special characters, all caps, and multiple exclamation points. Maintain consistent sender IDs, keep content professional, and use registered domains for links.
Support Azerbaijani, Russian, and English. Use correct encoding (GSM-7 or UCS-2) and consider cultural nuances when crafting your message. Customer support should also be provided in local languages.
Rate limits vary by provider, generally 1-10 messages per second. Implement exponential backoff for retries and consider batch APIs and queue systems for large campaigns to manage throughput effectively.
The article provides examples for Twilio, Sinch, MessageBird, and Plivo. Each requires specific authentication details and offers various features like delivery reports and status callbacks. Ensure to handle Azerbaijani number formatting correctly.
Loading...