Klaviyo SMS setup for France: consent, campaigns, and flows

Short answer. Enable SMS, select or add France as a sending country, activate the current supported sender, and verify the displayed brand and unsubscribe path. Collect SMS-specific consent through a localized form or checkout choice, preserve evidence, and build France-only eligibility segments. Enforce carrier quiet hours, then launch one small campaign and one controlled flow before scaling.

Klaviyo SMS setup is not complete when the sender appears in the account. A production launch needs consent architecture, destination routing, message classification, profile states, pressure rules, flow exits, cost controls, and real-device QA.

As re-checked August 10, 2026, Klaviyo's country availability guide lists France with branded sender ID and SMS support, but not MMS, and the sending numbers table shows no long code, short code, or toll-free option for France. The platform's SMS consent guide requires SMS-specific agreement and an active sender in the relevant supported country before consent collection. Confirm current product behavior in the live account.

Step 1: write the SMS implementation specification

Before changing settings, document:

• legal entity and customer-facing brand;
• recipient countries and languages;
• promotional, transactional, and order-update use cases;
• sending owner and backup;
• collection sources;
• current phone and consent data;
• ecommerce and subscription events;
• campaign and flow priorities;
• expected monthly messages by destination;
• quiet hours and frequency policy;
• unsubscribe method;
• support and incident process;
• measurement and holdout plan.

France should have its own row, even inside a global program. Sender type, reply behavior, quiet hours, language, price, and consent expectations differ by market.

Step 2: enable SMS and configure France

In the current Klaviyo setup flow:

1. open SMS settings or the onboarding wizard;
2. select the primary sending country and relevant sender type;
3. add France or contact support if the account architecture requires it;
4. choose the mobile messaging plan or spend;
5. complete any current verification or registration;
6. review the displayed sender;
7. configure brand, company, and disclosure settings;
8. test with controlled French numbers.

Klaviyo says the primary SMS country affects number types and compliance rules, and changing it later may require Support. International brands should design the market structure before enabling a default US or UK sender.

The current France row lists a branded sender ID. Branded IDs are one-way and cannot receive replies, opt-in keywords, opt-out keywords, conversations, or conversational flows. Build the program around a supported unsubscribe link or other current one-way method.

MMS is not currently supported in Europe according to the availability guide. Do not design image-based flows for French numbers without verifying a product change.

Step 3: model phone and market data

Normalize phone numbers to international E.164-style format, including +33 for France. Handle the French domestic leading zero correctly during normalization. Use a tested phone parsing library rather than string replacement.

Keep:

• original entered value where needed for troubleshooting;
• normalized phone;
• country derived and then verified;
• locale and preferred language;
• profile or customer ID;
• channel consent state;
• source and timestamp;
• disclosure version;
• confirmation state;
• suppression and opt-out history.

Do not infer current physical location only from the number. A French number can travel, and a person can use a number outside France. Use the number country for routing and the profile's current customer context for localization.

Decide how email-only, SMS-only, both-channel, transactional-only, and order-update profiles appear. Create test profiles for every state.

Step 4: collect consent through supported paths

Possible paths:

• Klaviyo popup or embedded form;
• multi-step email then SMS form;
• checkout checkbox;
• account or preference center;
• Customer Hub when current plan and store support it;
• email opt-in invitation;
• QR code or subscribe page;
• third-party form integrated through supported API behavior.

Every SMS choice should be distinct from email, unchecked, and optional. Show brand, purpose, relevant frequency or rate information, unsubscribe, and privacy access according to the applicable program.

Do not collect SMS in Klaviyo for a country where the account has no active supported sender. The platform says consent collection requires SMS enabled and a sending number for that country.

Multi-step form

A common structure:

1. email value and email consent;
2. success state or optional SMS invitation;
3. French SMS disclosure and phone input;
4. confirmation and expectation.

The person should be able to complete email signup without SMS. Do not disguise the second step as necessary.

Checkout

Place SMS marketing choice separately from phone collection needed for delivery. Label the checkbox clearly and keep it unchecked. Ensure the ecommerce integration passes phone and consent correctly, not just the number.

