At a glance
First check your workflow and then the platform. Klaviyo documents the native WhatsApp connection and campaigns, Brevo campaigns and automations, Superchat Team Inbox and keyword opt-ins. The decision depends on what data, responsibilities and approvals your team requires. Each feature must be confirmed in the actual account and the subscribed plan.
Describe the work brief before comparing tools
Describe a single customer touchpoint: for example, a requested reminder about a product launch, an order requiring clarification, or a new sign-up for a series of articles. Note down source data, recipient, consent, message, landing page and the person responsible for replies. A general objective such as ‘more WhatsApp’ cannot be technically verified nor assessed in a commercially meaningful way.
Our own model is a shop selling cycling clothing. It wishes to draw interested customers’ attention to a new collection and have its team answer questions about sizing. To do this, it needs a verified marketing opt-in, a correctly filtered recipient list and a reliable response channel. Extensive automation is only helpful if these steps function fully. Otherwise, it merely shifts the lack of coordination into a new system.
Klaviyo: Connect WhatsApp with existing customer information
Klaviyo describes a native setup process within the WhatsApp settings. This requires a WhatsApp Business account with Meta, the appropriate administrative rights and a suitable telephone number. The official guides deal with consent and WhatsApp campaigns separately. The Mobile Messaging Plan must also be suitable for sending messages. If you are already using a number, check the current migration process or possible co-existence arrangements using the setup documentation.
If your team already maintains shop data and segments in Klaviyo, the shared database is an obvious point to check. Can consents be correctly distinguished and current buyers excluded before a mailing is sent? Is the appropriate template actually available in the account? Who is responsible for providing answers? The existing data will only facilitate a smooth start if events, channel rules and roles have already been reliably maintained.
Brevo: Campaigns and documented automations
Brevo documents the linking of a WhatsApp Business account, telephone number verification, template approvals and scheduled campaigns. Recipients require a completed WhatsApp attribute; supported countries and current sending limits must be checked separately. The automation guide describes, amongst other things, list sign-ups or website events as starting points, as well as waiting times and branching logic. An existing email plan does not in itself prove the availability of the desired WhatsApp feature.
For the model shop, it should be checked whether the necessary shop events actually occur in Brevo and whether the purchase exclusions take effect promptly. The documentation describes possible building blocks, but not an automatically complete data flow for every shop. Please also confirm the scope of the plan, the WhatsApp budget and the separate processing of replies within the account. The pilot should run through the same data scenarios as with Klaviyo.
Superchat: shared inbox and newsletter opt-ins
Superchat describes access to the official WhatsApp Business API, a shared inbox for the team and connections to other tools. The newsletter product page mentions opt-in collection via keywords, templates with media and buttons, variables, as well as planning and analysis. This information suggests a possible focus on the collaborative management of conversations and campaigns. It does not yet guarantee any specific shop integration or performance improvement.
For size-related queries in the model shop, a proper handover is therefore essential: can the next member of staff view the previous history? Who is authorised to approve templates, export contacts or launch a campaign? Is a keyword opt-in, including the wording and timing, recorded in a traceable manner? Clarify ownership of numbers and Meta account access before set-up or migration. Check the features currently included and any additional usage costs in the quote.
Record the decision in a checklist
| Provider | Officially documented focus | To be tested in the pilot |
|---|---|---|
| Klaviyo | Native WhatsApp integration, consent and campaigns | Shop events, segment exclusions, response path |
| Brevo | Campaigns and automations with conditions | Data flow, countries, budget, plan coverage |
| Superchat | Team inbox, keyword opt-ins and newsletter templates | Roles, store integration and conversation handover |
This comparison does not imply that other providers lack any features. Add your own essential criteria and request proof that these are included in the package you book. All providers undergo the same test catalogue within the specific shop.
Check consent, unsubscribing and measurement at the same time
Test the same scenarios with all providers: no WhatsApp opt-in, valid opt-in, subsequent unsubscription, incorrect number, unavailable template language, and a purchase made shortly before sending. Check how unsubscribes affect ongoing automations and imported lists. Membership of a group or a previous service enquiry does not automatically constitute consent to receive marketing messages.
Also, compare the meanings of the reporting columns. ‘Scheduled’, ‘sent’, ‘delivered’, ‘read’ and ‘purchased’ are different stages. Different attribution windows mean that sales figures are not directly comparable. For the pilot, you should therefore measure pre-defined targets, costs and support effort. Our email marketing metrics guide explains the difference between attributed results and a robust comparison.
Secure account access, contractual terms and an exit plan
A useful selection includes the confirmed scope of functions, numbering and account ownership, team rights, data export, contract term and current billing. Also clarify the way forward: which templates, contacts and proofs of consent can be reused should a change occur later? A solution that is convenient in the short term should not make the company dependent on a single personal admin account.
Start with a limited pilot and a designated person in charge. For the bicycle shop, this would be a suitable recipient group with a verified response process. The team will then make a decision based on successful test cases and the actual effort involved.
Sources and further documentation
Product documentation and primary sources relating to the steps described. Editorial source date: 5 October 2026.
