Applying Salesforce CX Research to Your Own Business

Most organisations that read research about customer centricity nod along and change nothing. The findings confirm what they already suspect, land in a shared inbox, and dissolve into the next quarterly planning cycle. That is not a knowledge problem. It is an application problem — and it is worth solving deliberately.

Salesforce's 7th edition of the State of the AI Connected Customer report is one of the more substantive pieces of CX research published in recent years. It is also, like most research of its kind, written for a general audience. The work of applying it to a specific organisation — its culture, its maturity, its actual customer base — falls entirely to the reader. This article does that work.

The short answer: Customer centricity is not a mindset declaration or a values statement. It is an operating model — a set of decisions about measurement, governance, workflow, and incentives that either puts the customer's experience at the centre of the business or quietly relegates it to a support function. Salesforce's research surfaces the gap between intention and reality. Closing that gap requires a structured approach to defining, measuring, and improving customer centricity at the level of individual touchpoints, not just aggregate scores.

What the Salesforce Research Actually Says — and What It Doesn't

The State of the AI Connected Customer (7th edition, Salesforce Research) is a large-scale global survey examining how customer expectations are shifting in an era of AI-assisted service and commerce. Its central finding, consistent across editions, is that the gap between what customers expect and what organisations deliver remains wide — and that AI is accelerating customer expectations faster than most businesses can adapt their operations.

What the report does well: it quantifies the scale of the expectation gap, identifies the channels and moments where trust erodes most quickly, and flags the growing importance of personalisation, proactivity, and consistency across channels. These are real, actionable signals.

What it cannot do: tell you where your organisation sits within that distribution, which of your specific touchpoints are failing, or what the commercial cost of your current CX gaps actually is. That translation — from sector-level finding to firm-level action — is the practitioner's job. The research is the diagnosis of an industry; the treatment plan is yours to write.

For a deeper look at how Salesforce's findings compare with what organisations actually experience in practice, see Salesforce Customer Centricity Findings vs Real-World Practice.

Why Defining Customer Centricity Precisely Is the First Step

Ask ten senior leaders to define customer centricity and you will receive ten different answers — most of them correct in spirit and useless in practice. "Putting the customer first" is not a definition; it is an aspiration. A working definition must be specific enough to fail.

A practitioner-grade definition: customer centricity is the consistent prioritisation of customer outcomes in decisions about product, process, policy, and people — measured by the quality of experience at each touchpoint, not by internal satisfaction with the output.

That last clause is the one that matters. The Salesforce research, across multiple editions, has documented the persistent gap between how organisations rate their own performance and how customers rate the same interactions. An organisation that measures customer centricity only through internal metrics — project completion rates, SLA adherence, call-handling time — is measuring its own efficiency, not its customers' experience. These are related but not the same thing, and conflating them is the root cause of most CX programmes that plateau.

Defining customer centricity with this precision does two things. It makes the concept auditable — you can point to a decision and ask whether it prioritised customer outcomes or internal convenience. And it creates a shared language across functions that otherwise argue past each other about whose responsibility the customer is.

The Business Case for Customer Centricity: Arguing From Mechanism, Not Just Metrics

The business case for customer centricity is sometimes made through aggregate statistics about revenue uplift or churn reduction. Those figures are useful when they come from verified, named sources. When they are invented or generalised beyond their original context, they erode credibility rather than build it.

The more durable argument runs through mechanism. Customers who consistently experience low friction, accurate expectations, and genuine resolution of problems have fewer reasons to defect. They are also more likely to recommend — not because they were asked to, but because the experience was worth talking about. Reciprocity, one of the most robust findings in behavioural economics, operates here: when an organisation demonstrably acts in a customer's interest rather than its own, customers respond in kind. This is not sentiment; it is a predictable pattern rooted in how humans process fairness.