If using Shopify order-update consent or Klaviyo transactional consent, explain the narrower purpose and test the exact platform state. Do not promote to that profile unless broader promotional eligibility exists.

Third-party forms

Map the consent event, disclosure version, and source, not only the phone. Use approved API endpoints and current Klaviyo requirements. Reconcile counts and sample profiles after sync.

Step 5: choose opt-in confirmation behavior

Single or double opt-in behavior depends on platform support, consent type, market, and risk policy. Double opt-in can strengthen evidence and number quality where available, but it adds a completion step.

Two France-specific behaviors decide this step. The classic double opt-in confirmation text is skipped automatically wherever a branded sender ID is used, because the subscriber has no way to reply. Smart Opt-in still works: the visitor enters a number, receives a one-time code sent from a Klaviyo-managed short code, and confirms without leaving the site. It requires a paid SMS plan, and downgrading to a free plan breaks forms already built on it.

Klaviyo also notes that transactional consent always uses single opt-in and cannot be combined with Smart Opt-in or tap-to-text. Promotional and order-update paths have different behavior. Verify the live documentation before choosing.

Measure:

• form submissions;
• confirmation message delivery;
• confirmed subscriptions;
• invalid or unreachable numbers;
• time to confirmation;
• support contacts.

Do not send ongoing promotion to unconfirmed profiles where the chosen process requires confirmation.

Step 6: create eligibility segments

Build a base France SMS promotional segment:

• can currently receive SMS marketing;
• phone country is France or current supported France route;
• valid phone exists;
• not suppressed;
• not a test or internal profile.

Then add relevance:

• recent customer or engagement;
• product or category interest;
• requested restock;
• loyalty status;
• event participation;
• recent campaign or flow pressure;
• no conflicting support or operational issue.

Build monitoring segments:

• France phone but unknown consent;
• SMS consent but missing market;
• SMS profile without language;
• recently opted out;
• transactional-only;
• order-update-only;
• invalid or bounced;
• unexpected subscriber spike.

Do not turn monitoring segments into campaign audiences accidentally. Use a naming standard and folder or tag convention where supported.

Step 7: configure quiet hours and sending windows

Klaviyo's current compliance guide lists France carrier quiet hours:

• before 8:00 a.m.;
• after 10:00 p.m.;
• all Sundays;
• public holidays.

Use recipient local time and a stricter internal window if appropriate. A practical promotional policy might be narrower than the technical maximum.

Check how smart sending, scheduled campaigns, flow delays, recipient time zones, and quiet-hour deferral interact. A message deferred from Sunday should not arrive at an irrelevant moment on Monday.

Create QA dates for:

• normal weekday;
• Saturday;
• Sunday;
• French public holiday;
• daylight-saving transition;
• missing time zone;
• campaign spanning multiple countries.

Keep transactional user-requested messages in a separately governed path. Do not disable all safeguards globally to accommodate a security-code use case.

Step 8: write the first campaign

Choose a low-risk, highly relevant audience and one useful action. For example, a requested restock or loyalty access.

Campaign checklist:

• current SMS promotional eligibility;
• France destination;
• brand identified;
• one reason and one link;
• terms visible;
• supported unsubscribe method;
• stock and landing page current;
• recent purchasers excluded;
• quiet hours checked;
• message segment count and cost reviewed;
• email and flow overlap reviewed.

Because French branded sender IDs are one-way, do not include Reply STOP. Use the current unsubscribe link or supported method.

Send to an internal controlled list first, then a small production cohort. Monitor delivery, clicks, conversion, opt-out, support, and carrier behavior before expansion.

Step 9: add SMS to ecommerce flows selectively

Do not copy the email flow and replace the channel.

Welcome SMS

Send only to promotional SMS subscribers. Confirm the brand and promised program, deliver the specific value, and avoid stacking several immediate messages after email signup.

Checkout abandonment

This is marketing, not transactional. Use promotional eligibility, a supported ecommerce trigger, order exclusion, quiet hours, and strict frequency. Keep the text useful and avoid automatically discounting.

Post-purchase

Separate:

• necessary order or delivery update;
• relationship guidance;
• promotional cross-sell.

Use the correct consent or service purpose for each. A promotional post-purchase text needs marketing eligibility even when the person bought.

