Identifying steps customers must repeat

Repeated work is easy for an organisation to miss: each team sees only its own interaction. A customer may explain the same issue to a bot, a service agent and a specialist, then upload the same document again. Trace one task across channels to find the repeats.

Build a repeat inventory

Choose a recent case and list what the customer supplied at each step: identity details, order number, issue description, documents and preferred outcome. Mark whether the repeat was necessary for security, caused by missing access to prior information, or required because the first answer did not resolve the problem. Repeating information and switching channels are commonly observed high-effort behaviours; each repeat needs its own cause analysis.

Ask the customer to recount the sequence, then compare it with records where permitted. Logs may show two contacts but miss the time spent searching for an attachment or finding the right department. Include failed self-service attempts and forms abandoned before submission.

Causes of Customer Information Repeats

Remove the right repeat

Do not eliminate a required identity check just because it appears twice. Instead, see whether verification can carry safely into a later step, subject to the relevant privacy and security rules. For ordinary issue details, make a concise case summary available to the next authorised team. Let the customer correct that summary rather than dictate it again.

After a change, sample the same case types. Count repeats per completed task, repeat contacts and errors introduced by transferred information. If a field is still being requested twice, identify who owns the hand-off. A shorter form does not solve the problem if the next agent asks for everything it omitted.

Key Metrics After Process Improvements