Access codes on time, renewals without surprises.
Access codes go out on their own route, renewal and billing notices follow each subscriber's dates, and new releases reach the people who opted in. Every channel answers to the same API and the same subscriber record.
Sign up through the site and get a US$5 test credit.
Four moments in a subscriber's month.
Each one starts with an event from your platform and runs on SMS, journeys, email and push.
Access codes
Codes go out on the access-code route, separate from the route your campaigns use, over the REST API or SMPP. Outside Brazil, a WhatsApp authentication template does the job.
Renewal coming up
Your billing system posts the event, and a journey sends a utility template with a link to manage the plan.
Payment failed
A utility template carries the card-update link from your system. If the payment event doesn't arrive within the wait you set, an email reminder follows.
A new release
Push from the dashboard or the API to people with your app, and a marketing template to subscribers who opted in.
A billing notice that stops when the payment lands.
The condition waits for your payment event. Whoever pays leaves the journey at the goal; whoever doesn't gets one email reminder with the same link.
The payment event is yours: your system posts it through the API, and the journey's goal ends the run for whoever paid.
The channels a subscription runs on.
SMS carries the codes, WhatsApp and email the billing, push the new releases. One API and one webhook for all of them.
Access codes on their own route, over REST or SMPP, with the carrier's delivery receipt. Brazilian numbers; other countries on request.
Explore SMSRenewal and billing notices through utility templates, and launches to subscribers who opted in.
Explore WhatsAppNew releases on iOS, Android and the browser, for people with your app or who allowed your site.
Explore PushAccess codes that arrive while the subscriber waits.
Rumo.tv, a streaming platform, sends its subscribers' access codes by SMS, connected to CCX over SMPP.
Read the customer storyCodes and campaigns on separate clocks.
What keeps the code arriving on a launch day, and the bill clear for the subscriber.
What one subscriber costs in a month.
You pay the monthly plan and each message at its published price. Journeys, waits and webhooks cost nothing.
International price list in US dollars. WhatsApp prices are for messages to the United Kingdom; each destination country has its own price.
What subscription services ask before they start
Still unsure? Talk to the team that runs the platform.
Can I send access codes outside Brazil?
SMS outside Brazil is on request. For other countries, use a WhatsApp authentication template, priced by destination country.
Do I need SMPP?
No. The REST API sends codes with an Idempotency-Key, and SMPP over TLS is there for teams that already run an SMPP client.
Will a launch delay the codes?
On SMS, codes go out on the OTP route, apart from the campaign route. On WhatsApp, scheduled campaigns use a bulk queue of their own.
How do subscribers opt out?
A STOP reply on SMS or WhatsApp records the opt-out, and every email carries a one-click unsubscribe link.
Can a notice follow each subscriber's renewal date?
Yes. Your billing system posts the event through the API when it's time, and the journey sends the notice. Waits in a journey run from 1 minute to 90 days.
How much does it cost?
The monthly plan, from US$39, plus each message at its published price. No per-seat fees and no setup fee.
Send the next code on its own route.
Sign up through the site and get a US$5 test credit.