Log support requests on the Brevo contact
A help request creates or updates the Brevo contact and records what was asked, so follow-up email sends from one profile.
New support or contact form submitted
Create or update a Brevo contact and log the request as an attribute
One-directional. A submission triggers the action — nothing is written back into your form.
Support email tends to fragment. The same customer writes in from two addresses, someone replies from a shared inbox, and the marketing side of the business has no idea the person has an open problem when the next campaign goes out.
Putting the request onto the Brevo contact keeps one profile per person. Small teams without a dedicated helpdesk use this most: the contact form is the front door, and Brevo is already sending their transactional mail.
Setting it up
- 1
Publish the contact form on your help page, using conditional logic if billing questions and technical ones need different follow-up fields.
- 2
In Brevo, add text attributes for the request itself, such as LAST_SUBJECT and LAST_MESSAGE, plus a date attribute for when it came in.
- 3
In Zapier, point the New Submission trigger at that support form and pull through a sample submission to map from.
- 4
Use Brevo's create or update contact action matched on Email Address, so a repeat customer updates an existing profile rather than creating a second one.
- 5
Map Subject into LAST_SUBJECT and Message into LAST_MESSAGE, so the request text is readable directly on the profile.
- 6
Map Phone Number into Brevo's SMS field only if you actually send SMS; otherwise keep it as a plain text attribute to avoid validation errors.
- 7
Add the contact to a support list if a Brevo automation should send the acknowledgement, since an attribute update alone will not start a list-based workflow.
- 8
Send a test request from your own address, check the profile shows the subject and message, then turn the Zap on.
What maps where
Using the Contact Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Brevo |
|---|---|
| Full Name | FIRSTNAME on the Brevo contact |
| Email Address | The contact's email address, used to match an existing profile |
| Phone Number | The SMS field, or a plain phone text attribute if you do not send SMS |
| Subject | A LAST_SUBJECT attribute that gives the request a readable label |
| Message | A LAST_MESSAGE text attribute holding what the customer wrote |
Variations worth knowing
Point a Brevo automation at the support list so every new request gets a short confirmation carrying your expected response time. It is one email, and it heads off the second did-you-get-this message that otherwise arrives an hour later.
An unhappy customer does not need a promotion the same afternoon. Have the Zap set an OPEN_ISSUE attribute on the contact, then exclude anyone carrying that value from your next campaign until support has cleared it.
If something isn't arriving
Brevo attributes hold a single value, so LAST_MESSAGE is always the most recent request by design. Keep the responses list as your archive of everything that was ever sent, and treat the Brevo attribute as a snapshot.
They wrote in from a second address. Brevo matches on email only, so merge the duplicates there, and consider asking for an account or order reference on the form to make the next pair obvious when it happens.
Frequently asked questions
Does this replace a helpdesk?
No. It gives Brevo an accurate contact record and a trigger for transactional mail. Ticket queues, assignment and status tracking belong in a helpdesk tool, which you can add as a second Zapier action if you need both.
Will a reply sent from Brevo show up on the submission?
No. Nothing is written back into the form. The submission stays exactly as the customer sent it, and every exchange after that lives in Brevo or in whichever inbox your team answers from.
Can I send a different acknowledgement per request type?
Yes. Branch in Zapier on the Subject value and add the contact to a different Brevo list on each branch. Every list can have its own automation, so a billing question gets a different reply than a bug report.
Related automations
- Add newsletter signups to a Brevo list
Every footer signup becomes a Brevo contact in your newsletter list, with the topics they chose already attached.
- Add webinar registrations to a Brevo reminder list
Each registration becomes a Brevo contact on the list for that session, with company and job title already filled in.
- Send gated guide downloads to a Brevo list
The download form adds the reader to a Brevo list with attributes for the asset and the date they asked for it.
- Start a Brevo nurture workflow for demo requests
A demo request creates the Brevo contact, records what the prospect wants to solve, and enters them into your welcome automation.
- Store survey scores as Brevo contact attributes
Post-purchase survey answers update the Brevo contact with a score and a comment you can segment a follow-up send on.
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free