Have the Brevo campaign built before four o’clock

Why does a companion check your senders first?

Because those are the things that fail silently.

One tool lists your verified sender identities, so a companion knows which from addresses are usable before composing anything rather than building a campaign around an address Brevo will refuse. Another lists folders, because creating a list needs a folder id the platform requires without ever saying so out loud.

Contact data gets the same treatment. A companion lists the custom attributes defined on your account, the real field names in the real spelling, and writes to those. That is the difference between populating COMPANY_SIZE and inventing CompanySize, and it is why the writes are worth trusting.

The four o’clock assembly, in order

Filter the contacts server-side by segment, list or last-modified date, so the audience is a query rather than a guess. Create the list in the right folder, add the matching contacts, remove the ones who should not be there. Draft the campaign, created as a draft unless you ask for a scheduled time. Write or update the template it uses.

Every step is reviewable before the next runs. You see the list count before the campaign is built, and the campaign before anything is queued. What you get is six small artefacts you approved in sequence, which is how marketing work stays checkable when an agent is doing the assembly.

• "Which of my sender addresses are verified, and which campaign drafts are using the others?"
• "Build a list of contacts modified since 1 July who are on the product-updates list but not the beta one."

Who bounced, and what did we send them?

Two reporting tools carry the weight, and they turn email into an operations question rather than a vibe. The daily transactional report returns requests, deliveries, opens, clicks, bounces, blocks and spam complaints per day, which is the series you want when someone says email feels broken this week. The transactional event log goes the other way: filter by recipient address, message id, template or date range and see the delivery, open and click events for one specific person.

Set the approval line before the first send

Firing a campaign is described to the companion as destructive and something to confirm with you first, and in practice it will ask. The browser's own hard-stop list, the one that always interrupts with an approval card as it does for Gmail sends and Teams posts, does not currently include the Brevo sends.

So choose it deliberately. In Settings → AI permissions, Ask Always makes every action pause for approval regardless of the defaults, and for anything reaching twelve thousand inboxes that is the setting you want. The simpler discipline is to let a companion build drafts and keep the last click in Brevo, where the audience count is on screen.

The tools that matter here, lists, folders, contact attributes and unsubscribe flags, exist because permission-based sending has bookkeeping. A companion keeps that bookkeeping for you.

Frequently asked questions