Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Customer Experience, Retention & Loyalty › CX Foundations

Reducing Customer Effort Across the Journey

How to find and remove the effort customers spend on a business: repeating themselves, switching channels, long forms, proving who they are and chasing updates.
Guideintermediate10 min readUpdated

Effort is a cost the business moves onto the customer

Most effort in a customer relationship is not an accident. It exists because something was easier for the business that way: one team's system does not talk to another's, so the customer carries the information between them; a policy needs proof, so the customer finds it; nobody sends updates, so the customer chases. Each choice saves the business a little work and spends the customer's time, patience and goodwill instead.

Seen this way, effort is a cost, and like any cost it can be measured, ranked and cut. The customer retention strategy guide names service as one of the four levers that keep customers; effort is where service most often fails without anyone noticing, because customers who give up rarely complain. They simply do not come back, and the loss shows only later in the Churn Rate.

The voice of the customer guide covers the Customer Effort Score, the survey question that asks how easy it was to get what the customer needed, and when to ask it. This guide does not repeat it. A survey tells you that effort exists; the work here is finding where it comes from and removing it. The customer experience foundations hub places that work alongside the journey, onboarding and retention.

The kinds of effort and where they hide: a table

Effort takes a small number of recurring forms. Each leaves traces in a different place, which is what makes it findable.

Kind of effortWhat the customer doesWhere it usually hidesWhere to find it in your records
Repeating informationGives the same details more than once: to a bot and an agent, to sales and to deliverySystems that do not share history; handoffs between teamsContacts where agents ask for details already held; transcripts with repeated questions
Switching channelsStarts in one channel and is told to finish in anotherChannels that cannot complete certain tasks; policies that only one team can applyContacts that arrive in a second channel soon after a first; "please call us" replies
TransfersIs passed from one person or team to anotherRouting that sends contacts to the wrong team; agents without authorityTransfer counts per contact; contacts reassigned before closing
FormsFills in long, unclear or repeated formsBooking, returns, claims, sign-up and contact formsForm analytics, the Form Abandonment Rate, contacts asking how to complete a form
Proving identity or eligibilityAnswers security questions, finds receipts, sends documentsSecurity checks applied the same way to every request; warranty and refund rulesContacts held up waiting for proof; complaints about being asked again
Chasing updatesAsks where an order, repair, refund or reply has got toProcesses that tell the customer nothing between start and finishContacts asking "where is" or "any update"; repeat contacts on open cases
Finding answersSearches, reads and still has to askHelp content that is hard to scan or out of date; answers buried in termsHelp searches with no result; contacts that follow a help article view

The table is a starting set, not a complete list. A walk through the business's own journey, as the walking the customer journey tutorial sets out, usually adds kinds specific to the business, such as paperwork for a delivery slot or a phone call that is the only way to change a booking.

Finding effort in your own records

Effort is easiest to find where customers had to ask for help, because each contact is a moment when the experience did not carry them through on its own. Three sources do most of the work.

Support contacts by reason. A contact reason list, built as the tutorial on tagging support contacts by reason sets out, shows which questions customers ask most. Many reasons are effort in disguise: "where is my order" is chasing, "how do I change my booking" is a missing self-service route, "I was told to contact you" is a channel switch. Count them by reason and read a sample of each.

Repeat contacts. A customer who contacts the business again about the same problem has spent effort twice. Repeat contacts are the clearest evidence, because they show that the first contact did not end the customer's work. Look at which reasons produce repeats and at what happened in between: a promised call-back that never came, an answer that did not solve the problem, a transfer that lost the history. The support channels and self-service guide names handover without history as the most resented failure in support; repeat contacts are where it shows.

The journey and the systems behind it. Contacts show where effort became visible. The rest is in the journey itself. A journey map built with the customer journey mapping framework marks the touchpoints where customers struggle, and the retention version of the map gives service and billing lanes of their own. Where the cause of the effort sits inside the business, such as information typed into one system and never passed to another, drawing a service blueprint traces it to the handoff that produces it.

Read small counts with care. A reason that appears a handful of times in a month may be noise or may be the first sign of a new problem, so look at the contacts themselves before deciding. Surveys add the customer's own account: the open-text answers to an effort question often name the exact step that caused it. When a relationship score has been falling and the coded comments point at repeated details, handoffs or waiting, the diagnosis for a relationship survey score that is falling sends that cause here.

Fixes: remove, do it for them, tell them first, join it up

Almost every effort fix is one of four kinds. Asking which applies is quicker than designing from a blank page.

Remove the step. The cheapest effort to cut is a step that does not need to exist. A form field nobody uses, a security question asked for a request that changes nothing sensitive, a proof-of-purchase demand for an order the business can look up. For forms, Nielsen Norman Group's form usability recommendations, as the forms guide summarises them, start with keeping forms short and then reduce the other costs: single-column layout, logical order, visible labels and specific error messages that explain what went wrong. The same rules apply to a returns form or a booking form as to a lead form. Where a decision depends on many answers and the form cannot be short, the tutorial on redesigning a long application form arranges the effort instead, with a list of what to have ready, short steps and saved progress.

Do it for them. Where a step is necessary, the business can often do it instead of the customer. Pre-fill what it already knows. Look up the order rather than asking for the number. Book the follow-up visit rather than asking the customer to call back. Arrange the collection rather than sending instructions. Each of these moves work from the customer back to the business, which is usually cheaper than handling the contact that follows when the customer gets it wrong.

