Brevo Automation Guide

Who this guide is for

This guide is for small marketing and growth teams that need email automation, a shared contact database, and at least one other channel — SMS, WhatsApp, or live chat — without paying for three separate vendors. If budget scrutiny is a quarterly ritual, Brevo's tier ladder is built for that conversation.

You will get the most value if you run a mixed motion: product announcements by email, time-sensitive nudges by SMS, and a light sales pipeline tracked in the same CRM. Founders and two-person marketing teams are the natural audience; so are agencies consolidating client tools under one bill.

If you need deep billing-native subscription automation or extreme event branching, pair Brevo with a specialist or read the alternatives first — the pricing guides index and our verified pricing snapshot show how the axes differ before you commit a year of contacts to any platform.

Brevo's genuine strengths are visible here, alongside the places where its billing integration story requires more assembly.

Learning the workflow builder

Start from the recipe gallery rather than a blank canvas: welcome, follow-up, and re-engagement templates encode sensible delays and branch points. Customize entry triggers for your funnel — list join, form submit, page visit, deal stage — and keep the visual canvas readable by naming every node after the decision it makes rather than the email it sends.

Reserve SMS for moments where minutes matter: trial expiry, appointment reminders, shipping updates, a security code. An SMS budget spent on routine nurture trains people to ignore the channel before the urgent message ever lands.

Combining transactional and marketing mail

Brevo sends transactional and marketing mail under one account with shared templates and sender management. Route receipts and resets through the transactional pipeline while nurture runs as automations, monitoring both streams separately so a campaign spike never masks a problem in critical mail — separate logs, separate alarms, one deliverability reputation.

For SaaS billing events, connect the payment processor through available integrations and map webhook events to automation entry points. Test the complete path end to end before launch.

Budget an engineering afternoon for the webhook mapping and a test-mode pass over trial expiry, payment failure, and cancellation before calling dunning live. Keep a dated note of who owns the mapping; the failure we see most is an unowned integration silently going stale.

Keep transactional templates boring and fast: plain structure, authenticated domain, no promotional footer dragging receipts into marketing scrutiny.

Choosing the right tier

Validate on free, buy Starter when daily volume or branding limits pinch, and step to Standard once A/B testing, advanced statistics, and deeper automation matter. Pro suits high-volume senders needing dedicated infrastructure — the $499 jump is a serious commitment, so reach it on evidence rather than ambition.

Model twelve months of list and volume growth before you pre-pay any tier: Brevo's axis is volume and features, not contacts stored, which is friendlier to big lists than per-contact rivals — but the feature gates at Standard are what most growing teams actually feel.

Our verified pricing snapshot lays the entry figures side by side; treat the official Brevo page as the final authority before purchase.

Check Brevo pricing

Pricing tiers and the billing axis

The axis is volume-plus-features rather than contacts stored. A growing SaaS list with thousands of dormant free users does not inflate the invoice the way per-contact tools allow — what moves cost is how much you send and which feature gate you have crossed. For list-heavy funnels that is a genuine advantage; for teams stuck below the Standard gate it means the automation ceiling is felt long before the budget does.

Read the tiers as a capability staircase. Free proves the canvas. Starter removes daily volume pressure and branding. Standard is where A/B testing, advanced statistics, and deeper automation logic arrive — the tier most actively growing teams land on.

Pro at $499 is infrastructure territory: dedicated resources for senders who have outgrown shared paths, not a default upgrade for teams still finding their cadence.

Watch the second meter: SMS and WhatsApp usage adds credit-style charges on top of the email tier, so multichannel teams should forecast both. Compare the combined cost against standalone SMS vendors in our verified pricing snapshot before assuming the email sticker is the whole bill.

Where it fits in the five-stage lifecycle

Welcome and nurture are where Brevo's recipe gallery shines — fast, conventional, hard to get badly wrong. Convert and retain depend on how much event truth you feed it: with payment webhooks and product events wired in, the branches get sharp; without them, conversion flows lean on dates and opens, which is where behavioral suites pull ahead.

That gap is not permanent — it is an instrumentation decision. Teams that wire three events (trial created, payment failed, key feature used) close most of it; teams that wire none stay on calendar logic forever and blame the tool.

