First-contact problem resolution

Establish a one-contact resolution for customer issues

Frank, L., Poll, R., Röglinger, M., & Lea, R. (2020). Design heuristics for customer-centric business processes. Business Process Management Journal, 26(6) All sources

Description

Companies should ensure that all information needed to solve customer issues are collected at the first encounter in the business process. This reduces the interaction effort on both sides and supports the fast and comprehensive identification of solutions.

Every additional contact for the same issue costs the customer effort and the company handling time, and each handover is a chance to lose information. The heuristic aims at the concerted interaction capability, i.e. coordinating processes so that interactions with customers run smoothly. In practice, three things have to come together at the first contact: the right information (customer data and case history, see Informed point of contact), the right person or system (skills-based routing), and the authority to decide (see Empower resources). When one of them is missing, the case loops back to the customer. It also connects to Reduce touchpoints, because each resolved first contact prevents several follow-ups.

Real-World Example

At Allianz, call center agents are instructed to serve customers in minimum time by prohibiting repeated calls, by permitting only one forwarding per call and by assigning the most appropriate agent available. This way, customers do not need to describe their problem or needs several times and get support as soon as possible.

Implementation

This heuristic can be realized by reducing the number of loops in business processes and by proactively assigning the most suitable employee or IT-based touchpoint (e.g. chatbots).

Selected source. The main idea and elements of this heuristic are derived from Dixon et al. (2010) and the process redesign best practice “Empower” presented by Reijers and Liman Mansar (2005).

Key Takeaways

  1. Collect everything at the first encounter — Ask for and retrieve all information needed to solve the issue during the first contact.
  2. Route to the right resource — Assign the most suitable employee or IT-based touchpoint from the start.
  3. Give the authority to decide — First-line staff need the mandate to resolve the issue, not only to record it.
  4. Remove loops — Each loop back to the customer is a failed first contact and a redesign target.

Performance considerations

Impact. Concerted interaction capability.

The heuristic serves customer-centricity through the concerted capability: coordinating and integrating processes so that interactions with customers run smoothly.

  • Time: Total resolution time drops because callbacks, forwardings and repeated explanations disappear. Individual first contacts can take somewhat longer.
  • Cost: Fewer contacts per issue lower handling cost. Better routing, training and decision authority for first-line staff cost money.
  • Quality: Customers don’t have to repeat themselves and information is not lost in handovers. Pressure for speed must not lead to premature closure.
  • Flexibility: Requires broader skills or good routing, which can make staffing less flexible.

Example

For example, a manufacturer’s customer care could analyse its service request types (product returns, defects, invoicing issues) and find that defect cases are often reopened because the serial number or a photo was missing at the first contact. Making those fields mandatory in every channel, routing defect cases straight to technically trained agents, and allowing those agents to approve a replacement up to a set value would let most defect cases close in the first contact.

Spotting the opportunity in event data

Framed along the FLAC rule types — fitness, location, attribute, constraint.

  • Fitness: Service and complaint processes. Measure first-contact resolution rate (share of cases closed after one inbound contact) as the fitness value.
  • Location: Loops back to “request information from customer”, repeated inbound contacts within one case, and forwarding or reassignment activities.
  • Attributes: Contacts per case, number of reassignments, reopen rate, time between contacts, issue category and the skill of the first handler.
  • Constraints: Some issues genuinely need investigation or a site visit. Don’t close cases early just to improve the metric.

Sources & references

  1. Frank, L., Poll, R., Röglinger, M., & Lea, R. (2020). Design heuristics for customer-centric business processes. Business Process Management Journal, 26(6) Summary on this site Publisher page DOI 10.1108/bpmj-06-2019-0257

Share this pattern

Enjoy these

Foundational free Patterns

Apply Integral technology

Elevate physical constraints by applying new technology

Apply triage

Consider the division of a general activity into two or more alternative activities

Appoint case managers

Assign a responsible individual for handling each case type

Assign cases

Let workers perform as many steps as possible for single cases

Automate activities

Consider automating activities

Automate for environmental impact

Implement automation in a sustainable way

Buffer information

Buffer external information and subscribe to updates

Combine activities

Combine small activities into composite activities

Consolidate Work

Collect similar work items and work in batches

Constraint-based task assignment

Allocate tasks considering business process execution constraints

← Back

Connected to

Empower resources

Empower workers for more decision-making authority

Reduce touchpoints

Reduce the number of contacts with customers and third parties

What's Happening?

Dec 2023
New Pattern

Consolidate Work

Nov 2023
Oct 2023
Oct 2023
New Cheat sheet

Redesign Essentials

Sep 2023
Sep 2023
Aug 2023
New Pattern

Task delegation

Aug 2023
Aug 2023
New Pattern

Green Feature

Aug 2023