§ SMS
SMS in Brazil, with the tedious compliance part already solved
An SMS campaign run end to end by our team — consent checked, your account's opt-out list applied before every send, and the carrier's report at the end. Because in Brazil, getting this wrong costs up to 2% of revenue.
- Recorded, auditable consent
- Account-wide opt-out applied before every send
- Run end to end by our team
R$ 50M
cap on a single LGPD fine
ANPD · LGPD, art. 52
2%
of Brazilian revenue — how that same fine is calculated
ANPD · LGPD, art. 52
145M
active RCS users in Brazil
Mobile Time · Jun 2026
The channel is cheap. Getting it wrong is not.
SMS costs cents per send, which tempts people to treat their list as disposable. But commercial messaging in Brazil requires prior, free, informed and revocable consent — and the ANPD, which became a regulatory agency in 2026, opened 19 new sanctioning proceedings in June alone. The risk is not in the send; it is in where the list came from and whether you can prove consent.
How we work
- 01
Lists arrive with provenance
Before we schedule a send, we check every contact for consent source, date and the version of the text they accepted. Without those three fields there is no proof of compliance — and that is exactly what the authority asks for.
- 02
Opt-out covers the whole account, and we are the ones who apply it
Anyone who asks to leave goes onto your account's opt-out list. We apply that list before every send, across all of your campaigns — it is not a per-campaign list, and leaving holds until the person asks to come back.
- 03
We are the ones running the campaign
You send the list and the message; we clean it, fit the copy to the channel, schedule it inside the permitted window and send. There is no self-service console and no API for you to send on your own — this is an operated service, from brief to report.
- 04
The carrier's report, not an estimate
Sent, delivered, failed and unsubscribed: at the end of each campaign we hand over the delivery report the carrier returns, rather than a figure we estimated.
What's included
- List import and cleaning, with deduplication
- Consent record check (source, date, text version)
- Account-wide opt-out list, applied by us before every send
- Message copywriting and channel fit
- Scheduling and sending by our team, inside permitted sending windows
- The carrier's delivery report at the end of each campaign
Who this is for
It fits if
- You own a list with traceable consent origin
- You need universal reach that does not depend on an app
- You would rather a team ran the whole campaign than operate a tool
- You want to start on SMS now and look at RCS when we open it
It doesn't fit if
- The list was purchased or its origin cannot be evidenced
- The plan is to message people who never asked to hear from you
- You need an inbound support channel, not outbound sending
- You want a console to send on your own, on the spot
Frequently asked questions
- Can I use a list I bought?
- We do not work with purchased lists. Commercial messaging in Brazil requires prior consent from the individual, and a purchased list cannot evidence that. If your list's origin is uncertain, the path is a re-confirmation campaign before any commercial send.
- Do you deliver RCS as well?
- Not today. What we sell and deliver is SMS. RCS reaches compatible devices — 135 million in Brazil — with images, buttons, rich links and replies inside the conversation, and it is the channel we want to open next. But it has no price yet, it cannot go into a proposal, and there is no automatic fallback between the two: when it is ready, we will announce it as a service of its own.
- How does opt-out work?
- Every message carries exit instructions. Anyone who opts out goes onto your account's opt-out list, and we apply that list before every send, across all of your campaigns. Leaving has no expiry date: the number only hears from us again if the person asks to.
- Is there a console where I can send on my own?
- No. Our team runs the operation: you send us the list and the message, we prepare, schedule and send it, and we return the carrier's report. There is no self-service console and no public API — if there ever is one, it will be announced as a separate product.
- Who is accountable for the list under LGPD?
- It depends on the contractual arrangement and is defined case by case in the contract. Broadly, whoever determines the purpose of processing is the controller; whoever executes the send acts as processor. That split is made explicit before any send.
- How is it billed?
- Per message sent, priced by volume and agreed up front. No platform subscription fee.
Have a list and want to use it without the risk?
Tell us the volume and where the list came from. The first thing we do is assess whether it can be used at all — before talking price.