Use Cases
Built for the workflows
your team actually runs.
Seven real-world scenarios where connecting Salesforce Service Cloud and Klaviyo makes a measurable difference for B2C brands.
Salesforce Service Cloud
Cases, contacts, opt-outs
flows
Klaviyo Marketing
Flows, profiles, segments
Stop Marketing to Customers With Open Support Tickets
A customer waits 4 days for a damaged shipment resolution. You send them a 20% off promotion.
How suppression works
Suppression Segment
open_case_count > 0Promo Campaign
SuppressedContact excluded
When case closes → property updates → contact re-enters flow
The Problem
A customer contacts support about a damaged shipment. Their case is unresolved and sitting in a queue. The same week, a promotional campaign goes out. The customer receives it while still waiting to hear back — making the brand look oblivious.
How It Works
Open case count syncs to Klaviyo as a profile property with every contact sync. Build a suppression segment on that property and apply it across all promotional campaigns. When the case closes, the property updates automatically and the customer re-enters your normal cadence.
Business Impact
Fewer brand-damage moments during active support interactions. CSAT scores improve. The support team handles fewer "why are you emailing me?" callbacks.
Trigger on case close
Satisfied
Review request + recommendation
Dissatisfied
Recovery sequence
Automate What Happens After a Case Closes
A case closes in Salesforce. Whether the resolution was excellent or mediocre, the customer hears silence.
The Problem
A case closes in Salesforce. Nothing happens on the marketing side. Whether the resolution was excellent or mediocre, the customer hears silence — and the highest-opportunity window in the support lifecycle goes completely unused.
How It Works
A Case Closed event fires into Klaviyo with resolution time, case type, and resolution category. A flow triggers with a conditional split: satisfied customers receive a review request and product recommendation; dissatisfied customers enter a recovery sequence.
Business Impact
Review volume increases from satisfied customers asked at exactly the right moment. High-value customers who had a poor experience are caught before they quietly churn.
Close the Consent Gap Before It Becomes a Legal Problem
A customer unsubscribes Monday morning. Your agent mentions the upcoming promotion on Monday afternoon.
Real-time bidirectional consent
Every change is logged
The Problem
A customer unsubscribes from Klaviyo email. Their Salesforce Contact record still shows them as opted in. A support agent sees "subscribed" and mentions an upcoming promotion during a call. Or the reverse — a customer tells an agent to stop emailing them, and Klaviyo sends another campaign 45 minutes later.
How It Works
Real-time, bidirectional consent sync. An opt-out in Klaviyo updates the Salesforce Contact record immediately. An opt-out recorded by a support agent suppresses the Klaviyo profile within seconds. Email and SMS consent are maintained separately. Every change is logged with a source and timestamp.
Business Impact
Eliminates the window between an opt-out and actual suppression. Substantially reduces exposure under GDPR, CCPA, CAN-SPAM, and TCPA.
Case-aware abandoned cart flow
Cart Abandoned
Standard trigger fires
Conditional Split
open_case_count"We're working on your question - your cart is saved."
"Looks like you left something behind."
Make Abandoned Cart Flows Aware of Open Support Tickets
They opened a ticket asking about sizing. An hour later, Klaviyo sends: "Looks like you left something behind."
The Problem
A customer adds items to their cart, opens a support ticket with a product question, and leaves without buying. Klaviyo's standard abandoned cart flow fires automatically: 'Looks like you left something behind.' The customer is literally waiting for your team to answer their question.
How It Works
Add a conditional split to your abandoned cart flow using the open case count property synced from Salesforce. If an open case exists, the customer receives a different message — acknowledging their question is being worked on and confirming their cart is saved. If no open case exists, the standard flow runs.
Business Impact
Converts a potential brand-damage moment into a trust moment. Customers who feel acknowledged are more likely to complete the purchase once the case resolves.
Give Support Agents Marketing Context
Your agent is handling a case. The customer is mid-flight in a winback flow. Neither of them knows.
Klaviyo activity in SF Service Console
Contact Info
Case #4821
In ProgressRecent Marketing Activity
Synced from Klaviyo as SF Task records
The Problem
A support agent handles cases with an incomplete picture of who they're talking to. They can see case details and order history. They cannot see whether the customer recently clicked through a sale email or whether Klaviyo has them in a winback segment.
How It Works
Klaviyo engagement events — opens, clicks, and campaign interactions — sync back into Salesforce as Task records, visible from the Contact record in the Service Console. Agents see recent marketing activity without leaving the case view.
Business Impact
Agents calibrate their approach based on marketing context. A customer who just clicked your retention campaign gets a different conversation than one who has been inactive for six months.
Pattern detection across systems
60-day support history
case_count_60d ≥ 3At-risk segment
Proactive outreach triggered
Before the customer decides to leave
Catch Repeat Complainers Before They Churn
Third support case this month. Each resolved in isolation. Nobody connected the dots. Marketing: normal.
The Problem
A customer submits their third support case in 60 days. Each was resolved individually. No one connected the pattern. Marketing continues as normal. The two strongest early-warning signals for churn — purchase behavior and support contact frequency — are in separate systems with no connection between them.
How It Works
Open case count and case history sync as Klaviyo profile properties with each contact sync. Build a segment on support frequency and combine it with Klaviyo churn risk signals to identify customers who need proactive outreach before they quietly leave.
Business Impact
Early intervention before the decision to leave has been made. The only time a retention play works is before the customer has mentally checked out.
Use Case Data as a Marketing Content Signal
Your product launch is generating a surge of 'how does this fit?' support cases. You send another product campaign.
Case data → content targeting
Salesforce · case_type distribution (last 30d)
Klaviyo segments → targeted content
case_type = sizing_issue→ Size & Fit Guidecase_type = compatibility→ Compatibility CheckerThe Problem
A product campaign launches. Cases start coming in about the same confusion — sizing, compatibility, or installation issues. The marketing team has no visibility and keeps sending messaging that generates more support contacts.
How It Works
Case type and priority sync as profile properties in Klaviyo. Segment customers by the type of support interaction they have had and send targeted content that addresses their specific experience — a fit guide, a compatibility explainer, or an exchange-friendly offer.
Business Impact
Fewer repeat cases when marketing proactively addresses common confusion. Campaign content becomes relevant to what customers are actually experiencing.
Get Started
Ready to make these workflows real?
Request early access and get direct onboarding support from the Solvative team.
Request Early Access