---
title: "Bulk SMS in Bolivia: ATT, Sender ID and Consent Guide"
description: "Bulk SMS Bolivia guide: ATT regulator, Entel, Tigo and Viva routes, sender ID lead time, consent under telecom decrees and Spanish text length in GSM-7."
canonical: "https://omnichannels.ai/blog/bulk-sms-bolivia-guide/"
language: "en"
updated: "2026-11-06"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
category: "sms"
primaryQuery: "bulk sms bolivia"
keywords: ["bulk sms bolivia", "sms masivos bolivia", "sender id bolivia", "att bolivia sms", "entel tigo viva sms", "sms marketing bolivia", "otp sms bolivia"]
published: "2026-11-06"
author: "OmniChannels.ai Editorial Team"
reviewer: "BroadNet Messaging Solutions Team"
readingMinutes: 9
answer: "To send bulk SMS in Bolivia, use a provider with routes to Entel, Tigo and Viva, plan for a sender ID lead time of about 10 to 14 business days, and message only people who agreed to hear from you. The regulator is the ATT. Bolivia has no comprehensive data protection law, but telecom decrees require explicit consent for personal data, so keep consent records and offer an opt-out. Plain Spanish without accents fits 160 GSM-7 characters."
takeaways: ["The regulator is the ATT (Autoridad de Regulación y Fiscalización de Telecomunicaciones y Transportes). Our regulation data says sender ID requirements are set by the operators and confirmed by BroadNet during onboarding, with a typical lead time of 10 to 14 business days.", "Three mobile networks appear in our coverage data, all with direct routes: Entel Bolivia (736-02), Tigo Bolivia (736-03) and Viva (736-01).", "Bolivia has no comprehensive data protection law. Telecom-sector decrees require a user's explicit consent before personal data is used, and the Constitution gives a right to challenge misuse of personal data; treat documented opt-in as the rule.", "Alphanumeric sender IDs are supported where the network allows it; some routes substitute a numeric sender, so test the sender ID your customers actually see on each operator.", "Spanish letters such as á, í, ó and ú are not in the default GSM 7-bit alphabet, so one accent moves a message from 160 to 70 characters per part; ñ and é do fit."]
faq: 
  - q: "Is bulk SMS legal in Bolivia?"
    a: "Yes. Businesses send OTPs, alerts and promotions by SMS through operator routes. There is no standalone bulk SMS statute in our sources, so the rules come from the ATT, operator policy and the telecom decrees on personal data. Use a legitimate route, hold consent for marketing and honour opt-outs."
  - q: "Do I need to register a sender ID in Bolivia?"
    a: "Plan on it. Our regulation data says sender ID requirements are set by the operators and that BroadNet confirms them during onboarding, with a typical lead time of 10 to 14 business days. Public sources disagree on which operator needs what, so confirm before launch and test on all three networks."
  - q: "Does Bolivia have a data protection law for SMS marketing?"
    a: "Not a comprehensive one, according to the DLA Piper data protection guide. What exists is the habeas data action in Article 130 of the Constitution and telecom decrees requiring a user's explicit consent for the use of personal data. Treat documented opt-in as mandatory and take local legal advice."
  - q: "Can I use an alphanumeric sender ID in Bolivia?"
    a: "Our regulation data lists alphanumeric IDs where supported, or numeric long codes and short codes. Some routes replace the sender with a numeric one, so send test messages to Entel, Tigo and Viva handsets and check what the recipient sees before you rely on brand display."
  - q: "Do Spanish accents break SMS length?"
    a: "Some do. The default GSM 7-bit alphabet includes ñ, é, ù, ü and a few others, but not á, í, ó or ú. One of those letters switches the whole message to Unicode, where a single message holds 70 characters instead of 160. Check final copy in a character counter."
  - q: "What opt-out keyword should I use in Bolivia?"
    a: "Use a keyword your Spanish-speaking audience will recognise, such as BAJA or STOP, and say it in the message. Our regulation data records STOP as honoured network-wide and one-step. Keep one suppression list across campaigns and channels."
sources: 
  - title: "Autoridad de Regulación y Fiscalización de Telecomunicaciones y Transportes (ATT), Bolivia"
    url: "https://www.att.gob.bo/"
  - title: "Data protection in Bolivia, DLA Piper Data Protection Laws of the World"
    url: "https://www.dlapiperdataprotection.com/?c=BO&c2=GB&t=law"
  - title: "3GPP TS 23.038: Alphabets and language-specific information"
    url: "https://www.3gpp.org/dynareport/23038.htm"
---

# Bulk SMS in Bolivia: ATT, Sender ID and Consent Guide

Canonical: https://omnichannels.ai/blog/bulk-sms-bolivia-guide/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

This guide is for marketing, e-commerce, fintech and operations teams that want to send business SMS to mobile numbers in Bolivia: OTPs, delivery alerts, reminders and promotions. It explains who regulates what, how sender IDs work, what the rules on personal data mean for you and how Spanish text affects message length. It is a practical overview, not legal advice; confirm requirements with Bolivian counsel and the operators before launch.

