Key takeaways
- Transactional messages respond to something the person did or needs: a code, a receipt, a delivery update.
- Marketing messages promote something, and generally need prior consent.
- The category affects consent, sender rules, routes, timing and sometimes price.
- When a message does both, treat it as marketing, or send the two separately.
The categories
| Type | Examples | Consent and rules |
|---|---|---|
| Transactional | One-time codes, payment confirmations, delivery updates, security alerts | Usually tied to an action or a service; rules vary by country |
| Service or informational | Appointment reminders, account notices, outage information | Generally allowed for existing relationships, with limits |
| Marketing or promotional | Offers, campaigns, new products, discount codes | Generally need prior consent, with an easy opt-out |
Why operators and regulators care
- Consent: marketing generally needs it, transactional messages often do not
- Sender rules: some countries require different registration for the two kinds
- Timing: some places restrict when marketing may be sent
- Routes and filtering: operators may filter promotional content harder, and routes can differ by type
- Reputation: a mix can lead to filtering that also hits your codes
Grey areas
Real messages are often mixed. A delivery notification with a coupon, a reminder that ends with an offer, or an account notice that pushes an upgrade all start as service messages and end up as marketing.
A safe rule is to look at the main purpose. If a message exists to sell or promote, treat it as marketing, even when it is dressed as a notice. Where a message does both, either separate the two or apply the stricter rule.
How to organise it
- Use separate senders or number ranges for transactional and marketing traffic
- Keep promotion out of one-time codes and security alerts
- Tag every message with its category in your own system
- Apply opt-out and timing rules to marketing automatically
- Check the local definition per country, since they are not identical
How ZafeConnect fits
ZafeConnect supports local SenderID registration and local regulatory handling in the countries it serves. Tell us your message types and destinations, and we will confirm how each is treated. This is general information and not legal advice.