Discovery field guide / Department
How to find AI opportunities in Customer Service & Contact Centers
Where should discovery start?
Follow an unresolved customer issue across contacts, channels, and back-office teams. The strongest discovery starting points are repeated explanations, transfers, and agent searches that prevent a correct resolution. Ask agents to show difficult cases and compare them with ordinary ones. Do not equate a short call or apparent containment with success: the customer may simply have abandoned the channel or returned elsewhere.
The shared framework
Fourteen stages, from objective to portfolio.
Every guide uses this sequence to connect a business problem to an accountable investment. Revisit earlier stages when new evidence changes the assessment.
Stage 1: Business Objective
Name the outcome the organization is trying to move, so every later idea has something to be measured against.
Stage 2: Department
Locate the team that owns the objective and the work that feeds it.
Stage 3: Process
Describe how the work actually runs today: steps, handoffs, systems, and exceptions.
Stage 4: People
Capture who performs and depends on the work, and what they know that no document records.
Stage 5: Problem
State the friction in plain terms: delay, rework, error, cost, or risk, with evidence.
Stage 6: Opportunity
Frame a specific improvement that addresses the problem, not yet tied to any technology.
Stage 7: AI/Automation Fit
Compare AI, RPA, IDP, workflow automation, process redesign, and no technology change.
Stage 8: Value
Estimate benefit in the objective's own terms, with assumptions written down.
Stage 9: Feasibility
Check data, systems, skills, and change capacity needed to deliver.
Stage 10: Risk
Surface compliance, quality, security, and adoption risks and the controls they need.
Stage 11: Scoring
Rate each opportunity on the same dimensions so comparisons are consistent and explainable.
Stage 12: Prioritization
Sequence opportunities by score, dependencies, and capacity, with reasons people can challenge.
Stage 13: Investment
Match approved effort to the sequence; people with budget authority decide what gets funded.
Stage 14: Portfolio
Track opportunities over time as a living set: delivered, in flight, waiting, and retired.
Start with one observable journey
Choose one contact reason and reconstruct the complete journey, including a repeat contact and a back-office handoff. Use consented, redacted transcripts and policy sources. Identify whether the customer needed an explanation, an authorized action, or a repair to the underlying service.
This is discovery across assisted and self-service support. Sales conversion and campaign targeting belong in Sales & Marketing; customer-service discovery centers on getting an issue resolved correctly.
Where to look in the work
The second and third contact
Inspect cases reopened after a superficially successful conversation. Check whether agents repeated identity checks, failed to see earlier commitments, or lacked authority to finish the task. A transcript summary cannot fix a refund system that no one on the queue is allowed to use.
Knowledge searches during a live interaction
Watch agents move between policy documents, product records, and supervisor messages. Note where language varies but the approved answer is stable. Where policies conflict, capture the conflict for the knowledge owner before proposing automated answers based on the same unreliable sources.
Who to interview and what each person knows
Agents from different queues
Include a frontline agent, an experienced escalation specialist, and a quality reviewer. Listen to an ordinary case and a difficult one together. Ask what the transcript fails to show, such as long system waits, a workaround, or a customer's inability to use a digital channel.
The people who can finish the work
Interview the back-office owner, knowledge editor, workforce planner, and a customer-experience lead. Establish who can authorize refunds or exceptions and who updates guidance. Do not let the contact-center manager commit another team's capacity without involving that team.
What to ask: follow the evidence
Why did this customer have to return?
Ask which commitment was not fulfilled and where the history became unavailable. What could the first agent have known or done differently? Which contact reasons are really product defects or unclear bills? Find the root cause before treating every conversation as a candidate for automation.
How does a customer reach a person?
Ask what triggers escalation, how vulnerability or accessibility needs are recognized, and which responses need approval. Can an agent verify the source behind a suggested answer? Capture how errors are corrected after the conversation, including any notification owed to the customer.
Signals of opportunity, and reasons to look elsewhere
Repeated search with a verifiable answer
A common policy question with current sources, clear eligibility, and an available escalation route can support agent assistance. The signal weakens when resolution needs discretionary negotiation or a disconnected system action. Separate answer quality from whether the promised action was actually completed.
Consistent missing context at transfers
Repeated manual reconstruction of customer history can indicate a bounded summary or structured handoff opportunity. Verify identity and account boundaries first. Long conversations involving distress or complex circumstances are not necessarily waste and should not be prioritized solely because they exceed an average handle time.
How to evaluate what you find
Judge resolution across the journey
Compare correct outcomes, repeat contacts, complaint handling, and total agent-plus-back-office effort. Test uncommon policy exceptions and relevant languages, not just frequent questions. Review whether a suggestion falsely promises an action or silently drops information needed by the receiving team.
Stress the handoff
Test what happens when knowledge is missing, identity cannot be verified, or the customer asks for a person. Include misleading customer text and sensitive information in controlled evaluation cases. Confirm recording, consent, retention, and access requirements with the responsible owners before using live conversations.
How to compare, prioritize, and invest
Begin with a bounded contact reason
An agent-reviewed knowledge or handoff trial is easier to inspect than immediate customer-facing automation across all queues. Repair broken policies or back-office bottlenecks first where those dominate repeat contact. Set a clear escalation route rather than optimizing for containment at any cost.
Protect service quality in the investment case
Compare candidates on correct resolution and avoided rework, with customer access and complaints as constraints. Do not assume released call time becomes cash savings. Name who will review failed interactions and stop the trial if customers become trapped or receive incorrect commitments.
Turn observations into a comparable opportunity record
Describe the current process before naming a solution. Record the trigger, owner, input, steps, handoffs, systems, output, and exception path. Separate what you observed from what someone recalled and what you still need to verify. A vivid interview story is a useful lead, not proof that every case behaves the same way. Validate it against a sample of ordinary work and difficult exceptions, with the limits of that sample made explicit.
Measure active work separately from waiting. Note the observation period, case mix, frequency, and source of each estimate. Include the receiving team's effort, checking, correction, and escalation so a local improvement does not merely transfer work. Describe the outcome in operational terms before attaching a monetary value. Capacity released is not automatically a budget saving; explain what can actually change and which manager has authority to make that change.
Compare interventions before selecting a tool
If a rule is explicit and the input is structured, test ordinary workflow automation first. If the task repeats a stable interface action, examine RPA and an integration alternative. If the difficulty is reading documents, consider IDP with source checks. AI may help where language or variable evidence requires interpretation, but its output still needs a task-specific acceptance standard. Process redesign or no technology change may be the right answer when policy, ownership, or an unnecessary step causes the problem.
Write down why each alternative would or would not address the observed cause. Do not compare a carefully controlled AI proposal with an artificially weak version of the current process. Include data repair, access approval, integration, training, review, and upkeep in each feasible option. An unavailable prerequisite is a reason to sequence work or pause, not a detail to hide inside a feasibility score.
Agree on a decision, not just a demonstration
Before a trial, name the business owner, evaluator, permitted data, review boundary, and person who can stop it. Define acceptable outputs and failures that must trigger escalation. Use examples held out from development, including missing information and uncommon cases. Compare the complete task with the baseline, including human verification and downstream consequences. Preserve the evidence behind the result so another owner can challenge the conclusion.
Keep value, feasibility, risk, and evidence confidence visible separately. A candidate with an attractive benefit estimate is not ready if its owner cannot obtain the data or operate the controls. Record the decision to investigate, pilot, wait, reject, or retire, with a reason and a condition for revisiting it. After delivery, compare observed results with assumptions rather than leaving the original estimate in the portfolio as fact.
Use the evaluation guide for the evidence standard and the prioritization guide to compare qualified candidates. Your leaders make funding decisions; a score or a discovery tool supplies structured evidence, not investment authority.
Continue through the discovery framework
Browse all departments and industriesRelated practice notes
For focused interview techniques, examples, and scoring detail alongside this field guide:
Bring a repeat-contact journey into IntakeOS
Use a redacted customer issue, its transfers, and the policy or action needed to resolve it. Explore how IntakeOS structures the process evidence so service leaders can compare a bounded opportunity with a simpler service fix.
IntakeOS supports structured interviews, qualification, and comparison; it does not make funding decisions or replace professional review. Learn about VARA, review the trust page, or explore the platform before sharing sensitive information.
Explore discovery in an IntakeOS demo