Measuring whether a support technology change reduced customer effort

Measure effort in the customer journey the change was meant to improve. Ask affected customers about ease, then check what they had to do: repeat information, make another contact, change channels or wait for an answer. Faster agent work alone does not establish that the customer's task became easier.

Define the journey and outcome

Name the change, the affected customers and the task they were trying to complete. A new handover view, for example, might aim to stop customers repeating their question after a transfer. The outcome concerns the customer's experience of that transfer, not the number of fields added to an agent screen.

Set the journey's start and end. Decide whether a later contact about the same unresolved issue remains part of it, and how a genuinely new request is counted. Keep journeys still open at the end of the observation window visible; completed cases alone can give a misleading picture.

Ask about ease consistently

A customer effort question can ask how easy it was to get help.

Choose the wording, scale, channel and survey point before comparing periods, and state which end of the scale means easier. If a journey is still open when surveyed, distinguish ease so far from ease of resolving the task.

Report the answer with its coverage:

Define the reported calculation in advance, whether an average rating or the share choosing an agreed “easy” response. Neither result describes non-respondents. Read customer comments and relevant case histories to understand the rating.

Check the path alongside the survey

Choose observations that match the intended benefit. For a handover change, inspect whether customers restated the issue and whether the next agent had the earlier context. For self-service, check whether the customer completed the task or still contacted support.

For an intake change, inspect requests for information already supplied. State the unit and period for each measure.

Keep agent handling time and ticket counts in supporting roles. They can help explain the path but do not directly measure how hard the task felt to a customer. Check whether the change shifted work to another channel or left more journeys unresolved.

Compare and decide

Compare similar issue types, channels, service hours and observation windows. Record other changes during the period, such as staffing, policy or a product incident. Where practical, compare a similar unaffected journey over the same dates. A simple before-and-after difference is an association, not proof that the technology change caused it.

Investigate disagreement between signals. Easier ratings alongside more repeat contact call for case review. Fewer agent touches alongside unchanged ratings may indicate internal efficiency without a measured customer benefit. Check survey coverage before interpreting a score movement.

Conclude with the included customers, what changed in reported ease and observed behaviour, what remains uncertain, and whether to keep, revise or reverse the change.