Winback is the stage most Brevo accounts skip, and it costs them twice: cold contacts drag engagement rates down, and nobody notices the reactivatable segment sitting in the list. Build a dormancy trigger, run one honest re-engagement pass, then suppress.

Automation depth: what you can and cannot build

The canvas is genuinely capable within its event model — here is the honest inventory of both sides.

• Visual workflow canvas with list, form, page-visit, deal-stage, and attribute conditions, plus timed delays and splits.
• Multichannel steps: email, SMS, WhatsApp, and chat handoffs inside the same workflow where credits allow.
• A built-in CRM — contacts, companies, deals, and scoring — so sales-assisted handoffs stay in one system.
• Transactional API and SMTP for receipts, resets, and alerts, with shared templates and sender management.
• Segmentation on attributes, engagement, and list membership, with A/B testing unlocked from Standard.
• Integrations and webhooks for payment events — assembled dunning, not native subscription triggers.
• Entry from e-commerce and marketing integrations without writing code for the common stacks.

Honest limits: billing depth is integration-shaped. Trial expiry, failed payment, and plan-change flows are buildable, but they depend on your webhook mapping staying correct as the payment provider evolves — there is no native subscription object driving the branch the way a billing-first suite does. Complex event-history branching (deep usage sequences, multi-product matrices) also reaches its ceiling earlier than Customer.io-style orchestrators.

The second honest note is feature gating: sophisticated statistics, A/B testing, and deeper automation logic live above the entry tiers. Teams that plan a behavioral program on Starter pricing are often surprised at activation, not by the bill.

Scope the program you actually intend to run, then buy the tier that unlocks it — and treat SMS credits as a separate forecast line rather than an afterthought. Preference and consent flows for SMS especially need deliberate design.

Brevo's case is breadth per dollar, and it is a real one. One $9-to-$18 entry buys email automation, a CRM, and a path to SMS and WhatsApp that would otherwise be three contracts; transactional mail shares the account; and the volume-plus-features axis never penalizes a big dormant list. For small teams whose lifecycle includes chat, lightweight sales tracking, and the occasional SMS deadline nudge, Brevo covers ground a single-channel suite deliberately does not.

The practical comparison for a SaaS team: if your pain is "we need SMS and a CRM cheaply," Brevo wins on that arithmetic.

If your pain is "our failed-payment and plan-change email is held together with tags and cron jobs," map the integration explicitly and test each state. Model the resulting send volume against the tiers in our pricing snapshot.

Common mistakes when adopting Brevo

These patterns show up repeatedly when teams adopt Brevo for lifecycle work — none are platform bugs, and all are avoidable with a day of planning.

• Treating the $9 Starter sticker as the plan for a behavioral program that actually needs Standard's testing and automation gates.
• Starting flows on a blank canvas when the recipe gallery already encodes sane delays — then debugging timing problems the recipe never had.
• Sending routine nurture over SMS and burning the credit budget (and subscriber patience) before trial expiry day.
• Leaving transactional receipts and campaigns in one undifferentiated log, so a campaign spike hides a delivery problem in critical mail.
• Assembling billing webhooks once at launch and never re-testing after payment-provider changes — dunning silently stops firing.
• Never building a winback stage, letting dormant contacts erode engagement metrics month after month.
• Scheduling one generic winback to the whole cold list instead of segmenting by last lifecycle stage and suppressing the truly dead.

Fix order matters: correct the tier fit first, then the channel discipline, then the webhook tests — the rest is iterative hygiene once those three hold.

Re-run the list quarterly; new integrations and new channels reintroduce the same mistakes under different names.

Rollout plan

A 30-day rollout for your first Brevo automations

1. Days 1–5 · Foundations. Authenticate the domain, port contacts, publish a welcome series from a recipe, and confirm transactional streams log separately from campaigns.
2. Days 6–12 · Engagement branch. Split recent engagers from quiet contacts; move quiet contacts to a slower educational path instead of the main cadence.
3. Days 13–18 · Convert moments. Add trial or cart reminders where an integration supplies the event, and reserve SMS for deadline-day nudges only.
4. Days 19–24 · Billing webhooks. Map payment events to entry points, test trial expiry and failed payment in test mode, and document who owns the mapping.
5. Days 25–30 · Winback and review. Launch a dormancy-triggered re-engagement pass, set a sunset rule, and review which flow produced pipeline before adding channels.

FAQ