Reduce the number of contacts with customers and third parties
Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) All sources
category: Customer Experience class: Rules for External Parties frameworkAspect: Customers perspective: functional
Each contact with a customer, supplier or other third party, whether a letter, call, e-mail or portal request, interrupts the case, creates waiting time you do not control and adds an opportunity for misunderstanding. The pattern aims to reduce the number of such contacts, either by avoiding them or by combining several exchanges into one.
The exchange of information with a client or third party is always time-consuming. Especially when information exchanges take place by regular mail, substantial wait times may be involved. Each contact also introduces the possibility of intruding an error. Hammer and Champy (1993) describes a case where the multitude of bills, invoices, and receipts creates a heavy reconciliation burden.
Note that this heuristic is related to the Interfacing heuristic in the sense that they both try to improve on the collaboration with other parties.
Typical sources of unnecessary contacts are incomplete first requests that trigger follow-up questions, separate notifications for every process step and repeated reminders. Asking for all required information once and in a structured way, confirming several items in one message, and giving customers self-service access to status information all reduce touchpoints. First-contact problem resolution and Offer Customer self-service are customer-centric extensions of the same idea.
The heuristic is mentioned Hammer by and Champy (1993) and Reijers and Goverde (1999a). Buzacott (1996) has investigated this heuristic quantitatively.
Contact reduction concerns decreasing the number of communications with customers and integration refers to combining an existing process with a business process of customers. These best practices are related to a change ofworkflows; thus, they lead to a change of a process model. More in detail, contact reduction removes repetitive loops from the process, while integration removes customer-related activities or sub-processes from an as-is process model. Therefore, identifying the application of the contact reduction and the integration best practices can be checked by comparing discovered process models (BPI1) before and after BPR. [@Cho.2017]
■ This pattern ■ Baseline
Reducing the number of contacts may therefore decrease throughput time and boost quality. Note that it is not always necessary to skip certain information exchanges, but that it is possible to combine them with limited extra cost. A disadvantage of a smaller number of contacts might be the loss of essential information, which is a quality issue. Combining contacts may result in the delivery or receipt of too much data, which involves cost.
The ratings weigh these effects as follows. Time improves, because waiting for replies from external parties drops out of the critical path. Quality is rated as worsening, reflecting the risk named above: with fewer contacts, essential information can be missed and customers may feel less informed. Cost is rated as slightly worsening, since combined exchanges can mean collecting and transferring more data than needed and investing in better first requests. Flexibility is neutral.
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes with many external contacts per case (outgoing requests, incoming replies, reminders). Location: activities involving customers or third parties, especially repetitive loops such as Request information → Receive information → Request information. Attributes: contacts per case, waiting time per contact, channel, share of cases with more than one request of the same type, contact reasons. Constraints: legally required notifications; contacts customers value, such as status updates during long cases; bundling so much that essential information is lost.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Consider automating activities
Automate for environmental impact
Implement automation in a sustainable way
Buffer external information and subscribe to updates
Combine small activities into composite activities
Collect similar work items and work in batches
Constraint-based task assignment
Allocate tasks considering business process execution constraints
Establish standardized interfaces
Consider a standardized interface with customers and partners
First-contact problem resolution
Establish a one-contact resolution for customer issues
Minimize numerical involvement
Too many cooks spoil the broth