Skip to content
OmniChannels.ai
Menu

Bulk SMS in Lebanon: TRA, Sender ID and Arabic/French Guide

Bulk SMS Lebanon guide: TRA sender ID registration on Alfa and touch, consent and Law 81/2018, Arabic, French and English SMS length, banks and NGO senders.

Updated 10 min read

By OmniChannels.ai Editorial Team · Reviewed by BroadNet Messaging Solutions Team

SMS & OTP

Short answer

To send bulk SMS in Lebanon, use a provider with direct routes to Alfa and touch, register an alphanumeric sender ID (up to 11 characters, Latin or Arabic) before launch, and message only people who gave verifiable opt-in, with a STOP or ايقاف opt-out on every promotion. Keep OTPs separate from promotions, and check Arabic and accented French text for Unicode, which holds 70 characters per message.

On this page
  1. What rules apply to bulk SMS in Lebanon?
  2. What does Law 81 of 2018 mean for SMS marketing?
  3. Which operators carry SMS in Lebanon?
  4. How does sender ID registration work in Lebanon?
  5. How should banks and NGOs separate their traffic?
  6. How do Arabic, French and English affect SMS length?
  7. How do you handle mixed Arabic, French and English audiences?
  8. When should you send?
  9. A worked example: a Beirut NGO
  10. What are the common mistakes?
  11. Launch checklist for Lebanon
  12. How OmniChannels.ai helps

Key takeaways

  • Our regulation data names the Telecommunications Regulatory Authority (TRA) and lists sender ID registration as required, one ID per legal entity per use case, with a typical lead time of 3 to 5 business days.
  • Only two mobile networks carry traffic in our coverage data: Alfa (415-01) and touch (415-03), both with direct routes.
  • Lebanon's Law No. 81 of 2018 gives people a right to object to the processing of their data for marketing and restricts unsolicited marketing emails; it has no dedicated SMS rules, so apply opt-in as the safe standard.
  • French needs care: é, è, ù and à stay in GSM-7, but ç in lowercase, ï, î, ô, ê and â push the whole message to Unicode at 70 characters.
  • Banks and NGOs should keep service notices separate from appeals and promotions, with their own sender IDs and suppression lists.

This guide is for banks, retailers, universities, NGOs and operations teams that want to send business SMS to mobile numbers in Lebanon: OTPs, account alerts, appointment reminders, beneficiary notices and promotions. It explains who regulates what, how sender IDs work on Alfa and touch, what Lebanon's data law means for consent and how Arabic, French and English text affect message length. It is a practical overview, not legal advice; confirm requirements with Lebanese counsel and the operators before launch.

What rules apply to bulk SMS in Lebanon?

Three layers apply: the TRA and the two operators for telecom and sender IDs, Law No. 81 of 2018 for personal data, and your own consent records. There is no statute named for bulk SMS.

Layer What it covers Where to check
TRA and operators (Alfa, touch) Telecom regulation, sender ID set-up, routes, filtering tra.gov.lb
Law No. 81 of 2018 Electronic transactions and personal data; right to object to marketing DLA Piper summary
Our regulation data Opt-in evidence, opt-out, sender ID rules Lebanon sender ID page

Our regulation data records that opt-in must be verifiable (logged source, timestamp, IP and channel), that evidence is kept for the life of the marketing relationship, and that every marketing message carries an opt-out keyword, STOP or ايقاف, honoured network-wide.

What does Law 81 of 2018 mean for SMS marketing?

It gives individuals the right to object to the processing of their data for marketing and forbids unsolicited marketing emails using a real person's name and address, but it does not mention SMS. According to DLA Piper, the spam ban does not apply where the person consented or the address was lawfully obtained through a previous engagement. DLA Piper also notes that Lebanon has no national data protection authority; the Ministry of Economy and Trade issues permits where a declaration is required, and people enforce their rights through the courts.

Practical consequence: the law's wording is built around email, so whether and how it reaches SMS is a question for counsel. The safe operating standard is the one in our regulation data: verifiable opt-in, an opt-out in every promotion and a suppression list you actually apply. Our opt-in consent generator drafts Arabic, French and English wording and opt-in consent across channels shows how to record it.

