Connect Brevo to Bebaak (marketing e-mail and live chat)

Brevo is optional. Without it, Connect → Marketing sends through your organisation's own mail account (with hourly and daily limits). With Brevo, campaigns and sequences go through Brevo's sending service, and Brevo reports deliveries, opens, clicks, bounces and unsubscribes back to Bebaak. Using the same Brevo account you already use for another business is fine — Bebaak only uses the key you paste and touches nothing else in that account.

Part A — marketing e-mail through Brevo

Before you start

• A Brevo account. Free accounts have a daily sending limit (Brevo shows it on your plan page) — keep Bebaak's “Most a day” at or below it.
• A verified sender in Brevo (Senders, Domains & Dedicated IPs → Senders) and, for good delivery, your domain authenticated there (DKIM / DMARC records — Brevo shows what to add at your domain host).
• In Bebaak you need the right to manage marketing settings (organisation admins have it).

Steps

1. Create an API key. In Brevo: your name (top right) → SMTP & API → API Keys tab → Generate a new API key → name it “Bebaak” → copy it (starts with xkeysib-). It is shown only once.
2. Paste it in Bebaak. Connect → Marketing → Sending & rights → Brevo → paste the key → Save key → Test connection. Bebaak reads your Brevo account once; the status becomes “Connected (test passed)” and names the account. A wrong key says “Test failed”.
3. Sender. On the same page choose Send through: Brevo, enter the sender name and the verified sender e-mail, replies-to address, and your postal address (shown in every marketing mail). Save. The status at the top must say Ready to send.
4. Webhook (opens, clicks, bounces, unsubscribes). Copy the webhook address shown under Brevo on that page (it ends with a secret code). In Brevo: Transactional → Settings → Webhook → Add a new webhook → paste the address → tick: Sent / Delivered, Opened, Clicked, Hard bounce, Soft bounce, Spam (complaint), Unsubscribed, Blocked, Invalid e-mail → Save.
5. Test: Connect → Marketing → Templates → open a template → Send a test to me. It should arrive within a minute. Then send a small campaign to a list of colleagues who agreed; open and click it; the campaign report should show the open and click shortly after.

Go-live checklist

• Domain authenticated in Brevo; sender verified.
• “Most a day / an hour” in Bebaak at or below your Brevo plan's limits.
• Webhook added and a test event seen in the campaign report.
• Your lists contain only people who agreed (Bebaak sends marketing only to “Subscribed” contacts, never to unsubscribed, bounced or suppressed ones).

What Bebaak does with Brevo's events

• Hard bounce / blocked / invalid → the contact is marked Bounced and added to the suppression list. Soft bounce → nothing changes.
• Spam complaint → marked Complained and suppressed. Unsubscribed → unsubscribed in Bebaak too.
• Repeated events are ignored; an unknown webhook address is refused.

Part B — Brevo Conversations live chat (Bebaak's own support)

This lets people with an open support request continue the conversation in Brevo's live chat; agents answer in Brevo and their replies are copied into the request in Bebaak. Without it, the built-in support inbox in the Bebaak console stays the only channel.

1. In Brevo: Conversations → Settings → Widget → Installation code → copy the value of BrevoConversationsID (letters and digits).
2. Bebaak console → Bebaak → Marketing plans & live chat → paste the widget ID and Bebaak's own Brevo API key (from Part A, step 1) → tick “Offer live chat on open support requests” → Save and test. The status must say Live chat on (it stays off until the key test passes).
3. Copy the webhook address shown there. In Brevo: Conversations → Settings → Webhooks (or Integrations → Webhooks) → add it for conversation messages.
4. Ask the server administrator to set BEBAAK_BREVO_CHAT=1 for the app and restart it — this allows Brevo's widget in the app's security policy. Until then the button does not appear.
5. Test: as a test user, open a support request that is with Bebaak → Continue in live chat → write a line; answer it from Brevo; the answer appears in the request in Bebaak (and in the console inbox).

Troubleshooting

• “Brevo refused the key” — key copied incompletely, deleted in Brevo, or an SMTP key pasted instead of an API key.
• Mails not sent, campaign stays “Sending” — the daily / hourly limit is reached (they continue next hour / day), or the sender is not verified in Brevo (failed sends show the reason on the contact).
• No opens / clicks in reports — webhook missing; some mail apps block images, so opens are always an under-count (clicks are reliable).
• Live chat button missing — status not “Live chat on”, BEBAAK_BREVO_CHAT=1 not set, or the request is resolved / with the organisation's own admin.

Security notes

• The API key is stored encrypted and never shown again; Disconnect deletes it and switches sending back to your own mail account.
• Webhook addresses contain a long secret; keep them private. Bebaak never stores Brevo account passwords.