At a glance
Klaviyo connects WhatsApp to a Meta and WhatsApp Business account. Campaigns use approved templates; Shopify data provides potential triggers, but does not replace appropriate WhatsApp consent. Check the setup, language, follow-up enquiries and unsubscribing as a coherent process. Prices depend, amongst other things, on message type, recipient market and your contract.
Distinguish between ‘Business App’ and ‘Business Platform’
The WhatsApp Business app and the Business Platform are different products. A manually managed conversation in the app is not an automated Klaviyo campaign. The Klaviyo guide to linking accounts describes the setup under Settings → WhatsApp using Meta access, business details and a number to be verified. This requires Owner or Admin access in the Klaviyo account.
Clarify who owns the number and Meta account, and who will manage them over time. For an existing number, assess migration and any option to use both systems in parallel separately. Setup, connection and live sending are distinct steps. Document where the team creates campaigns, receives replies and accesses the account. A successful technical connection should lead to a properly managed inbox.
What role do Shopify and the shop data play?
A shop integration can deliver products, orders and customer events. Use your own test profile to check whether the expected purchase, the correct variant and a valid landing page link are received in Klaviyo. An existing checkout flow cannot be automatically transferred to WhatsApp: the data source, timing and sending authorisation must also be correct for the new message.
Klaviyo documents Consent app blocks for Shopify pages. The available placements and features depend, amongst other things, on the Shopify plan. You should therefore check the specific shop rather than following general checkout instructions. A purchase made using a telephone number does not constitute a marketing sign-up. Also test the scenario where a customer allows email but not WhatsApp, and check the result directly in the profile.
Create a clear expectation regarding WhatsApp
When describing the sign-up process, specify the brand, the channel and the intended content. The Klaviyo Guide to WhatsApp Consent distinguishes, amongst other things, between marketing and transactional messages. Consent given for email or SMS does not automatically constitute consent for WhatsApp marketing. Record the actual sign-up method and ensure the displayed explanation is clear and comprehensible.
A model example: A trainers shop invites customers to sign up for updates on limited-edition new releases. The first message confirms precisely this topic and explains how to unsubscribe. A daily general discount series would fail to meet expectations. Also, plan for rejection and subsequent revocation. The technical status in the tool must match the person’s actual preference. Failure to deliver does not justify switching to another unauthorised channel.
Adapt templates to the occasion and language
For campaigns, Klaviyo describes Approved WhatsApp templates with structured text and optional elements. Before planning, check the approval status, the language used and variables. The Meta policy requires approved templates for conversations initiated by the business; replies within the specified service window serve a different purpose.
A brief draft of your own for the trainers shop could read: “The new trail collection is available. You can find sizes and material details here.” A button leads directly to the collection. Only add a first name if the standard version without a name remains legible. Check the text, image, button and landing page as a whole. An incorrectly translated version or an expired offer cannot be rectified by approving the template.
Planning campaigns, flows and responses together
A campaign has a specific occasion and a defined target audience. A flow responds to a customer moment. For both, specify when WhatsApp offers its own benefits and when an email is sufficient. Map a person’s existing contacts onto a timeline. Otherwise, separate channel rules may result in multiple messages repeating the same content in quick succession.
Every dispatch has a corresponding response channel. Who answers questions about sizes, delivery times or an order? Which response is passed on to the service, and when does a human take over? Use an approved address or number to test not only receipt but also follow-up enquiries and unsubscription. The first campaign should be small and straightforward enough for the team to actually manage the dialogue.
How much does WhatsApp marketing cost?
For planning purposes, use the current Meta price information and your own Klaviyo plan. Billing distinguishes between message categories and recipient markets; Klaviyo also describes the classification within the Mobile Messaging plan. A previous price per conversation is therefore not a reliable flat-rate calculation for current campaigns. This guide deliberately does not specify a fixed message price.
Take into account expected delivery, actual category and managed dialogue. Before sending, check whether the cost displayed in Klaviyo fits the budget. Subsequently, evaluate orders and contribution margin alongside messaging costs, unsubscribes and service costs. A high read-through rate may be encouraging, but does not necessarily indicate additional purchases. Where possible, compare results with a suitable control group receiving the same other measures.
Which test cases should be carried out before launch?
- The number used and the business account clearly belong to the correct brand.
- A person without WhatsApp marketing authorisation remains excluded.
- The approved template uses the correct language and complete default values.
- A purchase that has since taken place prevents inappropriate reminders.
- The button and mobile landing page display the advertised product.
- Enquiries are directed to the relevant team, and unsubscribing stops further advertising.
You should then record the actual sequence of events rather than just a screenshot of the editor. If account access, delivery or replies have not yet been tested, part of the operation is missing. Start with a clear use case and only expand the channel once recipient rules and support are functioning reliably.
Sources and further documentation
Product documentation and primary sources relating to the steps described. Editorial source date: 5 October 2026.