# Opt-outs in English and Kinyarwanda, handled for you

> Recipients can reply STOP, hangana or guhagarara, and BWEZE refuses later sends to them. How opt-outs work and what your code should do.

Source: https://sms.bweze.com/blog/opt-outs-in-kinyarwanda/ · Updated 2026-11-17

People in Rwanda do not all reply in English. A recipient who wants your messages to stop might text STOP, or they might text *hangana* or *guhagarara*. BWEZE SMS understands all three.

## How it works

When a recipient replies with an opt-out word, BWEZE records that the number has opted out of messages from your workspace. From then on, a send to that number is refused with HTTP 409 before it reaches a carrier:

```json
{ "error": { "code": "recipient_opted_out", "message": "...", "docs": "https://docs.bweze.com/errors/recipient_opted_out" } }
```

Nothing is sent and nothing is charged. A recipient who changes their mind replies **TUMA** or **START**, and sends to them work again.

| The recipient replies | What happens |
| --- | --- |
| STOP, *hangana* or *guhagarara* | The number opts out of your messages |
| TUMA or START | The number opts back in |

## What the regulator asks

RURA's 2018 regulation on unsolicited commercial communications covers SMS. For commercial messages, it asks senders to:

- identify who sent the message and how to contact them (article 7);
- offer a free way to unsubscribe, based on words like STOP, END, CANCEL, UNSUBSCRIBE or QUIT (articles 9 and 10);
- give that unsubscribe statement in at least two languages used in Rwanda (article 10);
- stop sending within 24 hours of an opt-out (article 11);
- send nothing commercial between 7 PM and 7 AM unless the recipient agreed to it (article 15).

The fine for breaking it is between RWF 50,000 and 500,000 (article 28). Messages that facilitate, complete or confirm a transaction the recipient agreed to, or give account information, are outside it (article 4). A promotion is inside it. Read the regulation itself before you rely on this summary.

## What your code should do

- **Treat `409 recipient_opted_out` as final.** Do not retry it, and do not loop over other templates hoping one gets through. Mark the user's number as opted out in your own records.
- **Offer another way in.** If the message was a sign-in code, show the user another way to verify, such as email, on the same screen.
- **Say how to stop, in two languages.** Commercial messages should tell people they can reply STOP or *hangana*. It costs a few characters, the regulation asks for it, and it keeps the trust that makes people read the next message.
- **Mind the hour.** Schedule promotions between 7 AM and 7 PM.

## Why it is built into the API

Opt-out handling is easy to forget and expensive to get wrong. If every app has to parse replies itself, some will not, and people who asked to stop keep getting messages. Handling it in the API means every BWEZE customer respects an opt-out from the first send, in the languages its recipients use.

The [messaging docs](https://docs.bweze.com/docs/messaging) list every error a send can return. For what a message costs, see [what a verification code costs to send in Rwanda](/blog/what-an-otp-costs/).

## Sources

- [BWEZE docs: Messaging (opt-out)](https://docs.bweze.com/docs/messaging)
- [RURA: Regulation N°001/R/STD-CMR/RURA/018 governing unsolicited commercial communications in Rwanda](https://www.rura.rw/fileadmin/user_upload/RURA/Documents/Consumer_Affairs/Laws_and_Regulations/REGULATION_GOVERNING_UNSOLICITED_COMMERCIAL_COMMUNICATIONS_IN_RWANDA.pdf)
