§ SMSplus
SMS in Brazil, with the tedious compliance part already solved
Two ways to send: the self-service console — sign-up, verified consent, sending and the carrier's report — or a campaign run end to end by our team. Either way, your account's opt-out list is applied before every send. Because in Brazil, getting this wrong costs up to 2% of revenue.
- Recorded, auditable consent
- Account-wide opt-out applied before every send
- Self-service, or run 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 in Brazil, processing data for commercial messages needs a valid legal basis under the LGPD and has to respect people who ask to leave — and the ANPD, which became a regulatory agency in 2026, opened 19 new sanctioning proceedings in June alone. Our standard is consent with a provable origin; the legal basis in each case is assessed with your legal team. 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
In self-service, every import records the list's source and the version of the consent text you declare. In a campaign we run, we check each contact for consent source, date and the version of the text they accepted. Without that there is no proof of compliance — and that is exactly what the authority asks for.
- 02
Opt-out covers the whole account
Anyone who asks to leave goes onto your account's opt-out list, and that list is applied before every send, across all of your campaigns — the ones you send from the console and the ones our team runs. It is not a per-campaign list, and leaving holds until the person asks to come back.
- 03
You send it, or we do
In the console you import the list, write the message, see the estimate before sending and send inside the permitted window — or integrate through the API. Higher-risk profiles and campaigns are reviewed by our team before anything goes out. The console is in Portuguese for now. If you would rather not operate anything, send us the list and the message, and we clean it, fit the copy to the channel, schedule and send.
- 04
The carrier's report, not an estimate
Sent, delivered and failed come from the status the carrier returns — per campaign in the console and per message through the API, and in the report we hand over at the end of a campaign we run. Not a figure we estimated. Anyone who replies SAIR is added to the account's opt-out list automatically.
What's included
- List import and cleaning, with deduplication
- Consent record check (source, date, text version)
- Account-wide opt-out list, applied automatically before every send
- Message copywriting and channel fit, in campaigns our team runs
- Sending from the console or the API, or scheduling and sending by our team — always inside permitted sending windows
- The carrier's delivery status, in the console or in the report at the end of the 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 want to send on your own from a console or the API — or would rather a team ran the whole campaign
- 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 today, not outbound sending
AI Messaging & Actions · in pilot
And after the reply?
Sending works today. Understanding the reply and taking the next step we are building with pilot companies. Anything marked pilot or planned is not yet a product on sale.
Available today
- SMS sending from the console, by API or run by our team
- Delivery status returned by the carrier
- Automatic opt-out when a person replies SAIR
- A record of each list's origin and consent
In build, open to pilots
- Storing the replies received
- Classifying replies with AI
- Suggested replies with human approval
Planned
- Integration with CRM and company systems
- Appointment confirmation and rescheduling
- Carrying out actions under rules, with human intervention
How this could look
- Hello Maria. Your request is waiting on one piece of information. Can we help?
- Yes, I'd like to know what's missing.
- This is the company's automated assistant. I can check the status and guide the next step. Would you like to continue?
Frequently asked questions
- Can I use a list I bought?
- We do not work with purchased lists. Our rule is verifiable consent, and a purchased list cannot evidence it. 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?
- Anyone who replies SAIR (or PARAR, STOP) goes onto your account's opt-out list automatically, and that list is applied before every send, across all of your campaigns. In campaigns we run, every message carries exit instructions; in self-service, including them in the text is the sender's responsibility. Leaving has no expiry date: the number only hears from your account again if the person asks to.
- Is there a console where I can send on my own?
- Yes. Sign up at bytemerica.com/sms/start: you verify a phone number, declare your use case and send a test SMS; low-risk profiles are activated straight away, the rest are reviewed by our team. Then you import contacts, create campaigns and follow delivery — or integrate through the API. The console is in Portuguese for now. If you prefer, our team still runs the whole campaign for you.
- 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 you see the estimate before you send. No platform subscription fee. In self-service the balance is prepaid: you pay by Pix or bank transfer and our team credits your service balance, which can only be spent on messages.
- Does AI already answer my customers?
- Not today. What is live is SMS, and among the replies received the system only handles opt-out requests automatically. Understanding, answering and acting with AI is what we are building with pilots.
- What is an AI Messaging pilot?
- A test agreed with one company, with scope, volume and rules set before it starts. Timing and price are agreed case by case, and requesting an assessment does not guarantee a place. The rule for any pilot: an automated reply identifies itself as such, and there is a way to reach a person.
Have a list and want to use it without the risk?
To send on your own, create an account at bytemerica.com/sms/start. For our team to run it, 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.