The inverse is equally predictable. Loss aversion — the well-documented tendency, described by Daniel Kahneman and Amos Tversky in their foundational work on prospect theory, for people to weight losses more heavily than equivalent gains — means that a single bad experience carries disproportionate weight in a customer's overall assessment. A loyalty programme, a discount, or a personalised communication cannot easily offset a broken promise or an unresolved complaint. The Salesforce research reflects this asymmetry: customers who lose trust in a brand are significantly harder to win back than they were to acquire in the first place.

If you want to quantify the commercial case for your own organisation, the CX ROI Calculator offers a structured way to model the revenue impact of reducing churn and improving retention — using your own inputs rather than industry averages.

How to Measure Customer Centricity Without Drowning in Data

The measurement problem in CX is not a shortage of data. Most organisations have more customer data than they can act on. The problem is that the data is rarely structured around the customer's experience of a journey — it is structured around the organisation's internal processes. Call volumes, resolution times, and digital engagement rates tell you how the operation is performing. They do not tell you whether the customer felt heard, whether their expectation was set accurately, or whether the effort they had to expend was proportionate to the value they received.

A measurement framework for customer centricity needs to operate at three levels simultaneously:

• Relationship level: Net Promoter Score (NPS) or equivalent — a periodic read on overall sentiment and advocacy intent. Useful for tracking direction; not useful for diagnosing cause.
• Transaction level: Customer Satisfaction Score (CSAT) at key touchpoints — captures the immediate emotional response to a specific interaction. Granular enough to be actionable if tied to a specific moment in the journey.
• Effort level: Customer Effort Score (CES) — measures the friction a customer experienced in completing a task. Particularly valuable for identifying process failures that feel invisible from the inside.

None of these metrics is sufficient alone. NPS without CES tells you customers are unhappy but not why. CES without CSAT tells you a process was easy but not whether it resolved the actual problem. The three work as a system, each illuminating a different dimension of the same experience.

The Salesforce research points to personalisation and proactivity as two of the highest-leverage drivers of positive customer sentiment. Both are measurable at the touchpoint level: did the interaction reflect knowledge of this customer's history? Did the organisation anticipate the need before the customer had to articulate it? These are not soft questions — they can be scored, tracked, and improved.

For organisations that want a structured view of where their measurement capability sits relative to best practice, a CX Maturity Assessment provides a diagnostic across the twelve building blocks of a mature CX programme, including measurement architecture.

The Most Common Customer Centricity Mistakes — and Why They Persist

The mistakes are not mysterious. They recur because they are structurally incentivised, not because the people making them are careless.

Measuring satisfaction instead of experience. A customer who rates an interaction 4 out of 5 may have received competent service while still feeling that the organisation's policy was designed for the organisation's convenience, not theirs. Satisfaction scores capture the interaction; they rarely capture the underlying experience of fairness, effort, or respect. Organisations that optimise for satisfaction scores without examining the policies and processes that shape the experience are polishing the surface of a problem they have not solved.

Treating customer centricity as a communications exercise. Slogans, values posters, and customer-first pledges are not CX strategy. They are, at best, a signal of intent. At worst, they create a gap between what the organisation says and what the customer experiences — a gap that erodes trust faster than silence would. The Salesforce research consistently shows that customers are highly attuned to the distance between brand promise and operational reality. Closing that distance is an operational challenge, not a marketing one.

Siloing the customer experience function. When CX sits in a single department — typically marketing or customer service — it has no authority over the product decisions, policy choices, or process designs that most directly shape the customer's experience. The customer experience function needs cross-functional reach and executive sponsorship to move from advisory to operational. Without it, journey maps become documents rather than instruments of change.

Confusing the journey map with the journey. A journey map is a hypothesis about what a customer experiences. It becomes useful only when it is tested against real customer behaviour, updated with real feedback, and connected to the decisions of the people who can change what happens at each touchpoint. Static journey maps — produced once, presented to leadership, filed — are a common artefact of CX programmes that have substituted activity for impact.

