Send Brevo Transactional Emails and SMS From a WhatsApp Chat

By Alva Chew 5 min read Updated November 11, 2026

Yes. AeroChat works directly with Brevo. When a customer asks in the chat for an email or a text, such as their order confirmation again, an invoice or a pickup code, AeroChat sends it through Brevo’s transactional email or SMS API, using the templates you already built in Brevo and the details from your store.

This recipe sends the one-off messages customers ask for in chat from the same Brevo account that sends your store’s other emails, so they look the same and show up in your Brevo logs. On WooCommerce, the Brevo plugin already sends your order emails through Brevo, and AeroChat uses the same account. Part of connecting Brevo to WhatsApp and AI chat.

What happens today

A customer messages on WhatsApp: “I never got my order confirmation, can you send it again?”. Or they need the invoice for their company, or the pickup code for a click-and-collect order. Someone finds the order, opens WooCommerce or Brevo, and resends it by hand, or types the details into the chat, which is not what the customer’s accounts team wants.

The flow that works

  1. The customer asks for an email or a text about their order.
  2. AeroChat finds the order in your store and checks the email or phone number on it matches the customer.
  3. It confirms the email address or mobile number to send to.
  4. It sends your Brevo template by email, filled with the order number, items and total, or sends a short transactional SMS.
  5. It tells the customer it has been sent and where to look.

What it looks like on WhatsApp

Customer: Can you email me the invoice for order 30871? I need it for work. (example)

AeroChat: Of course. I’ll send it to the email on the order, j.lim@example.com. Is that right?

Customer: Yes.

AeroChat: Sent. Look for an email from us with the subject “Your invoice for order 30871”. If it isn’t there in a few minutes, check your spam folder.

In Brevo: a transactional email using your Invoice template (example) is sent to j.lim@example.com, filled with the order number, items and total, and shows in your transactional logs.

The recipe

Copy this into AeroChat

When a customer asks us to email or text them something about their order, such as the order confirmation, an invoice or a pickup code, follow these steps.

  1. Ask for their order number if we do not have it. Find the order in our store and check that the email or phone number on it matches the customer. If it does not match, do not send anything.
  2. Confirm the email address on the order, or the mobile number with the country code, before sending.
  3. For an email, send our Brevo transactional template for that request: Order confirmation (example) or Invoice (example). Fill it with the order number, the customer’s name, the items and the total.
  4. For a text, send a Brevo transactional SMS from our sender name with one short message, for example “Your pickup code for order 30871 is 4821 (example)”. Do not add marketing content or an opt-out line to a transactional text.
  5. Tell the customer it has been sent and where to look.

Never send to an address or number that is not on the order unless our team approves it. Never send marketing content through this workflow. Reply in the customer’s language.

Change the template names to the transactional templates in your Brevo account before you paste it.

What to connect

  • Your store. WooCommerce or Wix, built in. Connect it in the AeroChat dashboard so AeroChat can find the order. For WooCommerce, add a REST API key with read access to orders.
  • Brevo. An admin creates an API key in Brevo’s SMTP and API settings and copies it. Paste it in when AeroChat asks.
  • Brevo templates and SMS. Build the email templates in Brevo with variables for the order details. For texts, SMS needs to be set up in your Brevo account with a sender name. Brevo allows up to 11 characters for a sender name made of letters.

Brevo treats an SMS that contains an opt-out line as marketing, even if it is sent as transactional. That is why the recipe keeps texts short and leaves the opt-out line out. Brevo documents both endpoints in its developer documentation.

After you paste the recipe, AeroChat builds the workflow as a draft and shows a checklist: connect Brevo, add your knowledge base if the recipe uses one, then switch it on. If it built the connection from Brevo’s public documentation, the checklist asks you to check it once against the current docs.

Using a different system? If it has a public API, it connects to AeroChat the same way: describe what you want, paste in its key, and it runs.

Can’t find your tool? Message us in the chat on this page and we’ll tell you how it connects.

What you still decide

  • Which messages customers can ask for in chat, and which template each uses.
  • Whether AeroChat may send to a new address, or only to the one on the order.
  • Which requests get an SMS rather than an email.

The result to expect

Customers get the confirmation, invoice or code they asked for in seconds, from your own Brevo templates. Your team stops resending order emails by hand.

Measure it with your own numbers: resend requests handled in chat per month, and time your team spent on them before.

See also: update a customer’s contact details in Brevo.

Works on every chat channel

This workflow runs the same way on WhatsApp, Instagram, Facebook Messenger, Telegram, the chat on your website and email, with the same Brevo connection behind it. See what each channel does on the Brevo integration page.

Resend your next order email from the chat

Paste the recipe, add your Brevo API key, and ask your own chat to resend a test order confirmation.

Start your 7-day free trial. No credit card needed.