CCXMessages
Platform · Automations and campaigns

One rule at a time, without a single line of code.

When something happens, if the condition matches, then the platform acts: it sends, tags, creates a task, alerts the team or starts a full flow. Across the six channels, with approval and an audit trail.

See the automations →
app.ccxmessages.com/automations
6 rules active, 1 pausedclick a rule to see the detail
3
pieces per rule: when, if, then
6
channels as an action, with a declared fallback
R$ 0
per rule executed — you pay only for the message
1 click
to pause or reactivate a rule
Pieces of a rule

Trigger, condition and action. That is all.

An automation is one sentence: when something happens, if the condition matches, then run the action. When the journey has several steps, the action is to start a flow — and the visual builder takes over from there.

See automations in the panel →Trigger it by API →
WhenTrigger

The event that starts the rule. It comes from the platform itself, from your ERP or from an API call.

Contact createdSignup in the panel, import or via API
Conversation resolvedClosed by an agent or by the AI agent
SLA at riskTime without a reply above the queue limit
AI agent handoffWhen the AI transfers to a human
Event from your systemPurchase recorded, invoice overdue, order status
Time with no interaction30, 60 or 90 days since the last contact
IfCondition

Optional filter. With no condition, the rule applies to every event from that trigger.

Contact attributeTag, city, billing group, custom field
Active opt-inBlocks marketing to anyone who unsubscribed
Amount and rangeAverage order value, invoice amount, days overdue
Where it came fromQueue, channel or whether the AI handed off
FrequencyOnce per contact or on every occurrence
ThenAction

What the platform does. It can be a send, an internal change or starting a full flow.

Send a templateOn any of the six channels, with variables
Start a flowMulti-step journey in the visual builder
Add or remove a tagNo cost: it feeds segments and queues
Create a taskAssigned to a team, with a deadline
Notify an internal teamSlack or webhook, with no message consumed
Move it in the queueHigh priority, top of the queue or another team
01Campaigns

Bulk sending with a report you can decide on.

Scheduling, approval, execution tracked in real time and failures kept apart for reprocessing. The report shows delivery, reads and replies per channel — not just how many messages went out.

01Approval before the sendA campaign above the limit needs release from someone with permission.
02Execution you can watchProgress, cost consumed and failures visible while the campaign runs.
03Failure retryReprocesses the batch with the fix, keeping traceability to the original.
See campaigns in the panel →
Campaign · July billingsending
Send progress18,402 / 24,000
Pace matched to the channel throughput
Delivered97.1%
Status confirmed by the channel provider
Replies3,104
Conversations opened in the Billing queue
Failures to reprocess212
Invalid, ported or out-of-area number
Failures are kept apart for reprocessing: the original is archived and a new message is generated referencing it.
02Audience

Four ways to say who to send to.

Tag, CSV, a list typed on the spot or a segment saved by attribute. In every case, opt-out and suppression are applied before the send — without depending on someone remembering to filter.

01Variables per recipientFrom the spreadsheet, from a contact attribute or typed into the form.
02Validation before it is acceptedFormat, duplicates and opt-out checked, with a report of what was rejected.
03Reusable segmentThe saved query works for a campaign and for a rule condition.
See contacts and segments →
How to build the audience18,402 contacts

Pick one or more tags applied by the service team, by an automation or by the API. The audience is recalculated at send time.

⊞Tags combined with AND / OR
✕Tag exclusion (who should not receive it)
⛊Opt-out and suppression applied automatically
tags: ["overdue", "active_agreement"] exclude: ["opt_out", "in_negotiation"]
03Integrations

The trigger comes from the system you already use.

Ready-made connectors for VTEX and Opencart, and a generic webhook for any other system. The rule can also be fired by an API call, with your payload as the variables for the actions.