Ignoring the employee experience upstream. The Salesforce research, like most serious CX research, points to the connection between how employees experience their work and how customers experience the organisation. An employee navigating a broken internal process, unclear authority, or misaligned incentives cannot consistently deliver a customer-centric experience regardless of their personal commitment. Employee experience is not a separate programme — it is the upstream condition that determines the quality of the customer experience downstream.

A Practical Framework for Implementing Customer Centricity

Translating research findings into operational change requires a structured approach. The following sequence is not a methodology in the abstract — it is the order in which decisions actually need to be made for customer centricity to take hold rather than stall.

1. Establish a precise, agreed definition. Before any measurement or improvement work begins, the leadership team needs a definition of customer centricity that is specific enough to audit decisions against. Use the framing above or develop one that reflects your organisation's context — but it must include a clear statement of what "prioritising customer outcomes" means when it conflicts with internal convenience or short-term cost.
2. Map the actual journey, not the intended one. Commission a journey mapping exercise that begins with customer research — interviews, observation, complaint analysis, mystery shopping — rather than internal assumptions. The gap between the journey the organisation believes it delivers and the journey the customer actually experiences is where the most valuable improvement opportunities live. A structured CX journey design process provides the methodology for doing this rigorously.
3. Score every touchpoint for experience impact. Not all touchpoints carry equal weight. Some are moments of truth — points in the journey where the customer's trust is either confirmed or broken. Identifying these requires both quantitative data (where do complaints cluster? where does churn spike?) and qualitative insight (what do customers say about the moments that mattered most?). Prioritise improvement effort on the touchpoints with the highest impact on trust and loyalty, not the ones that are easiest to fix.
4. Connect measurement to accountability. CX metrics that are reported to leadership but not owned by the people who can change the underlying experience are decorative. Each key touchpoint metric needs an owner — a specific role with the authority and the incentive to improve it. This is a governance question as much as a measurement question, and it is where most CX programmes lose momentum.
5. Build a roadmap of improvements with commercial logic. Each improvement initiative should be connected to a specific customer outcome (reduced effort, faster resolution, more accurate expectation-setting) and a commercial hypothesis (reduced churn, increased repeat purchase, lower cost to serve). This is what makes CX investment defensible at board level and what distinguishes a CX implementation roadmap from a wish list.
6. Close the feedback loop visibly. One of the most powerful signals of genuine customer centricity is demonstrating to customers that their feedback changed something. This is not just good communications — it activates reciprocity and builds the kind of trust that sustains loyalty through the inevitable moments when something goes wrong. The Salesforce research highlights this as a significant differentiator between organisations customers trust and those they merely tolerate.

What Genuine Customer Centricity Looks Like in Practice

Examples of customer centricity that hold up to scrutiny tend to share a structural characteristic: the organisation has made it operationally difficult to deprioritise the customer. This is not achieved through culture alone — culture is downstream of structure. It is achieved through governance models that give CX metrics equal standing with financial metrics in operational reviews, through policy design that starts with the customer's situation rather than the organisation's liability, and through escalation processes that treat a customer complaint as a signal about a systemic failure rather than an individual incident to be closed.

The organisations that do this well are not necessarily the ones with the largest CX teams or the most sophisticated technology. They are the ones where the question "what does this mean for the customer?" is asked — and answered honestly — before operational decisions are made. That is a discipline, and like all disciplines, it requires practice, measurement, and the occasional willingness to absorb a short-term cost in the service of a long-term relationship.

The Salesforce research is useful precisely because it documents, at scale, what customers say they want and where they say organisations are falling short. The gap it describes is real. But the organisations that will close it are not the ones that read the research most carefully — they are the ones that build the internal structures to act on it consistently, quarter after quarter, at the level of individual touchpoints rather than aggregate scores.

Customer centricity is not a destination. It is the discipline of asking the right question — what does this mean for the customer? — and having the organisational architecture to act on the answer. The research tells you what the question is. The rest is design.

If you are ready to move from research to action, Renascence's customer experience practice works with organisations across MENA to translate CX strategy into measurable operational change — from journey design and measurement architecture through to governance and cultural embedding.