Integration · Email and SMS
Sociana + Brevo
Brevo is one provider the Sociana team has discussed for transactional email and WhatsApp sending. If your organisation has a Brevo account, confirmation emails, OTPs and campaigns can be routed through it, with delivery logs kept in Sociana. Use is agreed per occasion and is not a listed partnership.
Built per event
What it does inside Sociana
Transactional email keeps an occasion moving: login codes, booking confirmations, invoices. Sociana supports configurable OTP, ticket and invoice messages, sender configuration and email delivery logs. Brevo, which offers email, SMS and WhatsApp in one account, has been discussed alongside AiSensy and Twilio as a provider. Separately, the Sociana website's own lead form uses Brevo for its contact pipeline; that is the marketing site, not the product.
What the organiser configures
- Your Brevo account, a verified sender and sending domain (SPF, DKIM)
- Message text for OTP, ticket and invoice emails
- Fallback channel when email does not arrive
- Audiences by group for campaigns
Data that flows, and where it is stored
| Data | From | To | Stored |
|---|---|---|---|
| Email address, name and message variables | Sociana member record | Brevo | Message content and event data at Brevo; send record in Sociana delivery log |
| Delivered, bounced and opened events | Brevo | Sociana delivery log | Sociana database (hosting region on request) |
Data protection (DPDP)
The organiser is the Data Fiduciary and Sociana acts as processor. Ask us for the hosting region and retention period that apply to your occasion; the sub-processor list is on the Sub-processors and integrations page. We do not state a region or retention period on this page.
Security notes
- Email addresses and names pass to Brevo; Brevo would appear on the sub-processor list if used.
- Domain authentication (SPF, DKIM) is the organiser's responsibility.
Set-up checklist
- Decide whether Brevo is the right provider; ask the delivery team before purchasing a plan.
- Verify your sending domain so confirmations do not land in spam.
- Write and review the OTP, ticket and invoice emails.
- Share API credentials securely and send test messages to an internal group.
- Check the delivery log and the Spam or Junk folder on the day of the first send.
Limits, stated plainly
- Brevo is one provider option; the provider for your app is agreed at project start.
- Brevo's plan limits, charges and delivery terms apply.
- Opens and clicks depend on the recipient's mail client and are not reliable counts.
Not offered yet
- A listed Brevo partnership
Pricing note
Brevo charges its own plan and sending fees to the organiser.
Indicative figures are not a quote. Pricing explains how scope moves the price.
At a glance
- Provider
- Brevo
- Status
- Built per event
- Set up by
- The Sociana delivery team, with your accounts
Questions people ask
Does Sociana require Brevo for email?
No. Email sending runs through a configured provider, and Brevo is one that has been discussed. The choice is made at project start and the provider contract is yours.
Is the Brevo on the Sociana website the same thing?
No. The marketing site's contact form uses Brevo for its own lead pipeline. That is separate from how an occasion app sends email, which is set per organisation.
Where do I see whether an email was sent?
In the delivery log in the admin panel. It shows what was sent and the provider's status. A log entry is not a promise of arrival, so the first send should always go to an internal test group.
Need this connected for your event?
Tell us which tools your team already uses. We will show you where the data lands and who sees it.