01Native connectorsVTEX and Opencart with order, cart and status events mapped.
02Generic webhookAny ERP or internal system fires the rule with the payload it already has.
03Action back on your APIWhen the rule starts a flow, that flow reads from or writes to your system.
See available integrations →
Connectorswebhook + API
VTVTEXOrder, abandoned cart and status changeActive
OCOpencartOrder created, paid and shippedActive
{}Generic webhookAny system fires the rule with your payloadActive
SHShopifyOrder and cart — in developmentSoon
BTBling and TinyOrder and invoice ERP — in developmentSoon
With no ready-made connector, any system fires the rule by webhook or by the API — the trigger accepts your payload.
Governance

Bulk sending needs a handbrake.

Approval before the send, a frequency cap per contact, quiet hours and an audit trail. No large campaign goes out without someone signing off.

Security and compliance →
Before the send
✓Approval by thresholdA campaign above the defined volume or cost waits for a named release.
◱Estimated cost before sendingThe review screen shows the projection from the channel rate card and the wallet balance.
⛊Opt-out applied to the audienceWhoever asked to leave is removed at send time, not in the spreadsheet.
◐Test with a real contactA run in the test environment executes the whole rule without debiting real balance.
During and after
◷Frequency cap per contactThe same customer never gets more than you defined, even if two rules reach them.
⏸Pause and resumeA running campaign can be paused; whatever already went out stays tracked.
▤Audit trailWho created it, who approved it, who paused it and who reprocessed it — with the time.
◎Report by channel and branchDelivery, reads and replies per channel, and conversion by condition path.
Ready-made templates

Start from a template, not from an empty screen.

Rules and flows ready for the most common cases, with trigger, condition and action already set. You swap the text, confirm the trigger and switch it on.

⚡
Abandoned cart
A 4h wait, a coupon on WhatsApp and a last-call SMS.
conversion 7.4%
◱
Billing sequence
Notice, due date, overdue and negotiation with handoff at the limit.
handoff on 12%
✎
Post-sale and NPS
Collects the score, saves it on the contact and opens a ticket when it is critical.
response 31%
◷
Appointment confirmation
Asks, validates and reschedules from the customer's reply.
no-show −22%
◫
New customer onboarding
Welcome sequence that collects the data still missing.
5 blocks
↻
Winning back inactive customers
Segment of 30 days with no purchase, with an offer and a fallback.
reactivation 9%
▣
Delivery notice
ERP trigger on every order status change.
0 human touches
Lifecycle

Testable, reversible and auditable.

A rule is born disabled, gets tested with a real contact and only then goes live. Pausing is one click, and every change is recorded with author and time.

disabledBorn without firingA newly created rule receives no event — you can leave it half-written with no risk.
testRuns with a real contactIn the test environment it shows which condition was evaluated and which action fired.
activeGoes liveIt starts responding to every event, with a run counter and the last fire.
pausedStops in one clickPausing does not erase: the history stays and the rule resumes where it stopped, with no reprocessing.
“We swapped eight spreadsheets and two scripts for seven rules. When the billing policy changes, it changes in the panel — not in production.”
DPDiego PradoOperations Director · debt collection company
Frequently asked questions

What people ask before automating.

Want us to build the first rules with you? Book a session .

The automation is the short rule: when something happens, if the condition matches, run one action. The flow is the multi-step journey, with waits, branches and data collection, built in the visual builder. The two meet when the rule's action is precisely to start a flow.

Start today with R$ 50 in test credit.

Sandbox wallet released when you create the account, a WhatsApp test number and guided onboarding. No card, no contract.

Book a demoCreate free accountSales reply within 2 business hours
CCX
Brazilian CPaaS platform. WhatsApp, email, SMS, RCS, push and Instagram in a single integration.
All systems operational
Product
InboxAI agentAutomationsIntegrationsPricing
Channels
WhatsAppEmailSMS and RCSPushInstagram
Solutions
SegmentsCustomersCollectionsRetailLogistics
Developers
DocumentationPlaygroundChangelogStatusHelp center
Company
About usBlogContactCareershiringLog in
© 2026 CCX Digital Solutions LTDA · CNPJ 24.329.191/0001-06 · BrazilTerms of usePrivacySecurityChangelog