Tell them first. Chasing disappears when the business sends the update before the customer has to ask: the dispatch, the delay, the engineer's arrival window, the decision on a claim. These messages are service, not promotion, and the service and support hub sets out the standards and routing they sit within; they are the main fix for the chasing row of the table. The tutorial on proactive service messages covers telling affected customers about a delay, fault or disruption before they ask. Help content belongs here too: people scan for their answer rather than reading, as Nielsen Norman Group's research on how people read on the web shows and the writing for the web guide explains, so answers placed where the question arises, written to be scanned, save a contact.

Join it up. Repeating information, transfers and channel switches are mostly caused by history that does not travel. The fix is to make the customer's history follow them: one record seen by every team, notes carried across a handoff, a conversation that continues when it moves from chat to email. Where assistants or bots answer first, the AI in customer service guide covers handing over to a person with the conversation and details attached, so the customer does not start again.

Ranking the fixes and proving they worked

A business that starts looking for effort usually finds more than it can fix at once. Rank the candidates with the impact-effort matrix: impact from the business's own counts of contacts, repeats and complaints for each kind of effort, and effort from what the fix would take in systems, process and staff time. Fixes that affect many customers and need little work go first, which usually means telling customers before they ask and removing steps nobody needs. Fixes that need systems joined up often matter most and cost most; plan them rather than leaving them on the list.

Decide how you will know each fix worked before you make it. Pick the evidence that showed the effort in the first place and count it before and after: contacts for that reason, repeat contacts about it, form completions, the open-text answers that named it. Choose a comparable period, because many contact reasons rise and fall with the season, and allow for anything else that changed at the same time. Treat one or two of these counts as a KPI for the service team, owned and reported like any other.

Be careful about what the evidence can say. Fewer contacts about a step is good evidence that the step got easier. It does not, on its own, prove that customers stayed longer or spent more, and this guide makes no claim that lower effort predicts loyalty in general. If the business wants to know whether its effort survey or its contact counts move with retention, that is a question to test on its own customers with its own data.

An appliance repair service takes effort out of booking (illustrative)

Illustrative example — not a real result

Dravenko Appliance Repairs stops asking customers the same questions

Dravenko Appliance Repairs, an invented service that repairs washing machines, ovens and fridges, takes about 900 bookings a month by phone and through an online form. Reading 3 months of contacts by reason, the team finds that customers give the appliance's make and model up to three times: on the phone or form, again when an agent rings to confirm, and again to the engineer at the door. Separately, about 260 calls a month ask what time the engineer will arrive.

Using an impact-effort matrix, the team ranks 6 candidate fixes and chooses 2. First, the booking form and the phone script record make, model and fault once, stored against the booking, and the confirmation call is replaced by a message that shows those details and asks the customer to reply only if something is wrong. The engineer's job sheet shows the same details. Second, customers receive a message with a 2-hour arrival window the evening before, and another when the engineer sets off.

Over the next 3 months, calls asking about arrival times fall to about 70 a month, repeat calls about the same booking fall from about 140 to 85 a month, and engineers report fewer visits where they arrived without the right part. The team keeps a third fix, letting customers rebook online without calling, for the next quarter.

Common mistakes

  • Treating effort as a survey score. A better score is welcome, but the work is removing the steps that caused the effort. Start from contacts and repeats, not from the score.
  • Fixing the channel, not the cause. Moving a question from the phone to chat leaves the customer doing the same work. Ask why the question arises at all.
  • Adding self-service that adds steps. A help article or a bot that sends the customer round in circles is more effort, not less. Check that self-service actually completes the task.
  • Forgetting handoffs. Most repeating and transferring happens where information passes between teams or systems. Join the history up, or customers carry it.
  • Removing checks that protect customers. Some steps exist for good reasons. Make necessary steps lighter and explain them rather than cutting them.
  • No before-and-after count. Without counting the evidence that showed the effort, nobody can tell whether the fix worked.
  • Claiming more than the evidence shows. Fewer contacts about a step shows the step got easier. Whether it kept customers is a separate question for the business's own data.

Frequently asked questions

Is reducing customer effort the same as improving the Customer Effort Score?

No. The Customer Effort Score is a survey question that asks how easy it was to get something done, and it is one way to hear about effort. Reducing effort is the design work: finding the steps that make customers repeat themselves, chase, prove or switch channels, and removing them. A business can reduce effort without running the survey at all, using its support contacts and records, and a better score means little if the steps that caused the effort are still there.

Where should a business start reducing customer effort?

Start with the effort that shows up most often in its own records, usually repeat contacts about the same problem and contacts asking where something is. Those are visible in support data, they affect many customers, and the fixes are often cheap: telling customers before they have to ask, or storing information once so nobody asks for it twice. Rank the candidates by how many customers they affect and what the fix costs before choosing.

Can reducing effort go too far?

Some steps exist for good reasons, such as checking identity before changing an account or confirming a large order. The aim is to remove effort that serves only the business's convenience and to make the necessary steps as light as they can be, not to remove every check. When a step protects the customer, explain why it is there; customers accept effort they understand far more readily than effort that seems pointless.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Website Forms Usability: Top 10 Recommendations — Nielsen Norman Group
  2. How Users Read on the Web — Nielsen Norman Group

Related