A customer does not experience a contact center as a collection of departments, queues, scripts and software platforms. They experience one journey: “I need help, and I want a clear answer without repeating myself.”
That makes First-Contact Resolution (FCR) a powerful Critical-to-Quality measure. FCR generally means the percentage of eligible customer issues resolved during the initial interaction, without a repeat contact for the same reason. The basic formula is:
FCR = Issues resolved on first contact ÷ Total eligible contacts × 100
Value Stream Mapping (VSM) makes the entire journey visible. Instead of improving Average Handle Time in isolation, a Lean Six Sigma team can see where time, information and customer effort accumulate: from call arrival and IVR navigation to authentication, diagnosis, resolution and after-call work.
This guide presents a worked contact-center example, including current-state data, the eight wastes, a future-state design and a practical kaizen sequence.
1. Select the right value-stream scope
The fundamental purpose of scoping is to prevent the team from mapping an entire customer-service ecosystem when the project concerns one measurable outcome.
For this example, the scope is:
- Unit of work: One inbound customer call
- Start point: Call arrives in the ACD or IVR
- End point: The customer’s issue is resolved and the interaction is closed
- Primary CTQ: First-Contact Resolution
- Supporting measures: Queue time, transfer rate, hold time, repeat-contact rate, abandonment and customer satisfaction
- Participants: Contact-center operations, workforce management, IT, quality, knowledge management and frontline agents
The team should also define FCR operationally before collecting data. For example, a contact counts as resolved on first contact only when:
- The issue is resolved during the initial interaction.
- No transfer to another queue is required.
- No repeat contact for the same issue occurs within seven days.
- The case is not reopened because the original resolution was incomplete.
This definition prevents teams from inflating results by counting a call as resolved simply because the agent selected a “closed” status.
For practical scoping support, a project scope boundary calculator can help clarify inclusions, exclusions and ownership.
2. Build the current-state map
A current-state VSM must represent the process as it operates: not as the procedure manual suggests it operates. Walk the flow, observe real calls, interview agents and extract data from the ACD, CRM and ticketing platforms.
A typical current-state sequence is:
- Customer call arrival
- IVR menu selection
- Queue waiting
- Agent connection and authentication
- Problem diagnosis
- System search or hold
- Resolution, transfer or escalation
- After-call work
- Repeat contact if the issue remains unresolved
Worked example: four-week baseline
Assume a contact center receives 10,000 inbound calls over four weeks. Of these, 9,200 are answered, while the remainder abandon before reaching an agent.
The baseline shows:
- FCR: 63%
- Transfer rate: 22%
- Repeat-contact rate within seven days: 21%
- Average queue wait: 6.8 minutes
- Average hold or system-search time: 3.2 minutes
- Average after-call work: 2.7 minutes
- Abandonment rate: 8.0%
The value-stream team records the following average contact path:
| Process step | Touch time | Waiting or delay | Key observation |
|---|---|---|---|
| IVR navigation | 2.0 min | 0.5 min | Six menu choices create misrouting |
| Queue to agent | : | 6.8 min | Demand exceeds capacity during peaks |
| Authentication and diagnosis | 4.5 min | 1.2 min | Customers repeat information already in CRM |
| System search or hold | 2.4 min | 3.2 min | Knowledge is spread across four applications |
| Resolution or transfer | 5.8 min | 4.5 min | Transfer creates a second queue |
| After-call work | 2.7 min | 1.9 min | Agents enter the same information twice |
| Total | 17.4 min | 18.1 min | 35.5-minute average lead time |
The map reveals that the problem is not simply “agents need to work faster.” The total touch time is 17.4 minutes, but the customer experiences 35.5 minutes because waiting, holds and handoffs add 18.1 minutes.
Using the process-cycle-efficiency formula:
PCE = Value-added time ÷ Total lead time × 100
If the team classifies 17.4 minutes as direct issue-resolution work, current PCE is approximately 49.0%. The classification should be agreed with the customer: authentication, duplicate data entry and internal searching may be necessary, but they do not necessarily create value from the customer’s perspective. The Process Cycle Efficiency Calculator can support this analysis.
3. Identify the eight wastes in the call journey
Lean’s eight DOWNTIME wastes provide a disciplined lens for analysing the current state.
- Defects: Incorrect routing, incomplete answers, inaccurate case notes and unresolved contacts that generate repeat calls.
- Overproduction: Unnecessary outbound follow-ups, duplicate reports and case records created before the customer’s need is understood.
- Waiting: IVR navigation, queue time, internal holds, supervisor approval and back-office response time.
- Non-utilised talent: Skilled agents spending large portions of the shift searching systems or performing repetitive administration.
- Transportation: Movement of information between frontline agents, specialist queues, email teams and back-office departments.
- Inventory: Open tickets, callback requests and unresolved cases accumulating in a work queue.
- Motion: Agents switching between CRM, billing, policy, knowledge and authentication screens.
- Extra-processing: Repeated authentication, duplicate questions, manual copy-and-paste and multiple quality checks for the same interaction.
The most significant bottleneck in this example is the combination of knowledge search and transfer routing. A 22% transfer rate means approximately 2,024 of the 9,200 answered calls require another queue or another agent. If only half of those transferred calls eventually resolve without a repeat contact, the transfer process is a major contributor to the 21% repeat-contact rate.
4. Design the future-state value stream
A future-state map should not be a wish list. It should describe a practical flow supported by owners, technology, standard work and control measures.
The proposed future state includes:
- Simplified IVR: Reduce six menu choices to three clear intent-based paths.
- Intent-based routing: Use customer selection and account information to route calls to the best available skill group.
- Unified agent workspace: Display customer history, authentication status and relevant knowledge articles in one view.
- Standard work for common call types: Provide decision trees for the top 10 reasons for contact.
- Clear escalation rules: Reserve specialist escalation for defined complexity thresholds rather than uncertainty.
- Pull-based back-office queue: Use visible WIP limits and service-level triggers for cases that genuinely require follow-up.
- Automatic case notes: Populate standard fields from the interaction record to reduce duplicate entry.
- Daily visual management: Display FCR, transfer rate, queue time and repeat-contact rate by team and call type.
Agile practices can complement this work. Rather than waiting for a large technology release, the team can pilot one call type, review results after one week, adjust the knowledge content and then expand the solution. This iterative approach supports disciplined experimentation while the VSM protects end-to-end flow.
5. Current state versus future state
The following targets are illustrative and should be validated through a controlled pilot.
| Metric | Current state | Future-state target | Improvement |
|---|---|---|---|
| First-Contact Resolution | 63% | 82% | +19 percentage points |
| Transfer rate | 22% | 10% | 12-point reduction |
| Repeat contact within 7 days | 21% | 12% | 9-point reduction |
| Average queue wait | 6.8 min | 3.5 min | 48.5% reduction |
| Hold or system-search time | 3.2 min | 1.1 min | 65.6% reduction |
| After-call work | 2.7 min | 1.8 min | 33.3% reduction |
| Abandonment rate | 8.0% | 4.0% | 50% reduction |
| Average lead time | 35.5 min | 22.0 min | 38.0% reduction |
| Process Cycle Efficiency | 49.0% | 68.0% | +19 percentage points |
An increase from 63% to 82% FCR would prevent approximately 828 repeat contacts per month if the center handles 9,200 answered contacts monthly and the improved FCR applies consistently. At an illustrative avoidable-contact cost of $7.80, that represents approximately $6,458 per month, or $77,500 annually, before considering customer-experience benefits.
6. Sequence the kaizen work
Improvement should be sequenced according to flow impact, feasibility and learning value.
Kaizen 1: Stabilise the current process
- Confirm the FCR operational definition.
- Validate transfer, repeat-contact and abandonment data.
- Create standard work for the top three call types.
- Remove obsolete knowledge articles.
- Establish a daily visual board.
Kaizen 2: Reduce avoidable waiting
- Analyse arrival patterns by half-hour interval.
- Align schedules with demand using takt-time thinking.
- Simplify IVR choices.
- Introduce a real-time Andon-style alert when queue wait or transfer volume exceeds the agreed threshold.
Kaizen 3: Improve first-contact capability
- Build a searchable knowledge structure.
- Use agent feedback to improve decision trees.
- Cross-train selected agents for the highest-volume transfer reasons.
- Pilot a unified customer-information screen.
Kaizen 4: Control the future state
- Monitor FCR with a run chart or appropriate control chart.
- Review transfer rate and repeat contacts weekly.
- Audit a sample of closed contacts for true resolution.
- Assign process ownership across operations, IT and knowledge management.
- Revisit the VSM after 30, 60 and 90 days.
Formal approvals are useful governance checkpoints, particularly for IVR changes, system releases and policy updates. However, excessive approval layers can become another bottleneck. Define decision rights clearly so low-risk improvements move quickly while material customer, compliance or technology risks receive appropriate review.
Build capability to lead the next improvement
Value Stream Mapping is not merely a diagramming exercise. It is a way to connect customer value, process flow, variation, waste, capacity and measurable business results.
When you can distinguish touch time from waiting, identify the bottleneck, define FCR precisely and sequence improvements through DMAIC, you move from opinion-led change to evidence-based operational improvement.
Lean 6 Sigma Hub offers CSSC-accredited Green Belt training with self-paced lessons, practical tools, case studies, worked examples and statistical methods for leading real improvement projects. If you are beginning your journey, explore the full Lean Six Sigma training pathway from White Belt through Master Black Belt.
Pursue Lean Six Sigma certification and learn to transform waiting, handoffs and repeat contacts into measurable customer value.
Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)
