The platform is the same. What changes are your sector's rules.
Whoever collects has restrictions on hours and on approach. Whoever sells has campaign peaks. Whoever delivers has to give notice within minutes. Pick your sector and see the setup that already handles it — channels, automations and compliance safeguards.
Collecting without becoming a consumer protection case.
Collections is the sector with the most rules of conduct and the least room for improvisation: permitted hours, language that can't embarrass anyone, a record of everything that was said. The operation needs scale and a paper trail — both at the same time.
The pain that shows up first
- A cadence spread across a dialer, a spreadsheet and an SMS tool, with no view of who has already been contacted today.
- Agents negotiating outside policy because the discount ceiling lived in the supervisor's head.
- No consolidated record of what was promised to the customer on each channel.
Recommended setup
3 channels + AICollection groups organize contact by company when you collect on behalf of third parties.
The automations that usually come first
A notice on the due date and, with no reply in 48 hours, an automatic fallback to SMS.
The unpaid installment comes in as an event: the journey sends the notice and a webhook tells your system.
The payment event feeds the journey's condition, and the next reminder for that contract doesn't go out.
Built as journeys: from the dashboard templates or, for longer paths, through the API. See Journeys
Hours, approach and record-keeping — the three points inspectors look at.
The platform helps you avoid the easy mistake: an opt-out that applies to every campaign channel, sends at the time you set, and a record of every message sent, with author and time.
See security and LGPDSends at the time you set
Campaigns, journeys and scheduled messages go out on the day and at the time you define, and each scheduled message goes out only once.
Writes only with approval
When the AI wants to create a task, update the contact or send a template, the request goes into a queue and only runs after a person approves it.
A trail of everything
Every message stays in the contact's history, and the audit log keeps author and time, searchable by period and by operator.
Campaign at peak, order in real time.
In retail two kinds of message live side by side: the campaign, which goes out in bursts and needs opt-in, and the order's transactional message, which can never be late. Mixing the two in the same queue is the classic mistake — and the most expensive one.
The pain that shows up first
- A Black Friday blast delaying order confirmations because everything went out on the same route.
- Abandoned carts recovered by hand, from a spreadsheet exported out of the e-commerce platform.
- Customers replying to a campaign and landing in an inbox nobody watched.
Recommended setup
4 channels + connectorsThe VTEX and OpenCart connectors link the store's catalog and orders to the AI agent, which answers status and tracking by order number.
The automations that usually come first
The cart event from your system enters the journey: it waits 4 hours and sends the coupon with the main item as a variable.
The code and tracking link go out when your system reports that the order status changed.
A short survey in a WhatsApp flow, with the answer going to the contact record.
Built as journeys: from the dashboard templates or, for longer paths, through the API. See Journeys
Marketing opt-in is what separates a campaign from a block.
The wrong template category and a list without consent are the two causes of quality drops at Meta. The platform warns you on the first and records the opt-out for the second.
See security and LGPDA warning from the draft on
A promotion declared as utility tends to be rejected by Meta. The editor warns you before submission when the text reads as promotional or a marketing template has no opt-out button.
Opt-out per contact
An unsubscribe recorded once applies to every campaign channel, with no manual bookkeeping.
Transactional on a separate route
On WhatsApp, campaigns go out through the bulk queue and don't compete with order confirmations, even on a peak day.
The notice that avoids the second trip.
In logistics, a late message is a direct cost: a delivery with nobody home goes back to the distribution center. The value isn't in sending something pretty, it's in sending it fast and getting an answer before the vehicle leaves.
The pain that shows up first
- Route notices going out from a spreadsheet at 7 in the morning, when the driver was already on the road.
- Rescheduling by phone, with people waiting on hold and nothing recorded in the system.
- Customers with no idea where the order was, opening tickets that ate up the whole team.
Recommended setup
2 channels + automationAn event from your TMS or ERP, sent through the API, becomes a journey trigger.
The automations that usually come first
A message with the delivery window and a reschedule button, scheduled for the day before.
Sent the moment the vehicle is loaded, with a tracking link.
A new attempt offered on the spot, with the answer flowing back into your system.
Built as journeys: from the dashboard templates or, for longer paths, through the API. See Journeys
Here the risk isn't regulatory: it's operational.
What protects the operation is knowing whether the notice arrived and having a trail of what was agreed with the customer — including when they deny having received it.
See security and LGPDDeclared fallback
In a journey, unread on WhatsApp within the time you set, the message goes out by SMS.
Proof of message delivery
Delivered and read statuses recorded per message, with the reason when it fails.
A reply that goes back into the system
Confirmation or rescheduling reaches your TMS by webhook, with no manual typing.
Cutting no-shows without exposing patient data.
A clinic lives on a full schedule, and the no-show is the enemy. But every message carries health data — which the LGPD treats as sensitive. The confirmation cadence has to work while saying the bare minimum.
The pain that shows up first
- The front desk calling one by one the day before, with half the calls never returned.
- A message revealing the specialty or the procedure in a lock-screen notification.
- A gap in the schedule discovered only on the day, with no time to fit another patient in.
Recommended setup
2 channels + AIA handoff rule sends any conversation that touches a clinical subject to a person.
The automations that usually come first
A confirmation question with a button; the answer reaches your system through the webhook.
With no reply in 24 hours, the journey tells your system to free up the slot.
A follow-up reminder scheduled for the date the specialty defines.
Built as journeys: from the dashboard templates or, for longer paths, through the API. See Journeys
Health data is sensitive — and the message has to reflect that.
The recommended setup sends the bare minimum: no specialty, procedure or result in the body of the message, with short content retention.
See security and LGPDA message that doesn't expose
A template with no procedure and no specialty; the detail stays in the portal, behind authentication.
Short retention
Message content retention can be set from 30 days.
Access by role
Nine roles separate who administers, who handles conversations and who takes care of billing, and access is revoked the moment someone leaves.
The customer talks to the company, not to the rep.
A B2B sale starts with a technical question: material, run size, lead time, payment terms. When each rep answers on their own phone, the history dies with them — and the customer starts the conversation from scratch at every contact.
The pain that shows up first
- Several phones with personal WhatsApp: when someone was out, the negotiation stopped.
- The same spec questions eating up the sales team's day.
- Repeat orders that meant digging up an old conversation on the phone of whoever handled it.
Recommended setup
2 channels + AIThe contact record keeps internal notes, documents and tasks, plus the whole conversation across every channel.
The automations that usually come first
Inbox rules send the conversation to the right team, by tag, area code or priority.
An automatic nudge if the customer doesn't reply, without the rep having to remember.
The customer is told the moment it is released, with the pickup details.
Built as journeys: from the dashboard templates or, for longer paths, through the API. See Journeys
The risk here is losing information, not breaking a rule.
What protects the operation is the history staying with the company and not on the phone of whoever handled it — including when that person leaves.
See security and LGPDThe company's history
The conversation belongs to the contact, not to the rep. An employee leaving doesn't take the book of business along.
Immediate revocation
A termination removes access right away, keeping the whole history available for whoever takes over.
Negotiation audit trail
What was promised on lead time and price stays recorded, with author and time.
An access code can't wait behind a campaign.
A subscription service has predictable, concentrated volume: authentication every day, recurring billing every month, a campaign at every launch. If it all goes out on the same route, the code arrives after the subscriber has given up on logging in.
The pain that shows up first
- Access codes and a launch blast competing for the same queue on a peak day.
- Messages from an anonymous short code, treated as a scam by part of the base.
- A recurring billing failure discovered through the cancellation, not through the notice.
Recommended setup
4 channelsThe segment count shows up before the send: accented letters are converted and don't change the price; an emoji drops the segment to 70 characters.
The automations that usually come first
Immediate contact with a card-update link before the cancellation.
Transparency that cuts disputes and chargeback requests.
A WhatsApp template with image and button for whoever opted in. The push for whoever has the app goes out as its own send, from the push screen or the API.
Built as journeys: from the dashboard templates or, for longer paths, through the API. See Journeys
Separating authentication from marketing is a survival rule.
Access codes and campaigns run on different clocks. On SMS, the OTP goes out through its own carrier route, separate from the campaign route.
See security and LGPDA route per purpose
OTP through the carrier's OTP route; campaigns through the campaign route.
An identified sender
On WhatsApp the message comes from the official number, with the display name approved by Meta, instead of an anonymous short code.
Opt-in for launches
Campaigns require consent; billing notices and OTP are transactional.
Which channel usually leads in each sector.
It's not a rule: it's the starting point we recommend. The main channel carries the volume, the support one steps in when the first doesn't solve it — and that's why having a support channel matters more than picking “the best channel”.
See price per channelClick a row to load that sector's setup above.
What people ask about their own sector.
Your sector isn't on the list? Tell us your case — the platform isn't vertical.
Is the platform different for each sector?
No. It's the same platform, with the same API and the same price. What changes is the recommended setup: which channels lead, which automations come first and which compliance guardrails are worth turning on from the start. None of it is exclusive to one sector — you can put together any combination.
My sector isn't on the list. Do you serve it?
Yes. These six verticals are examples, not a limit on who we serve. If your operation sends messages to customers, it fits here — in the sales conversation we put together the setup for your specific case.
Do you help build the automations for my sector?
Yes, during onboarding. A specialist walks through activating the channels and the first automations with you, and you validate everything with the test wallet before going to production.
Do I have to buy a module per sector?
There is no module per vertical, and no different price per segment. You pay the monthly tier for your volume and the messages you send — channels, inbox, automations and connectors are already included.
How do you handle regulated sectors?
With the governance tools: an opt-out that applies to every campaign channel, rules that hand a person the subjects the AI shouldn't handle, configurable retention and an audit log with author and time. The regulatory responsibility stays yours, but the platform keeps the easy operational mistake from happening.
Same platform, set up for your sector.
Sign up through the site and get a US$5 test credit.