## What rules apply to bulk SMS in Bolivia?

Three layers apply: the telecom regulator and operator policy, the telecom-sector rules on personal data, and the Constitution's data protection action. There is no single "bulk SMS law" in the sources we reviewed, so the picture is assembled from each.

| Layer | What it covers | Where to check |
|---|---|---|
| ATT and the operators (Entel, Tigo, Viva) | Telecom regulation, sender ID set-up, routes, filtering | [att.gob.bo](https://www.att.gob.bo/) |
| Telecom decrees on personal data | Explicit consent before personal data is used in the telecom sector | [DLA Piper summary](https://www.dlapiperdataprotection.com/?c=BO&c2=GB&t=law) |
| Constitution, Article 130 | Action to challenge improper use of personal data in public or private files | Constitution of Bolivia |

Our regulation data lists the ATT as the regulator and records that sender ID requirements are set by the operators. The rule that matters on launch day is therefore the one your operator route enforces.

## Is there a data protection law that covers SMS marketing?

Bolivia has no comprehensive data protection law. DLA Piper's guide reports that draft laws have been discussed and that protection comes indirectly, through the habeas data action in Article 130 of the Constitution and Supreme Decrees 1391 and 1793, which require a user's written, explicit consent before personal data is used in the telecom sector. The same guide notes no specific law on electronic marketing.

Because the position can change, check the current text before building sign-up flows. Our regulation data adds the operating rule: opt-in must be verifiable, with consent records kept under the local data-protection rules. A safe routine follows:

1. **Capture consent with a record:** the exact wording shown, the date and time, the channel and the number.
2. **Say who is sending and why** at sign-up, for example "Ofertas de Tienda Andina por SMS".
3. **Honour opt-outs immediately** and keep a suppression list across campaigns and channels.
4. **Keep the records** so you can answer a complaint or an operator query.
5. **Do not buy lists.** Purchased numbers carry no consent trail.

For wording, our [opt-in consent generator](/tools/opt-in-consent-generator/) drafts a consent text and the guide to [opt-in consent across channels](/blog/opt-in-consent-multichannel-campaigns/) shows how to record it.

## How do sender IDs work in Bolivia?

A sender ID is the name or number a recipient sees. Our regulation data lists alphanumeric IDs where supported, or numeric long codes and short codes, with requirements set by the operators and confirmed at onboarding. The published lead time is 10 to 14 business days. Treat it as typical, not guaranteed.

Public sources disagree on which Bolivian operator requires registration and which replaces alphanumeric senders with a numeric one. Rather than repeat unverified claims, test: send a sample message to Entel, Tigo and Viva handsets and note what the recipient sees.

| Step | What to do |
|---|---|
| 1. Classify | Decide which traffic is transactional (OTP, alerts) and which is promotional |
| 2. Choose names | Use your registered brand name; avoid names that imitate banks, operators or public bodies |
| 3. Prepare documents | Company registration papers and an authorisation letter naming the sender IDs and your provider |
| 4. Submit | Your provider files with the operators; track each approval |
| 5. Test | Send an OTP and a promotion to all three networks and compare what is displayed |

Our [sender ID letter generator](/tools/sender-id-letter-generator/) drafts the authorisation letter, and the [sender ID checker](/tools/sender-id-checker/) or the [Bolivia sender ID page](/sender-id/bolivia/) show the current position. If you want us to prepare and file the registration with you, see [registrations](/services/registrations/); approval decisions stay with the operators and regulators. For the formats themselves, read our guide to [sender ID types](/blog/sms-sender-id-types-explained/) and the glossary entry on the [alphanumeric sender ID](/glossary/alphanumeric-sender-id/).

## Which operators carry SMS in Bolivia?

Three mobile networks appear in our coverage data, each with a direct route:

| Operator | MCC-MNC |
|---|---|
| Entel Bolivia | 736-02 |
| Tigo Bolivia | 736-03 |
| Viva | 736-01 |

Our regulation data names Entel and Tigo for sender ID rules, while the coverage data also lists Viva. We report that difference to the content owner; in practice, check all three networks. Read delivery reports per operator, not just a blended figure. A healthy overall rate can hide a weak network, and our guide to [improving SMS delivery rates](/blog/sms-not-delivered-improve-delivery-rate/) shows how to diagnose it.

## How should you separate OTP and promotional traffic?

Keep OTPs, order alerts and other service messages on a transactional sender ID and route, and promotions on their own. A promotion inside an OTP puts your login codes at risk if the promotional route is filtered.

| Traffic | Example | Practice |
|---|---|---|
| Transactional | OTP, payment confirmation, delivery alert | No promotion inside; own sender ID; any hour |
| Promotional | Sale, new product, loyalty offer | Consented numbers only; opt-out in the message; daytime schedule |
| Mixed | "Tu pedido salió. Obtén 10% en tu próxima compra" | Avoid; the offer makes it promotional |

For OTP content and security, read our [OTP authentication messages guide](/blog/otp-authentication-messages-guide/).

## How does Spanish text affect SMS length in Bolivia?

Plain Spanish without accents fits the default GSM 7-bit alphabet, so one message holds 160 characters (153 per part when split). That alphabet includes ñ and é, but not á, í, ó or ú, so a single accented vowel switches the whole message to Unicode with 70 characters (67 per part). See [GSM-7](/glossary/gsm-7/), [UCS-2](/glossary/ucs-2/) and [concatenated SMS](/glossary/concatenated-sms/) for definitions.

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

These examples were counted against the limits:

| Message | Encoding | Characters | Parts |
|---|---|---|---|
| `Su codigo es 482913. No lo comparta con nadie. Tienda Andina` | GSM-7 | 60 | 1 |
| `Su código es 482913. No lo comparta con nadie. Tienda Andina` | Unicode | 60 | 1 |
| `Tienda Andina: 2x1 en cafe este sabado en La Paz! Detalles: andina.example/s. No mas? andina.example/baja` | GSM-7 | 105 | 1 |
| `Tienda Andina: 2x1 en café este sábado en La Paz. Detalles: andina.example/s. Baja: andina.example/baja` | Unicode | 103 | 2 |
| `Tienda Andina: tu pedido #1042 llegará mañana antes de las 17:00. Seguimiento: andina.example/p` | Unicode | 95 | 2 |

The second and fourth rows show the trade-off: one accent halves the capacity, and a 103-character promotion becomes two parts. Many brands choose accent-free copy for transactional codes and accept Unicode where correct spelling matters more than cost. Test both in the [SMS character counter](/tools/sms-character-counter/). For other scripts, see [SMS character limits and Unicode](/blog/sms-character-limits-unicode-arabic/).

## When should you send?

We have not found a regulator-published time-of-day window for promotional SMS in Bolivia, and our regulation data records none. Agree sending hours with your provider and the operators, send promotions in local daytime (Bolivia Time, UTC-4) and avoid late evenings. OTPs and alerts can go at any hour. The [send time planner](/tools/send-time-planner/) helps schedule campaigns, and our [SMS marketing rules by country](/blog/sms-marketing-rules-by-country/) article compares hours across markets.

## A worked example: a La Paz coffee chain

"Tienda Andina" (synthetic) has 25 shops and wants OTPs for its loyalty app, order alerts and a weekly promotion.

- It registers two sender IDs, one for transactional and one for promotional traffic, and tests both on Entel, Tigo and Viva handsets.
- It collects consent in the app and at the till, storing the wording, timestamp and number, and shows "Ofertas por SMS" with a clear way to stop.
- OTPs and order alerts use accent-free Spanish at 160 characters or fewer.
- The weekly offer is checked against the suppression list, scheduled for local daytime and sent as one part.
- Opt-outs from replies and the link feed one suppression list that also covers WhatsApp and email.

## What is a launch checklist for Bolivia?

Work through these steps in order before the first campaign:

1. Confirm the traffic types you will send and split them into transactional and promotional.
2. Choose sender names and file the registration through your provider, allowing 10 to 14 business days.
3. Write the consent wording and store each opt-in with timestamp, source and number.
4. Decide Spanish copy rules: accent-free for one-part codes, or accept Unicode and budget for two parts.
5. Add an opt-out line such as "Baja: link" or "STOP" to every promotion.
6. Send test messages to Entel, Tigo and Viva handsets and compare sender display and delivery time.
7. Schedule promotions for local daytime and keep OTPs on their own route.
8. Review per-operator delivery reports after the first send and adjust.

WhatsApp is a useful complement when recipients have opted in and use the app: it suits rich confirmations and conversations, while SMS stays the fallback for OTPs and for people without data. Read how to [send WhatsApp marketing messages](/blog/how-to-send-whatsapp-marketing-messages/) for the opt-in and template rules.

## What are the common mistakes?

- **Assuming no data protection law means no consent duty.** Telecom decrees still require explicit consent for personal data.
- **No consent evidence.** Without a timestamp and source you cannot answer a complaint.
- **Trusting the sender ID display.** Some routes substitute a numeric sender; test per operator.
- **One accent in every message.** It turns a 160-character message into a 70-character one.
- **Mixing OTP and promotion on one sender ID.**
- **Treating lead times as promises.** Plan buffer beyond 10 to 14 business days.

## How OmniChannels.ai helps

OmniChannels.ai is powered by BroadNet, which has direct routes to Entel, Tigo and Viva in our coverage data. We prepare and file sender ID registration with you, support Spanish and English content, and give you per-operator delivery reports, with SMPP 3.4 for high volume. For indicative list prices, see the [Bolivia SMS pricing page](/sms-pricing/bolivia/), then [book a demo](/demo/). Small team? Our [SMS marketing guide for small businesses](/blog/sms-marketing-small-business-guide/) covers the basics.
