Everything that changes your invoice, on one page: what each way of signing up charges for, what counts as usage, and what happens when you move up, move down or cancel.
Three words explain everything else.
Three things measure the size of an account, and they are what decide which plan it needs: users, projects and AI usage.
Beyond those three there is the Partner Programme, for anyone who wants to resell RedSync under their own brand. It is not a separate plan: the partner signs up for a normal plan and receives their own terms, set under contract. It is not bought on the site — the route is the partner form.
Four questions settle the choice:
| Way | Charges by | For whom |
|---|---|---|
| Plans | package: included users + projects | the company that will run RedSync with its team inside |
| Custom | licence = user × module | anyone who wants just one piece of RedSync, in a single business |
| SaaS Partners | project | software that uses RedSync as an engine for sending, automation and AI, via API |
There is no gratis tier. Anyone who creates an account gets 7 days with the entire platform: 50 users, unlimited projects, pipelines, boards and automations, every module, bulk campaigns, proposals and your own AI agents, plus 150k AI credits and 100 WhatsApp messages on the house.
It does not ask for a card and it generates no charge at all. When the AI credits or the message cap run out, that resource stops — nothing turns into an invoice for someone who has not signed up yet.
What the trial does not include: own branding and priority support. Those are contract items.
The administrator sees a counter at the top of the screen, highlighted in the last 3 days, and gets a warning at 3 days left and at 1 day left. Managers and agents do not see that counter: the decision to sign up is not theirs.
| When the 7 days end | What happens |
|---|---|
| Administrator | signs in normally and lands on plan selection |
| Manager and agent | a screen explaining the trial has ended and an administrator needs to choose a plan |
Automations are switched off on day 8. Integrations keep receiving: the one who did not sign up is the company, not the end customer who sent a WhatsApp message — and a lost message does not come back.
The path is always the same:
The plan is activated when payment is confirmed — not when the charge is generated. With a bank slip that takes the usual clearing time. Only the owner or the account administrator signs up, changes plan and pays; card details never pass through the RedSync screen. The service invoice is issued automatically and stays in the payment history.
| Method | Monthly | Annual |
|---|---|---|
| Bank slip | one charge per month | a single charge for the year |
| PIX | one charge per month | a single charge for the year |
| Credit card | automatic charge every month | in full or split into up to 12 instalments |
The subscription's due date is the anchor for everything: it defines the billing cycle, how usage is measured, and when AI credits renew.
On monthly, everything arrives on one invoice. The following month's invoice comes with the subscription fee and, itemised in the same document, the WhatsApp messages sent in the cycle, the fee per official channel, the AI overage on plans where it is billed, and the pro-rata of an upgrade made mid-cycle.
On annual there is prepaid credit. A 12-month cycle has no “next invoice” to put the month's usage on, so the annual account buys a balance before using it, and WhatsApp messages, official channel fees and AI overage come out of that balance.
| Monthly | Annual | |
|---|---|---|
| Cycle length | 1 month | 12 months |
| Discount | — | 20% to 30% |
| Instalments | does not apply (it recurs) | up to 12x on card |
| Usage (messages, channel, overage) | goes on the following month's invoice | comes out of prepaid credit |
| Renewal | automatic every month | every 12 months |
The annual plan has a discount, and the discount depends on how you pay:
| Plan | Monthly | Annual in full (−30%) | Annual 2–6x (−25%) | Annual 7–12x (−20%) |
|---|---|---|---|---|
| Starter | R$ 476 | R$ 333/mo · R$ 3,996 | R$ 357/mo · R$ 4,284 | R$ 381/mo · R$ 4,572 |
| Growth | R$ 956 | R$ 669/mo · R$ 8,028 | R$ 717/mo · R$ 8,604 | R$ 765/mo · R$ 9,180 |
| Pro | R$ 1,676 | R$ 1,173/mo · R$ 14,076 | R$ 1,257/mo · R$ 15,084 | R$ 1,341/mo · R$ 16,092 |
| Scale | R$ 3,153 | R$ 2,207/mo · R$ 26,484 | R$ 2,365/mo · R$ 28,380 | R$ 2,522/mo · R$ 30,264 |
Paid in full means bank slip, PIX or card in a single instalment. The same discount applies to Custom and to SaaS Partners, over the subscription total.
Three things are paid on top of the subscription fee, and they work differently in each way of signing up.
| WhatsApp messages — always per use | Cost |
|---|---|
| Marketing | R$ 0.49 |
| Utility | R$ 0.05 |
| Authentication | R$ 0.05 |
| Service (inside the conversation) | R$ 0.01 |
On the annual plan every overage comes out of prepaid credit — messages, channel fees and AI overage. When the balance hits zero, WhatsApp sending and AI use stop, and come back with a top-up. That is the central difference from monthly, where overage becomes an invoice and nothing stops.
Moves up immediately, bills later.
An upgrade also cancels a downgrade that was scheduled.
Moves down at the turn of the cycle.
Switching between Plans, Custom and SaaS Partners follows the same rule: price decides. A destination more expensive than the current plan is an upgrade, effective immediately with pro-rata. Cheaper or equal is a downgrade, effective at the turn of the cycle.
That is why it is case by case: a Custom setup at R$ 1,110 moving to Growth (R$ 956) is a step down; a Starter moving to a Custom setup at R$ 3,700 is a step up.
| From → to | What changes |
|---|---|
| Plan → Custom | one project only; licences are assembled at sign-up; automation and AI cease to exist; integrations outside the plan are paused |
| Plan → SaaS Partners | automations and integrations continue; module screens close; agents become managers, because SaaS Partners has no such role |
| Custom → Plan | licences cease to exist; automation, AI and integrations take effect |
| SaaS Partners → Plan | module screens open; the destination's project cap applies |
| SaaS Partners → Custom | one project only; the licensed modules' screens open; automation and AI drop out |
Joining or leaving the Partner Programme is not a switch between ways: the plan stays the same, and what changes goes through our team, not the checkout.
| Sign-up | How it renews |
|---|---|
| Monthly (bank slip, PIX or card) | automatically every month, on the subscription's due date |
| Annual in full (bank slip, PIX or card in 1x) | automatically every 12 months |
| Annual split on card (2 to 12x) | the instalments cover the contracted year; renewal is announced in advance and confirmed by the customer, because the number of instalments goes back through the card issuer |
At renewal, AI credits return to the plan's amount and the usage cycle restarts. The annual plan's prepaid credit is untouched: it does not expire and carries on as it is.
Cancelling ends the subscription, and access lasts until the end of the period already paid for. Nothing is charged after that, there is no penalty and there is no pending invoice. Until the period ends, everything keeps working normally.
When the period ends, the administrator signs in and lands on the sign-up screen again; managers and agents see a notice that the subscription was cancelled; and channels, flows and connections are switched off — not just automations.
Signing up again creates a new subscription and reconnects what billing switched off. Three things do not come back on their own, and the customer is better off knowing in advance:
The data stays, and the account's plan and payment history remains available.
The three days of grace at the start are deliberate: a bank slip takes time to clear, and warning someone the day after the due date alarms people who have already paid.
On day 10 automations are switched off. Integrations keep receiving — the one who did not pay is the company, not the end customer who sent a message. On settling up, access and automations return the moment payment is confirmed.
If nobody on the account has an administrator profile, the billing notice goes to the registered billing email, and the block explains that payment sits with the company's finance team.
| When | Administrator | Manager and agent |
|---|---|---|
| Days 0 to 2 | nothing | nothing |
| Days 3 to 9 | on-screen notice with a Settle now button, plus a notification | nothing: they have no way to resolve it |
| Day 10 onwards | signs in and lands on the list of outstanding payments | a blocking screen asking an administrator to restore access |