Replenishment

Use product, quantity, purchase date, and current subscription status. Exclude customers who reordered, subscribed, refunded, or have a product issue. Test timing against a holdout.

Subscription lifecycle

Use authoritative renewal, skip, failure, pause, and cancellation events. Account-management links should be secure and current. Keep save offers separate from necessary billing information.

Restock

Send to people who requested the specific product where the collection path and current consent support it. Exit after purchase and cap repeated restock messages.

Winback

Use only for a consented, still-relevant audience. SMS is rarely the right first step for very cold profiles. Combine expected purchase cycle, recent engagement, and customer value.

Step 10: set channel pressure rules

Document message priority:

1. user-requested security or necessary service;
2. critical order or subscription information;
3. high-intent lifecycle;
4. planned campaign;
5. lower-priority education or winback.

Use Klaviyo smart sending and exclusions where they match the rule, but understand its exact current evaluation. Some critical flows may need different smart-sending behavior from campaigns.

Review email, SMS, push, WhatsApp, and support together. A customer should not receive a checkout email, checkout SMS, sale campaign, and review request within the same hour.

Set ordinary caps by customer state, not only channel. VIP status does not mean unlimited attention.

Step 11: manage cost and message segments

Klaviyo's current billing documentation uses monthly Mobile Messaging spend and destination-dependent rates. Unused mobile messaging dollars currently do not roll over. Check live rates and billing settings.

Budget:

• eligible subscribers;
• messages per flow and campaign;
• destination mix;
• character encoding;
• long-message segmentation;
• unsubscribe text and links;
• seasonal peak;
• retry or duplicate risk;
• unused prepaid amount.

Preview accented French text. GSM and Unicode encoding can change the number of SMS segments. Shortening useful disclosure to save cost is not an acceptable strategy. Rewrite the message and choose the channel appropriately.

Calculate incremental contribution, not attributed revenue alone.

Step 12: build monitoring and incident response

Monitor:

• new SMS subscribers by source;
• consent confirmation;
• active and suppressed profiles;
• attempted, delivered, and failed messages;
• carrier or route anomalies;
• cost and message segments;
• opt-out;
• complaints and support;
• flow entries and exits;
• duplicate sends;
• country and quiet-hour violations;
• conversion and net economics.

Create alerts for sudden subscriber spikes, send-volume spikes, unusual failure, unsubscribe increase, and spend threshold.

Incident runbook:

1. pause campaigns and affected flows;
2. preserve logs and configuration;
3. identify audience, messages, and time;
4. stop source event or bad import;
5. involve privacy, security, legal, and vendor owners as needed;
6. correct suppression or data;
7. communicate appropriately;
8. document root cause and preventive control.

End-to-end QA matrix

Test on real French carrier destinations and representative devices. Save evidence with the launch checklist.

Rolling out SMS on top of your existing flows raises new compliance and sequencing questions, and a free 30-minute Klaviyo audit is a quick way to make sure yours are set up correctly.

FAQ

What sender does Klaviyo use in France?

Its current availability table lists a branded sender ID. That sender is one-way, so replies and keywords are not supported. Confirm current activation and display in the account.

Can Klaviyo send MMS in France?

Not currently according to the published European availability table. Use SMS and mobile landing pages, and verify future product changes.

Can I import existing phone numbers into SMS marketing?

Phone numbers alone are not consent. Import promotional eligibility only with valid, brand-specific evidence and correct market mapping. Otherwise retain the number for the appropriate non-marketing purpose without subscribing it.

Which Klaviyo flows should use SMS first?

Start with one high-intent, time-sensitive use case supported by reliable data, such as requested restock or a carefully governed abandonment step. Avoid adding SMS to every email flow.

How should Klaviyo SMS ROI be measured?

Use delivery, message and offer cost, net margin, opt-out, complaint, and incremental lift through holdouts or controlled rollout. Platform attribution alone can overstate the effect.

Launch one safe use case, then scale

Deliver, our Klaviyo audit team, configures France routing, consent, data, segments, flows, campaigns, QA, and reporting as one Klaviyo SMS system. Request a France Klaviyo SMS implementation.