Operating ProcedureExecution layer

Brevo Client Workspace Setup (Onboarding)

A checklist with 8 steps: Create the client's Brevo account under the agency's own login and confirm the plan tier before importing anything.

By InnovaAI ResearchPublished

What are the steps?

checklist

Brevo Client Workspace Setup (Onboarding)

  1. 01

    Create the client's Brevo account under the agency's own login and confirm the plan tier before importing anything

    The free tier caps multichannel automation at 2,000 contacts and allows a single user, so decide early whether the client needs Starter at $8.08/mo (up to 500K contacts, 100k monthly email sends) or a higher tier. A single-user limit blocks delivery teams from sharing access, so plan seat ownership before the pilot goes live.

  2. 02

    Complete sender authentication for every sending domain the client owns

    Configure SPF, DKIM, and DMARC records in the client's DNS panel and verify them inside Brevo's sender settings. Deliverability failures at launch are almost always authentication gaps, not content problems, and they surface within the first send.

  3. 03

    Import the client contact list with segmentation fields mapped before the first campaign

    Map custom attributes (purchase date, store location, opt-in source) during import so the welcome automation can branch on real data. Lists imported without attributes force a rebuild later and break reporting continuity.

  4. 04

    Build the multichannel welcome series in the visual automation builder

    Sequence email first, then SMS, then WhatsApp where the client has consent for each channel. Keep the entry trigger tied to a single opt-in event so contacts do not receive duplicate welcomes from overlapping lists.

  5. 05

    Connect the client's commerce and payment stack

    Wire Shopify, WordPress, Stripe, and Zapier where relevant so order and payment events feed automations and transactional messaging. Confirm each integration fires a test event before handover.

  6. 06

    Configure transactional messaging via SMTP or API for the client's product team

    Issue API keys scoped to transactional sends only, separate from marketing campaign access. Document the endpoint and key rotation owner in the client handover pack.

  7. 07

    Set reporting baselines and flag the white-label gap in the client agreement

    Brevo does not publish white-label branding options, so client-facing dashboards and reports will carry Brevo branding. Agree with the client whether reports are exported and rebranded by the agency or shared directly, and record the decision before the retainer starts.

  8. 08

    Run a live test send across all active channels and log the result

    Send one email, one SMS, and one WhatsApp message to agency-owned test contacts, then verify delivery, tracking, and CRM record creation. Delivery sign-off on this test is the gate before the client's first real campaign.