MILabs
Integrations

Lead intake assistant for Brevo contacts and lists

How a lead intake assistant reads new enquiries and proposes Brevo contact lists, with a person reviewing each suggestion before it is saved.

Updated 2026-03-29

Lead intake assistant with Brevo

Many small businesses receive enquiries through a website form, a phone message or an email, then copy each one into Brevo by hand. A lead intake assistant reads those enquiries as they arrive, works out what the person is asking for, and suggests the contact list or follow-up sequence that fits. For a team that uses Brevo for its newsletters and reminders, this keeps new contacts in the right place without a staff member sorting them first. At MILabs, we begin by reviewing the forms your team already uses and the lists it already keeps in Brevo. We then map which details are essential, which fields can be left blank, and where a person confirms a suggestion before it lands in a record. The assistant prepares the routing, and the team decides what happens next. It also records the permission each contact gives, so every contact fits Brevo's consent and unsubscribe rules and your newsletters reach people who said yes.

How it works

  1. Collect the enquiry fields from your website form or inbox, and confirm which Brevo lists they should feed.

  2. Pass each new submission to the assistant, which labels the request type and proposes a contact list or sequence.

  3. Have a team member check each suggestion at first, and adjust the labels that keep needing correction.

  4. Write approved changes to Brevo through its API, creating or updating the contact and its list membership.

  5. Keep consent and unsubscribe fields unchanged, so every new contact arrives with the permission the business actually holds.

good questions, straight answers

Frequently asked questions

Can I start with a part of a lead intake assistant on Brevo?
Yes. Many teams begin with one step, such as labelling enquiries from a single form and suggesting a list for each one. A person checks those suggestions for a while, and the assistant then writes to Brevo only when the team is satisfied with the results. Adding a second form, or a second list, is a separate decision that the team can make later. Starting small keeps the review load light and shows early whether the routing rules match how your enquiries actually arrive.
How does MILabs test a lead intake assistant against Brevo?
We run the assistant against a sample of past enquiries and compare its suggested lists with the ones your team actually used. Each mismatch is reviewed to find whether the rule, the prompt or the source data needs changing. Before any write reaches Brevo, we test on a separate test list so that no real contact is affected. Results are shared with your team in plain terms, including the cases the assistant still gets wrong.
What does MILabs do after delivering a lead intake assistant for Brevo?
After handover, we review the assistant's routing with your team at agreed points and look at which suggestions were corrected by hand. Changes to labels, lists or wording are made through a documented update rather than edited directly in Brevo. We also check that the Brevo API connection and any webhook settings still match the account, because platform or form changes can break them. Support questions go through the enquiry form.
Can a lead intake assistant work with Brevo?
Yes, provided the business uses Brevo for its contacts and lists. The assistant connects to Brevo through its API, which allows contacts and list membership to be read and updated. Where an enquiry arrives through a form or inbox outside Brevo, an automation tool can pass the details across first. Whether a particular form or inbox is supported depends on your setup, so we confirm that before any build begins.
What does a lead intake assistant write to Brevo?
It writes only the fields the business has agreed in advance, such as name, email address, enquiry type and the list or sequence chosen. It does not write consent or unsubscribe status on its own, because those come from the contact's own action and the business's records. Each write is logged so the team can see what changed and when. Free-text notes are kept short, and sensitive details that are not needed for follow-up are left out.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.