A2P SMS regulations in Tunisia.
Compliance with INT rules and sender-ID registration.
A2P SMS to Tunisia is regulated by the Instance Nationale des Télécommunications (INT). Alphanumeric sender IDs pre-registered with INT via the operator. Arabic, French, and Latin scripts supported, with approval typically taking 5-7 business days. Tunisia Personal Data Protection Law applies. BroadNet carries this traffic over direct operator connections.
Who regulates A2P SMS in Tunisia?
Application-to-person messaging to Tunisia is overseen by the Instance Nationale des Télécommunications (INT), which licenses the operators that terminate A2P traffic and sets the conditions those routes run under. BroadNet delivers into Tunisia over direct operator connections — Tunisie Telecom, Ooredoo Tunisia and Orange Tunisia — rather than through resold or grey routes, so the sender ID, the delivery receipt and the audit trail all come back from the licensed path.
- Telecoms regulator: Instance Nationale des Télécommunications (INT).
- Direct operator routes: Tunisie Telecom, Ooredoo Tunisia and Orange Tunisia.
- Sender-ID registration: Alphanumeric sender IDs pre-registered with INT via the operator. Arabic, French, and Latin scripts supported.
- Typical lead time: 5-7 business days.
Sender ID registration in Tunisia
Alphanumeric sender IDs pre-registered with INT via the operator. Arabic, French, and Latin scripts supported. Registration is not a formality — an unregistered or mismatched sender ID is the most common reason otherwise-valid traffic is filtered, and the failure is usually silent rather than a hard rejection. Plan 5-7 business days for approval and register before you need the route, not during a launch.
- Lead time: 5-7 business days.
- BroadNet files sender IDs on your behalf through the INT-licensed operators.
- Arabic / French / EN: All three scripts supported at parity.
- Time to production: Live in 5–15 business days from test-access request to production.
Consent, content and timing rules
Tunisia Personal Data Protection Law applies. Promotional traffic requires opt-in. Operator-side filtering enforces content rules. Promotional traffic requires a consent record you can produce on request, and an opt-out that is honoured immediately and permanently. Transactional messages — one-time passcodes, delivery and account alerts — are treated differently from marketing, but the distinction is decided by the content of the message rather than by how the campaign is labelled.
- INT sender ID: Sender IDs registered via INT-aligned operator framework.
- Arabic / French / EN: All three scripts supported at parity.
- Tunisia DPL: Personal Data Protection Law applies — consent, retention, breach notification.
- Opt-out wording: Every promotional SMS must include opt-out in French or Arabic.
- Data-protection law: Organic Law No. 2004-63 of 27 July 2004, enforced by the INPDP (Instance Nationale de Protection des Données Personnelles).
What this means for your integration
Practically, three things decide whether traffic to Tunisia performs: a registered sender ID on an INT-licensed route, a consent and opt-out record you can evidence, and message content that matches the category it was registered under. BroadNet's compliance engine checks each submission against the Tunisia ruleset before it reaches the operator, so a non-compliant send is rejected back to you rather than filtered silently downstream — which is the difference between a fixable error and traffic that quietly disappears.
- Every message returns a delivery receipt (DLR); BroadNet does not publish per-country delivery percentages.
- Indicative list pricing: EUR 0.038 – 0.06 per message.
- Addressable mobile base: 15M subscribers.
- Tunisia DPL: Personal Data Protection Law applies — consent, retention, breach notification.
- Submit your KYC packTrade licence, authorisation letter and sample messages
- BroadNet files the applicationWith the operators or the regulator, as the market requires
- Review and approvalTypical lead time5-7 business days
- Send under your brandYour approved sender ID on every message
Technical facts for Tunisia
Network codes, message lengths and sender-ID rules in one table. Segment lengths are the GSM standard values (3GPP TS 23.038).
| Mobile country code (MCC) | 605 |
|---|---|
| Dialling code | +216 |
| Operators (MCC-MNC) |
|
| SMS length, GSM-7 (Latin alphabet) | 160 characters in a single SMS; 153 per part when concatenated |
| SMS length, UCS-2 (Arabic, Cyrillic and other scripts) | 70 characters in a single SMS; 67 per part when concatenated |
| Regulator | INT (Instance Nationale des Télécommunications) |
| Sender-ID rules | Alphanumeric sender IDs pre-registered with INT via the operator. Arabic, French, and Latin scripts supported. |
| Sender-ID lead time | 5-7 business days |
Sources
Last reviewed
More on Tunisia
Compare A2P SMS rules across the region.
Each market pairs a regulatory playbook with its live coverage and operator-direct routing detail.
Tunisia rules: promotional vs. transactional SMS
| Capability | Promotional / marketing | Transactional / service (OTP, alerts) |
|---|---|---|
| Registered sender ID required | ||
| Prior consent required | — | |
| Opt-out instruction required | — | |
| Timing restrictions apply | — | |
| Delivery receipts available |
Common questions
Who regulates SMS in Tunisia?
Do I need to register a sender ID for Tunisia?
How long does it take to start sending to Tunisia?
What content and consent rules apply in Tunisia?
What does A2P SMS cost in Tunisia?
What delivery rate should I expect in Tunisia?
Keep exploring
Test first. Go live with confidence.
Test access on request, reply within one business day. Pay-as-you-go in production. Volume pricing from 1M messages/month.