---
title: Comms compliance
description: "What Venom Comms enforces for you (STOP and opt-outs, quiet hours in the recipient's time zone, sender-id rules per country, WhatsApp's 24-hour window) and what stays your responsibility."
section: comms
order: 40
audience: [user, operator, builder]
sources: [services/nodejs-cloud/lib/comms/pure.ts, services/nodejs-cloud/lib/comms/service.ts]
features: []
---

Messaging people is regulated, and carriers enforce their own rules on top. Comms builds the common ones into every
send so no caller can forget them. You still need consent to contact people, registrations where your countries ask
for them, and your provider's terms; Comms is not legal advice.

## Opt-outs and STOP

A reply of **STOP** (or STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, OPTOUT) opts that contact out of that channel and gets
one confirmation: "You are unsubscribed and will get no more messages from this number. Reply START to subscribe
again." **START** (or UNSTOP, SUBSCRIBE) opts them back in.

A message or call to an opted-out contact is stored as `blocked` with the reason and never reaches the provider. Admins
add and lift opt-outs on the settings page, applications through `/v1/comms/optouts`, and agents can add one but never
lift one. An opt-out on channel `*` covers every channel, calls included. Urgent profiles do not override opt-outs.

## Quiet hours

Messages and calls from a profile that is not urgent are held while it is night where the recipient is: by default
21:00 to 08:00, set per org. The recipient's time zone is `recipient_tz` when the caller gives it, else the one the
number's country implies (for a country with one zone), else the org's default zone. A held message is `scheduled` and
goes out when quiet hours end. Pages and other **urgent** profiles go out anyway and leave an audit entry
(`comms.quiet_hours_bypassed`).

In the United States telemarketing may not reach people before 8 a.m. or after 9 p.m. their time; other countries
have similar windows. Set yours to the strictest one you send to.

## Sender ids

Some countries refuse an alphanumeric sender ("VENOM") or need it registered first:

| Country | Rule |
|---|---|
| United States | No alphanumeric senders. A 10DLC number (brand and campaign registered), a verified toll-free number or a short code |
| Canada | No alphanumeric senders. A long code, toll-free number or short code |
| China | No alphanumeric senders; templates registered in advance |
| Brazil | An alphanumeric sender is replaced by a number |
| India | Sender ids (headers) and templates registered on a DLT platform |
| Singapore | Registered in the SMS Sender ID Registry; unregistered ones arrive marked "Likely-SCAM" |
| UAE, Saudi Arabia | Registered with the regulator through the provider |
| Indonesia, Philippines | Registered with the carriers |

An alphanumeric sender to a country that refuses one is rejected before the send, with the reason. Senders carry the
countries they serve, so Comms picks a valid one when the caller gives no `from`.

## WhatsApp's 24-hour window

A business may send free-form WhatsApp text only within 24 hours of the person's last message to it. Outside that,
only a **template** approved at Meta through your provider. A conversation shows `session_open`; send `template`
(name, language, parameters) when it is false. Support does this for you: it offers the approved templates, or falls
back to SMS ([Support and People](/docs/comms/support-and-people.md#support)). People must have agreed to get WhatsApp messages from you.

## SMS length and cost

An SMS is 160 characters in the GSM-7 alphabet, or 70 when the text has any other character (an emoji, most
non-Latin scripts). Longer texts are split into parts of 153 or 67, and each part is billed. A message reports its
`segments`.

## Privacy

Message bodies never appear in Venom's logs (only their length), and numbers in logs show only their last four
digits. Bodies are kept in your org's database, like Support's email, and the `message.received` event carries the
text to your webhooks.
