Insights
Do You Actually Have a Customer Experience Strategy?
Casey Rowland
TL;DR:
A customer experience strategy is a testable operating plan, not a values statement. Score yourself against four questions to find out if you actually have one.
Most teams that believe they have a CX strategy are guessing on at least two of the four.
The named frameworks (KPMG's six pillars, the "three C's," etc.) mostly aren't agreed industry standards, don't spend your energy picking the "right" one.
AI resolution is a lever for the questions below, not a substitute for answering them first.
Ask most support leaders if they have a customer experience strategy and they'll say yes. Ask them four specific questions about it and the answers usually get vague fast. That gap, between believing you have a strategy and being able to state it plainly, is where most CX strategies actually fail.
Here's the test. Four questions. Answer each one in a single sentence, out loud or on paper. If you can't, that's not a communication problem, it's the actual gap.
Question 1: Which ticket types get resolved immediately, and which need a human?
Not "we try to help people fast." A real answer names ticket types: order status and simple returns get an instant answer, anything touching a refund exception or an angry customer goes to a person, subscription changes get an AI-first attempt with a human backup.
Here's what a real answer sounds like for a mid-size ecommerce brand: "Where's my order" and tracking questions resolve instantly, every time, no human touches them. Standard returns within the policy window (unworn, tags on, inside 30 days) resolve instantly too. Anything outside the policy window, a damaged or wrong item, or a subscription cancellation request goes to a person, because those carry judgment calls or retention conversations a fixed rule shouldn't make alone. That's four ticket types, three resolution paths, stated in one breath.
Compare that to the vague version: "We handle most things pretty quickly and escalate the complicated stuff." That sentence contains zero decisions. It doesn't say what "complicated" means, so two different agents (or an AI agent and a human) will draw that line in two different places, on the same day, for the same ticket type.
If your answer named specific ticket types, you passed. If your answer was a feeling ("we try to be quick"), that's gap #1.
Question 2: Who's accountable when a ticket falls outside those paths?
Every strategy has edge cases, tickets that don't fit the defined resolution paths. The question is whether there's a named owner for those, or whether they just drift between people and tools until someone happens to notice.
This is the gap that shows up as a specific, recognizable failure: a customer asks where their order is, gets told it shipped, the tracking shows it stuck at a carrier facility for six days, and now the ticket needs someone who can actually contact the carrier or authorize a reship. If there's no named owner for "carrier problems the AI or tier-one agent can't resolve," that ticket sits. It doesn't get closed, it doesn't get escalated cleanly, it just ages in a queue until the customer follows up angry, at which point it becomes a retention problem instead of a logistics one. The failure isn't that the issue was hard. It's that nobody owned the moment it became hard.
If you can name a person or role for that exact kind of ticket, you passed. If the honest answer is "whoever sees it first," that's gap #2, and it's usually the most expensive one, because vague ownership is where tickets go quiet.
Question 3: What's the actual rule for escalating, not the vibe?
"Escalate when it feels hard" is not a rule. A rule is a trigger: an SLA about to breach, a specific ticket type, a sentiment signal, an account tier. If two different agents would make different escalation calls on the same ticket, there's no rule, there's improvisation.
Concrete triggers that actually work in ecommerce: a chargeback or dispute notice, always escalates, no exceptions, because it has a legal clock attached. A subscription cancellation request from an account above a certain lifetime value, escalates to a retention specialist rather than getting auto-processed. Negative sentiment detected twice in the same thread, escalates regardless of ticket type, because a customer repeating themselves angrily is a signal on its own. Each of those is a trigger you could write down and hand to a new hire on day one, and they'd make the same call an experienced agent would. For a deeper breakdown of functional vs. hierarchical escalation and how to keep context intact on the handoff, see our escalation management playbook.
If you can state the trigger the same way twice, you passed. If escalation depends on which agent is on shift, that's gap #3.
Question 4: How do you know if it's working?
Not "customers seem happier." A real answer names a number: first-contact resolution rate, split by automated vs. human-handled tickets. Escalation rate. Reopen rate. Something you actually look at on a recurring basis, not something you'd have to go build a report to answer.
A useful gut check here: if your CSAT is steady in the 75-85% range most CX teams treat as healthy but your reopen rate is climbing, you don't have a satisfaction problem, you have a "resolved" tickets that aren't actually resolved problem, and CSAT alone will hide it from you. That's the trap with tracking one number: a metric that looks fine in isolation can be actively misleading about whether the strategy is working.
If you named a metric you already track, you passed. If you'd need to ask someone to pull a number that doesn't exist yet, that's gap #4, and it means you can't tell if changes you make are helping or hurting.
Score yourself
4 for 4: You have a real strategy. The rest of this is a tune-up, not a rebuild. 2 or 3: You have pieces of a strategy and at least one real gap, usually ownership or measurement. Fix the gap before you add anything new, like an AI agent, on top of it. 0 or 1: What you have is a set of habits, not a strategy. Start with question 1, it's the one everything else depends on.
A worked example
Take a hypothetical 12-person DTC skincare brand doing about 400 tickets a week. Walking through the four questions:
Question 1: Order status and standard returns resolve instantly. Passed, that's a real answer.
Question 2: Damaged-item claims and carrier delays get escalated, "to whoever's free." Failed. Nobody specifically owns them, so they get picked up inconsistently, and the same carrier-delay ticket type takes anywhere from two hours to two days to get a real answer depending on who's on shift.
Question 3: No written trigger list exists. Agents use judgment. Failed, because "judgment" produces different outcomes from different agents on the same ticket type, which is exactly the inconsistency this question is checking for.
Question 4: The team tracks CSAT weekly. Passed, technically, though it's a thin answer since CSAT alone can't catch the reopen-rate problem described above.
Score: 2 out of 4. The fix isn't a new tool, it's writing down an owner for carrier/damage escalations and a short trigger list for when something automatically moves to a person. Only after that's written down does it make sense to ask whether an AI agent should own more of the "resolves instantly" tier, because right now the team doesn't have a clean definition of what "instantly" should even cover beyond the two ticket types they already named.
Skip the pillars-and-C's debate
Search for "customer experience strategy" and you'll find competing frameworks, KPMG's six pillars, the "three C's," a "five components" list, presented as if they're settled industry standards. Some are better sourced than others (see the FAQ below for the honest breakdown of each), but none of them will tell you which ticket types your team should automate. That only comes from answering the four questions above against your own ticket data.
If you want to map a framework onto the diagnostic rather than ignore it entirely, KPMG's six pillars translate reasonably well: "Resolution" and "Time and Effort" map onto questions 1 and 3 (does the issue actually get solved, and does the process for solving it stay fast and simple). "Expectations" maps onto question 2 (a customer's expectation of a timely answer is exactly what breaks when ownership is vague). "Personalization" and "Empathy" don't map onto any of the four questions cleanly, which is a fair critique of the diagnostic, it's built for operational consistency, not for the softer, harder-to-measure sides of a customer relationship. Both matter. They're just not what breaks first for a growing ecommerce team, which is why they're not where this diagnostic starts.
Pick a framework later if you want a shared vocabulary; don't let picking one become a substitute for the diagnostic.
Where AI resolution fits, and where it doesn't
AI resolution is a lever for question 1, specifically the "resolve immediately" tier. It's not a replacement for answering the four questions, and bolting an AI agent onto an undefined process just automates the confusion faster.
In ecommerce specifically, the tickets that tend to belong in that tier are the ones with a clear, data-backed answer: order status and tracking, return eligibility against a written policy, subscription pauses or skips, simple product questions your documentation already covers. The tickets that tend not to belong there are the ones question 3 already flagged as escalation triggers: chargebacks, damaged or lost claims that need a judgment call, high-value subscription cancellations, anything with negative sentiment repeated twice. An AI agent that reads order, return, and subscription data together can absorb a real share of the first group for an ecommerce team, but only once that group is actually defined, which is the entire point of question 1.
If you scored 0 or 1 above, fix that first. If you scored 2 to 4 and the gap is specifically "we don't have enough resolution capacity for the tickets we've already defined as automatable," that's the problem AI resolution is built to solve. See our breakdown of the metrics that actually move the needle (/blog/customer-service-metrics) for how to track whether it's working once it's in place.
Where Weav fits
We built Weav for question 1: an AI Agent that reads your order, return, and subscription data together, so it can actually own the "resolve immediately" tier instead of just answering FAQs and escalating everything else. If your four answers are solid and you're looking for a way to execute the automated tier, start for free today.
FAQ
What is a customer experience strategy? A customer experience strategy is an operating plan for how customer issues get resolved, covering resolution paths by ticket type, who owns exceptions, escalation rules, and a way to measure whether it's working. It's a decision framework, not a values statement.
What are the six pillars of customer experience? Per KPMG's research: Integrity, Empathy, Expectations, Personalization, Time and Effort, and Resolution. It's the most rigorously sourced CX framework available, built from research across roughly 3,000 brands.
What are the three C's of customer experience? There's no single agreed answer, different sources define this differently. The most commonly cited version is Consistency, Customization, and Convenience.
What are the five components of customer experience? There's no standard list here either. Commonly cited components include personalization, consistency, empathy, accessibility, and engagement, but different sources give different fives. Treat it as a menu of things worth measuring, not a checklist to complete in order.
What are the five C's of experiential marketing? Connection, Content, Context, Community, and Commerce. This comes from event/experiential marketing, a different discipline from support CX strategy, and isn't directly applicable to how a support team should operate.
How is a CX strategy different for ecommerce teams specifically? Ecommerce support deals with a narrower, more repeatable set of ticket types (orders, returns, subscriptions, shipping) than a generalist enterprise CX function, which makes automation and clear resolution paths more directly applicable than in a generic enterprise CX framework.
Does AI resolution replace the need for a CX strategy? No. AI resolution is a tool for handling a defined tier of tickets within a strategy. Without a defined strategy first, adding AI just automates an undefined process faster.
Related Posts
Casey Rowland