Which operators carry SMS in Lebanon?

Two mobile networks appear in our coverage data, each with a direct route.

Operator MCC-MNC Route
Alfa 415-01 Direct
touch 415-03 Direct

With two networks, a problem on one affects roughly half your audience, so read delivery reports per operator. The Lebanon market page summarises our channels there, and improving SMS delivery rates shows how to diagnose a weak network.

How does sender ID registration work in Lebanon?

Business SMS uses an alphanumeric sender ID of up to 11 characters, Latin or Arabic. Our regulation data lists registration as required with Alfa and touch, one sender ID per legal entity per use case, with a typical lead time of 3 to 5 business days. Treat that as typical, not guaranteed.

Public sources disagree on how strictly pre-registration is enforced, so we confirm the position on each network when you onboard instead of relying on a general statement.

Step What to do
1. Classify Separate service notices, OTPs and promotional or fundraising traffic
2. Choose names Use your registered name; avoid names that imitate banks, operators or ministries
3. Prepare documents Registration papers for the legal entity and an authorisation letter naming sender IDs and provider
4. Submit Your provider files with the operators and tracks each approval
5. Test Send each traffic type to an Alfa and a touch handset

Draft the letter with the sender ID letter generator and check the position with the sender ID checker. We can prepare and file the registration with you (registrations); approval decisions stay with the operators and regulator. Background: sender ID types explained.

How should banks and NGOs separate their traffic?

Keep OTPs and account or beneficiary notices on a transactional sender ID, and promotions, appeals and campaigns on another. The two audiences below have the same discipline problem: sensitive service messages sharing a channel with outreach.

Sender Service message Outreach message Practice
Bank OTP, payment alert, card notice Loan offer, new product Separate IDs; never include account balances in text
NGO Distribution time, appointment, programme change Fundraising appeal, newsletter Separate IDs and lists; consent for appeals; no sensitive details
Retailer Order status Sale Separate IDs; opt-out on sales

NGOs can add WhatsApp for two-way contact; see WhatsApp for nonprofits and NGOs. For OTP content, read the OTP authentication messages guide.

How do Arabic, French and English affect SMS length?

Arabic is always Unicode (70 characters per message, 67 per part); French and English can stay in GSM-7 (160, 153 per part) only if every letter is in the GSM alphabet. The alphabet includes é, è, ù and à, but not lowercase ç, ï, î, ô, ê or â, so one of those letters switches the whole message to Unicode. See GSM-7 and Unicode SMS.

Encoding Single message Per part when concatenated
GSM 7-bit 160 characters 153
Unicode (UCS-2) 70 characters 67

Synthetic examples from an NGO ("Cedar Aid"), counted against the limits:

Message Encoding Characters Parts
Cedar Aid: distribution tomorrow 9 am at the Saida centre. Bring your ID. Info: cedaraid.example/d GSM-7 98 1
Cedar Aid: Distribution demain a 9h au centre de Saida. Apportez votre piece d'identite. GSM-7 88 1
Cedar Aid: Distribution demain à 9h au centre de Saïda. Apportez votre pièce d'identité. Unicode 88 2
جمعية الأرز: التوزيع غدا الساعة 9 صباحا في مركز صيدا. أحضروا الهوية. Unicode 68 1

The third row is the trap: the single letter ï in "Saïda" changes the encoding, and the same sentence needs two parts. A text with unaccented letters reads fine in French but looks less polished, so decide per message whether the part count or the spelling matters more. Count final copy in the SMS character counter and read SMS character limits and Unicode. For tone, see Arabic customer messaging best practices.

How do you handle mixed Arabic, French and English audiences?

Segment by language preference, collect it at sign-up and send one language per message. A single message that mixes scripts is Unicode, shorter and harder to read. Ask for the preferred language when you collect consent, store it next to the number, and default to Arabic or English where it is unknown. Keep the sender ID in Latin letters if your audience is mixed, since it displays everywhere.

When should you send?

We have not found a regulator-published time-of-day window for promotional SMS in Lebanon, and our regulation data records none. Send promotions in Beirut local daytime, avoid late evenings and early mornings, and let OTPs and alerts run 24/7. The send time planner helps, and SMS marketing rules by country compares markets.

