Journeys that react to each contact's behavior
A standalone campaign reacts to no one. In Flow, a form submitted on your site starts a step-by-step journey — message, wait, condition and internal actions — with consent verified before every send. For marketing and growth teams, and for agencies.
Step-by-step sequence builder · Email from your own domain · Consent, opt-out and frequency cap · Trail of every send
Mass blasting reacts to no one
The newsletter goes to everyone the same way, the campaign lives in one tool, the sign-up in another and the follow-up in a spreadsheet. Without reacting to what each contact does — and without frequency control, opt-out or a trail — communication becomes noise. Flow starts from a submitted form and organizes the journey as steps in sequence.
One message for everyone
Without a journey, every contact gets the same thing at the same time. Those who already bought, those who went quiet and those who just arrived all land in the same blast — and engagement drops.
Isolated campaigns, no reaction
The cadence lives in one tool, the form in another and the CRM somewhere else. Nothing reacts to what the person did: the form they submitted goes unnoticed.
Communication without governance
Without frequency control, per-channel opt-out and a trail of every send, communication drifts toward spam and becomes hard to audit later.
From the form to the internal action — organized as steps in sequence
Flow turns a submitted form into a journey and the journey into action, without relying on a manual blast.
Journey builder with steps in sequence
Chain trigger, wait, condition and internal actions — move stage, adjust score, update field, apply or remove tag, webhook, notify the team. A condition that is not met ends the journey rather than opening a second path. It is a step-by-step sequence builder, not a drag-and-drop canvas.
Form-submission trigger
Today a journey starts when someone submits a form installed on your site. The other triggers shown in the editor — tag, segment, event, score band and manual start — do not start a journey yet, so they are not part of the offer.
Contacts, segmentation and lead scoring
Manage contacts with fields and import, create AND/OR rule segments, recalculated on demand and when each campaign is prepared, and score interest with lead scoring.
Campaigns with an estimated audience
Estimate the audience by list or segment before sending; at send time, the recipient list is frozen. No unlimited volume promised: every plan states its cap.
Conversion: forms and pop-ups
Capture leads with forms, pop-ups and the WhatsApp button, installed on your own site with a code snippet. The submission becomes a contact on the server and a journey trigger right away.
Results by source
Funnel, conversions and attribution show where each contact came from and what they did next. Events live in their own catalogue, and the base exports whenever you want — the data is yours.
Want to see a journey built for your operation?
Get to know FlowOne proven channel, one with assisted activation
Email is the channel Flow sends on today, from your own verified domain. WhatsApp uses the official Meta API and depends on your account and approved templates — so it comes with assisted activation, not a toggle.
Sending today
Comes in as a step inside the journey builder, alongside waits, conditions and internal actions.
Email (Resend) — marketing and transactional
Sending under your own sender identity, with the domain verified. One-click unsubscribe with the standard header, a suppression list honoured on every send, and consent verified before anything leaves.
With assisted activation
The channel exists in the product, but depends on third-party credentials and approval. Activation is done together with the team, and is not immediate.
WhatsApp — official Meta API
Sending via the official API (Meta Cloud), with your own account. Requires the contact's opt-in for marketing and templates approved by Meta; there is keyword opt-out and suppression. Never free-form blasting without opt-in.
To be direct: email is the channel that has already sent real messages in production. WhatsApp has the integration ready and no account configured so far — hence the assisted activation. SMS and web push exist in the code but are not part of the offer: they have never been switched on, and we do not sell what has never run.
From the trigger to the result recorded in the trail
An illustrative example of the real Flow — it includes verifying consent and suppression before any send. No real account, data or brand, and never a send without consent.
From trigger to result, step by step
IllustrativeTrigger
A form submitted on your site starts the contact's journey.
Contact created
The submission becomes a contact on the server, built from the fields sent.
Consent verified
Before sending, Flow checks consent and suppression. Without it, no send.
Message sent
The message goes out by email, from a sender on your own domain.
Wait
A wait respects the contact's timing before the next step.
Signal recorded
What the contact does on your site becomes an event and adjusts their score.
Condition
A condition checks the contact; if it is not met, the journey ends there.
Internal action
An internal action runs: tag, field, lifecycle stage or a notice to the team.
Result recorded
What happened is recorded in the trail of every send.
Flow: a submitted form starts the journey; the submission becomes a contact; consent and suppression are checked before sending (control point); the message goes out by email; a wait respects the contact's pace; a new signal from the contact adjusts their score; a condition checks the contact and, if it is not met, ends the journey; an internal action runs (tag, field, stage or team notice); the outcome is recorded in the trail.
Where Flow fits day to day
Four common uses of Flow, all under send governance.
Onboarding that activates
A sequence guides the new contact to first value and stops once they've activated — without repeating a message for those who already moved on.
Nurture after the form
Whoever submits the form enters a cadence with waits between messages; every send goes through the consent and frequency check, and a condition that is not met ends the journey.
Campaign to a segment
Estimate the audience of a rule-based segment, send the email right away and keep the list frozen at send time, with a record of every message and every block.
Handover to the sales team
When the contact's form arrives, the journey moves their stage, applies the right tag and notifies the team — and the lead also becomes a deal in Centriu Orbit, where the pipeline is managed.
Send-governance tools — not automatic compliance
Flow brings real controls so communication goes out with governance. They are support tools: consent is an option per workspace, and legal responsibility remains yours.
Consent per workspace
When consent is required, Flow checks it before sending and records the block when it is missing. It is configurable per workspace — not automatic data-protection compliance.
Per-channel opt-out and suppression
One-click email unsubscribe, using the standard header email clients recognise, and a suppression list honoured before every send.
Quiet hours and frequency cap
Quiet hours (global and per channel) and a weekly frequency cap per channel prevent over-messaging the same contact.
A trail of every send and kill switch
Every send is recorded for audit, and a kill switch lets you stop communication when needed.
These are tools to support communication governance. They help you honor consent and opt-out, but they do not replace your privacy policy or guarantee automatic legal compliance.
Flow, Agent, Link and Orbit solve different things
A prose positioning to place Flow — it is not an official comparison or an integration. Each one handles a different part of the operation.
Automates journeys and actions by trigger and condition
Flow starts from the contact's behavior and organizes the journey by steps and branches: message, wait, condition and internal actions, with send governance.
Provides specialized agents
Agent offers AI agents for specific tasks. It is a different object from Flow — which automates by rules, not by agents.
Centralizes conversations and channels
Link brings conversations and support channels together in an inbox. Flow automates communication journeys; they are distinct roles.
Organizes contacts, deals and pipeline
Orbit is the CRM for deals and pipeline. Flow handles communication automation; each holds a different kind of data.
This is positioning, not an official comparison or an integration. Today there is no confirmed data integration between Flow and Agent, Link or Orbit. If your operation depends on a connection between systems, talk to us before contracting.
Multi-client operation, with enablement
Flow was designed for those who run many clients at once — each in its own environment, without mixing data.
Multi-workspace
Manage several client environments, with members, blueprints and a directory, from an agency operation.
Each client isolated
Each client has its own workspace, contacts and journeys. Serve many accounts without mixing data.
Operation with enablement
The agency operation is sold with enablement, not as turnkey resale. End-to-end branding and financial pass-through are not available yet.
The agency operation requires enablement — it is not turnkey resale. End-to-end branding (white-label) and financial pass-through between agency and client are not available yet.
System plans
Three tiers that unlock more as you grow. On Max, you get access to everything.
Essentials to start
Up to 2,000 contacts and 12,000 emails per month
- Contacts with custom fields and CSV import
- Forms and pop-ups on your site; each submission becomes a contact
- Email marketing from your own domain
- AND/OR rule segments, recalculated on demand and before each campaign
- Step-by-step journeys with waits and conditions, started by a form submission
- Pixel tracking and event catalogue
- One-click unsubscribe, suppression and quiet hours
Full operation
Up to 10,000 contacts and 60,000 emails per month
- Contacts with custom fields and CSV import
- Forms and pop-ups on your site; each submission becomes a contact
- Email marketing from your own domain
- AND/OR rule segments, recalculated on demand and before each campaign
- Step-by-step journeys with waits and conditions, started by a form submission
- Pixel tracking and event catalogue
- One-click unsubscribe, suppression and quiet hours
- Rule-based contact scoring with recorded bands
- Email campaigns with audience estimates and a list frozen at send time
- Funnel, conversions and source attribution
- Outbound webhooks and contact export
Everything unlocked
Up to 25,000 contacts and 150,000 emails per month
- Contacts with custom fields and CSV import
- Forms and pop-ups on your site; each submission becomes a contact
- Email marketing from your own domain
- AND/OR rule segments, recalculated on demand and before each campaign
- Step-by-step journeys with waits and conditions, started by a form submission
- Pixel tracking and event catalogue
- One-click unsubscribe, suppression and quiet hours
- Rule-based contact scoring with recorded bands
- Email campaigns with audience estimates and a list frozen at send time
- Funnel, conversions and source attribution
- Outbound webhooks and contact export
- Multiple workspaces in a single operation (agency)
- Permission-based access profiles and multi-organisation
- Screens for data-subject requests, retention and export
- Assisted WhatsApp activation via the official Meta API
- API access
Add-on channels
WhatsApp and SMS are bought separately
No Flow plan includes WhatsApp or SMS — not even Enterprise. To send on those channels you buy the add-on, and keep paying your Flow plan as usual. The reason is simple: email is something Centriu buys and resells inside your cap; WhatsApp and SMS messages come out of your own provider account, and charging for them here would be charging you twice.
You connect your own WhatsApp Cloud API number. Flow handles templates, the 24-hour window, opt-out and delivery status.
- Up to 5,000 messages/monthR$ 197/mês
- Up to 25,000 messages/monthR$ 497/mês
- Up to 100,000 messages/monthR$ 997/mês
The provider account is yours: Meta (WhatsApp Cloud API). Meta bills you per message directly, and also caps your number with a tier. The cap that applies is the lower of the two — buying 100,000 for a TIER_250 number buys nothing.
SMS
You connect your own Twilio account. Flow normalises the phone number, honours keyword opt-out and records delivery.
- Up to 2,000 segments/monthR$ 97/mês
- Up to 10,000 segments/monthR$ 297/mês
- Up to 50,000 segments/monthR$ 697/mês
The provider account is yours: Twilio. Twilio bills you per message segment, directly. Accented text uses more segments — Flow shows how many before you send.
What you pay here is the platform around the send: opt-in and keyword opt-out, suppression list, approved templates, the 24-hour window, delivery status and the record of all of it. The send itself is billed by the provider, on their invoice, at their price. Two bills — and we would rather say so on the pricing page than let you find out on your first campaign.
Frequently asked questions
Is Flow an automation platform?
Yes. Flow is Centriu's platform for marketing automation and lifecycle journeys. It starts step-by-step journeys from a submitted form — with message, wait, condition and internal actions — plus contacts, segmentation, lead scoring, campaigns and conversion. The builder works with steps in sequence, not drag and drop.
Which triggers are there?
Today, one: form submitted. The editor shows others — tag applied, segment entered or exited, custom event, score band and manual start — but they do not start a journey yet, and we do not sell them as if they did.
Which channels can I use?
One in operation and one with assisted activation. Email (Resend, with your verified domain) is the channel Flow sends on today and is the message step of the journey. WhatsApp uses the official Meta API, with your own account, contact opt-in and approved templates — activation is done with our team. SMS and web push exist in the code but are not part of the offer.
Does Flow send WhatsApp?
Yes, via the official WhatsApp API (Meta Cloud) — with an honest caveat: the integration is ready and no account has been configured to date. That is why activation is assisted rather than a toggle. It requires your Meta account, the contact's opt-in for marketing and approved templates; there is keyword opt-out and suppression.
Does Flow send email?
Yes — marketing and transactional, via Resend, from a verified sender domain. What goes out is recorded in the send trail, with one-click unsubscribe and a suppression list. What is NOT part of the offer today is the delivery, open and click report: the provider callback is not yet wired to Flow, and we do not sell a metric we do not measure. We promise neither guaranteed delivery nor unlimited volume.
Does Flow create landing pages and forms?
Forms and pop-ups, yes — and the WhatsApp button. You install them on your own site with a code snippet, and the submission becomes a contact on the server and a journey trigger right away. A landing page hosted by Flow is NOT part of the offer: page authoring is not done in the product yet, and an empty page serves no one.
How does consumption work?
By two numbers, and both appear on the plan card: how many contacts fit in your base and how many emails you send per month. The contact is what the platform stores; the email is what it spends. Both are genuinely counted — contacts by direct count, emails by a record written in the database on every send.
What happens if I go over the limit?
You are warned from 80% of the monthly cap, on the Plan & Usage screen. At 100%, new sends stop until the month turns over or you move up a plan — there is no automatic overage charge, because there is no automatic charging in the product at all today. We would rather stop and tell you than raise an invoice you did not choose. There is no "unlimited email" here: every email has a real cost, and a plan pretending otherwise is charging someone the wrong price.
What is the difference between Flow, Agent, Link and Orbit?
Flow automates journeys and actions by trigger and condition. Agent provides specialized AI agents. Link centralizes conversations and channels in an inbox. Orbit organizes contacts, deals and pipeline (CRM). They are different roles — and, today, with no confirmed data integration between them.
How is consent handled?
When required, consent is checked before the send and a missing one becomes a recorded block, configurable per workspace. There is per-channel opt-out (one-click email unsubscribe and a keyword on WhatsApp), quiet hours, a frequency cap and a kill switch. These are governance support tools — not automatic legal compliance.
Can agencies operate Flow for clients?
Yes. Flow has multi-client management (multi-workspace), with environments, members and blueprints per client. The agency operation is sold with enablement, not as turnkey resale; end-to-end branding and financial pass-through are not available yet.
Is there an implementation?
Yes. Onboarding is assisted: kick-off, email domain verification, installing the tracking snippet and forms on your site, and building the first journey together with you. If WhatsApp is in scope, the Meta account and templates are configured in that same step. Marketing, growth and CX teams run Flow day to day.
Start with one journey and scale with governance
Tie the journey to the form on your site, build the steps in sequence and let every send carry consent and a trail. Talk to a specialist and see Flow applied to your operation.