Send iMessages from Klaviyo Flows
The short answer
Yes, with Blue Reacher. Klaviyo's channels are email, SMS, RCS, WhatsApp, and mobile push; iMessage isn't one of them. The wiring is clean anyway: Klaviyo flows include a webhook action that POSTs to any URL, so a flow step calls the Blue Reacher REST API and a blue-bubble iMessage goes out from your dedicated line, with replies and delivery states reporting back over webhooks. No A2P registration required for the line, and $249 per month with unlimited iMessages. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered.
Key takeaways
- Klaviyo sends SMS, RCS, email, WhatsApp, and mobile push on business messaging routes with A2P 10DLC and registered senders.
- Through Klaviyo's webhook action in its flow builder.
- Not the 50,000-profile blast; the line is a considered channel for the segments worth a considered message:
- One white-glove call picks which flows get the webhook step and configures the action with message intent tuning so sends read like a person.
How a message falls back
Doesn't Klaviyo already cover texting?
Klaviyo sends SMS, RCS, email, WhatsApp, and mobile push on business messaging routes with A2P 10DLC and registered senders. Right for 50,000-recipient blasts, wrong for moments where one person needs to answer.
- iMessage is the channel buyers live in, with blue-bubble texts getting opened 98%, read within 3 minutes 90%, flagged as spam under 3%. For high-intent moments, that's the difference between notification and conversation.
- The two run side by side: Klaviyo keeps the broadcast channels, and Blue Reacher takes the segments where a personal-reading text out-converts a campaign.
How does Blue Reacher connect to Klaviyo?
Through Klaviyo's webhook action in its flow builder. Add the action, point it at Blue Reacher's REST API, add phone and message fields in JSON. Klaviyo POSTs when profiles reach that step, with any trigger working: metrics, segment joins, list joins, date properties.
- Replies and delivery states write back as Klaviyo events so flows branch on them; STOP auto-detected, profile suppressed. Non-iMessage contacts get RCS, then SMS fallback.
- Klaviyo requires two-step authentication to add webhooks, and flow webhooks fire server-side only, so test with a real profile before scaling. White-glove team wires everything at onboarding.
Channel
- Klaviyo channels today
- Email, SMS, RCS, WhatsApp, push
- With Blue Reacher
- Blue-bubble iMessage from a dedicated line
Registration
- Klaviyo channels today
- A2P 10DLC and sender registration on carrier routes
- With Blue Reacher
- No A2P registration required
Reads as
- Klaviyo channels today
- A brand broadcast
- With Blue Reacher
- A person texting
Trigger
- Klaviyo channels today
- Flows
- With Blue Reacher
- The same flows, via the webhook action
Cost model
- Klaviyo channels today
- Metered by contacts and sends
- With Blue Reacher
- $249 per line per month, unlimited iMessages (50 opted-in / 30 cold new contacts a day)
Which Klaviyo flows should go blue first?
Not the 50,000-profile blast; the line is a considered channel for the segments worth a considered message:
- High-ticket abandoned checkout: a personal-reading text an hour after the email, referencing the exact item, from a named person
- VIP win-back: your top-decile customers who went quiet get a text, everyone else stays on the email flow
- Subscription lapse: a renewal nudge with a one-question reply beats a discount ladder for retention economics
- Back-in-stock for a waitlisted product: 90% read within three minutes is exactly what a limited drop needs
- Post-purchase check-in on premium orders: the review and referral ask that reads person-to-person
How does setup work?
One white-glove call picks which flows get the webhook step and configures the action with message intent tuning so sends read like a person. Most teams are live within a week.
- Pricing: $249 per line per month or $1,949 per year ($162.50/mo), unlimited iMessages, no per-message metering. Lines pace at 50 opted-in / 30 cold new contacts a day; replies never metered. $449 activation waived on annual.
Frequently asked questions
Can Klaviyo send iMessages natively?
No. Klaviyo's channels are email, SMS, RCS, WhatsApp, and mobile push (klaviyo.com); iMessage isn't available in the product. Blue Reacher adds it through the webhook action in Klaviyo's flow builder, which POSTs to the Blue Reacher REST API when a profile hits that step.
How is this different from Klaviyo's RCS push?
RCS is the carrier upgrade to SMS: branded, registered business messaging with its own verification requirements. iMessage is the blue-bubble thread people use with friends. Blue Reacher sends iMessage first and uses RCS, then SMS, only as automatic fallback for contacts who can't receive it, so each contact gets the best channel their phone supports.
Do I need A2P 10DLC registration for this?
Not for the Blue Reacher line, because iMessage isn't carrier SMS. That's a registration distinction, not a consent exemption: TCPA and your existing SMS consent practices still apply to text outreach, and STOP replies are detected automatically with the profile suppressed from future sends.
Can replies flow back into Klaviyo?
Yes. Replies, delivery states, and opt-outs arrive on Blue Reacher webhooks, and writing them back as Klaviyo events through its API lets flows branch on them: a reply exits the profile from the reminder path, a booked call triggers the confirmation flow. Hot replies can also route straight to the inbox your team answers.
What does it cost next to Klaviyo's pricing?
Klaviyo meters by profiles and sends; Blue Reacher is flat at $249 per line per month or $1,949 per year ($162.50/mo). Lines pace at 50 opted-in / 30 cold new contacts a day; replies never metered. $449 activation waived on annual. Point the line at highest-value segments and the flat fee usually clears on one recovered cart.
See it live on your Klaviyo flows
Book a demo and bring the flow you most want answered, high-ticket abandoned checkout for most brands. We'll add the webhook step, send a real blue-bubble text while you watch, and price it on the spot, because pricing is already public.