A worked example: a Beirut NGO

"Cedar Aid" (synthetic) runs food distribution in several regions and wants beneficiary notices plus a donor update.

  • It registers two sender IDs, one for beneficiary notices and one for donor messages, and tests both on Alfa and touch.
  • Beneficiaries give their preferred language at registration; donors opt in on the website with a logged timestamp and source.
  • Distribution notices are short, in the beneficiary's language, with no personal details, and go at any hour.
  • Donor updates go only to opted-in numbers in daytime, with a STOP line.
  • Opt-outs feed one suppression list that also covers email.

What are the common mistakes?

  • Mixing appeals into service notices. Beneficiaries must be able to rely on the notice channel.
  • Accents by accident. One ï or ç doubles the cost of a French message.
  • Sensitive details in text. SMS is not private; leave out balances and personal data.
  • No evidence of consent. Law 81 leaves consent thin, so your own records matter more.
  • Ignoring touch or Alfa results. With two networks, one weak route is a big share.
  • Treating lead times as promises.

Launch checklist for Lebanon

  1. Split service, OTP and promotional use cases.
  2. Register one sender ID per use case and wait for both networks.
  3. Build consent wording in the languages you use; store source and timestamp.
  4. Add STOP and ايقاف opt-outs and a shared suppression list.
  5. Count characters in Arabic, French and English; check accents.
  6. Test on Alfa and touch handsets.
  7. Review delivery reports per operator after the first send.

How OmniChannels.ai helps

OmniChannels.ai is powered by BroadNet, which has direct routes to Alfa and touch in our coverage data, and an office in Beirut. BroadNet is licensed in every country where it operates. We prepare and file sender ID registration with you, support Arabic Unicode SMS and give you per-operator delivery reports. For indicative list prices, see the Lebanon SMS pricing page, then book a demo. If you also plan WhatsApp, see the best WhatsApp Business API provider in Lebanon.

Frequently asked questions

Is bulk SMS legal in Lebanon?

Yes. Banks, retailers, NGOs and telecom brands send SMS through licensed routes on Alfa and touch. No single statute is named for bulk SMS, so the practical rules come from the TRA, the operators and Law No. 81 of 2018. Use registered sender IDs, hold documented opt-in for marketing and honour opt-outs. Confirm details with Lebanese counsel.

Do I need to register a sender ID in Lebanon?

Plan on it. Our regulation data lists registration as required with Alfa and touch, one sender ID per legal entity per use case, with a typical lead time of 3 to 5 business days. Public sources disagree about enforcement, so we confirm the current rule on each network at onboarding. Lead times are typical, not guaranteed.

Who regulates SMS in Lebanon?

The Telecommunications Regulatory Authority (TRA) is the regulator named in our regulation data. Alfa and touch apply sender ID and content rules on their networks. Lebanon has no national data protection authority; Law No. 81 of 2018 is enforced through the courts, and some processing needs a declaration to the Ministry of Economy and Trade.

Does Law 81 of 2018 cover marketing SMS?

It gives people the right to object to the processing of their personal data for marketing or promotion, and it forbids unsolicited marketing emails using a real person's name and address unless they consented or the address was lawfully obtained through a prior relationship. It does not mention SMS, so many organisations apply opt-in to texts as the safe standard.

How do Arabic and French affect SMS length in Lebanon?

Arabic is always Unicode: 70 characters per message, 67 per part. French can stay in GSM-7 (160 characters, 153 per part) if you avoid letters outside the alphabet, such as ï, î, ô, ê, â and lowercase ç. One such letter converts the entire message to Unicode, so check accents before you send.

Can NGOs use bulk SMS in Lebanon?

Yes, with the same sender ID, consent and opt-out discipline as businesses. Beneficiary notices such as distribution times are service messages, while fundraising appeals are promotional and need consent. Keep the two on separate IDs and lists, avoid sensitive details in the text and respect people who ask to stop.

Sources

  1. Telecommunications Regulatory Authority (TRA), Lebanon
  2. Data Protection in Lebanon, DLA Piper Data Protection Laws of the World
  3. 3GPP TS 23.038: Alphabets and language-specific information

Keep reading

More guides