Foundry Academy · Customer Service Operations · Lesson 3 of 6

Issue diagnosis and active listening

Convert a customer's narrative into a verified problem statement, reproducible facts, and an agreed next step without premature conclusions.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Issue diagnosis and active listening

Objective: Convert a customer's narrative into a verified problem statement, reproducible facts, and an agreed next step without premature conclusions.

Diagnosis begins by separating the customer's goal, observed symptom, timing, environment, and impact. Restate what you heard and invite correction: this confirms shared understanding without implying that the customer's interpretation is wrong. Ask one purposeful question at a time, beginning with facts that change the path of the case. Avoid making customers repeat information already present in the record. Distinguish observation from inference; 'the payment page displayed an error at 10:14' is an observation, while 'the bank declined the card' is a conclusion that may require evidence. Record uncertainty explicitly rather than filling gaps with guesses.

Active listening is demonstrated through decisions, not filler phrases. Summarize the issue, acknowledge material impact, explain why the next question matters, and check whether the proposed next step addresses the customer's immediate need. Use a reproducibility sequence for technical cases: starting state, exact action, expected result, actual result, time, environment, and frequency. For policy or billing cases, record the relevant transaction, policy version, authority level, and exception question. When safety, discrimination, fraud, legal threat, severe vulnerability, or significant financial harm appears, stop routine troubleshooting and follow the approved escalation process.

Before you begin

  • Confirm F02, F05, F08, and F09 are present; record that model, version, timestamps, error text, prior actions, and approved safety language are absent.
  • STOP. If the device details, error record, prior actions, or approved safety language are missing or conflict with F02/F05/F08/F09, route the gap to the qualified service/engineering owner; do not claim diagnostic approval or execute a reset, repair, or safety instruction.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This is a fictional, sanitized training case. All people, accounts, products, contacts, and records are fabricated; no real personal or confidential data is present, and no legal, safety, or warranty outcome is promised.

Harbor Home support recovery

Harbor Home Systems is a fictional seller of connected thermostats. A firmware update was released to 6,200 active devices on Monday. By Wednesday, support had received 184 contacts: 91 about repeated login prompts, 47 about schedules resetting, 18 about an unfamiliar error code, and 28 unrelated questions. The public service promise says customers receive a meaningful first response within four business hours, but the queue median is 7.2 hours and 36 cases have waited longer than 12 hours. The knowledge base tells agents to reset the device, yet engineering's internal notice says repeated resets can erase diagnostic logs needed for investigation. Identity verification is inconsistent: some agents request a full date of birth for low-risk preference changes, while others make account-email changes after confirming only a device nickname. One customer says a cold home creates an urgent safety concern for an elderly parent, but the agent cannot verify conditions or diagnose health risk. A team lead drafted a blanket promise that all schedules will be restored today; engineering has only reproduced the issue on one device model and has no recovery estimate. Case notes frequently say fixed or angry customer without recording observed behavior, approved steps, result, owner, or next action. Quality reviews sample only complaints and average privacy failures into the overall score. The operations manager wants agents to close every case after sending the reset article to reduce backlog. Learners must design a truthful service response, proportionate verification, disciplined diagnosis, reliable notes, de-escalation and escalation, and a quality-coaching loop. The exercise requires urgent safety concerns to be routed through approved emergency and specialist procedures without the learner diagnosing, guaranteeing restoration, or requesting unnecessary sensitive data.

Supported example — reference only

Element
TRIAGE-01
From or trigger
Customer reports schedule reset
To or outcome
Preserve logs; request model, version, time, symptom, and prior-action fields before diagnosis.
Evidence and source ID
F05, F09
Owner
Qualified support and engineering reviewer
Open question
Record-level values and approved diagnostic action are not supplied.
Status
Draft — review pending

A well-handled evidence gap

Element
TRIAGE-02
From or trigger
Urgent cold-home report
To or outcome
Pause diagnosis and route for authorized immediate-safety wording.
Evidence and source ID
F08
Owner
Qualified safety/service owner
Open question
Temperature, device state, timestamps, and approved safety language are not supplied.
Status
Open — escalation required

Flawed approach — do not copy

Marking this issue-triage decision tree “approved and complete” without the required evidence or reviewer is a flawed submission. Stop reset or diagnostic guidance when logs may be lost, facts are incomplete, or safety is implicated.

Repair: Rework the issue-triage decision tree as an evidence-backed draft, not an approved result. Start with observable symptom and urgency, not a diagnosis. Capture device model, version, time, customer-observed symptom, and prior action as required fields. Use F05 to stop reset guidance when evidence preservation applies. Check the revision against this requirement: Every branch distinguishes report, observation, and conclusion. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the issue-triage decision tree.

Create a question and observation flow that preserves diagnostic evidence and separates symptom from cause.

Deliverable: An issue-triage tree plus a bounded triage-record starter using the aggregate unfamiliar-error category, the schedule-reset evidence, and the urgent cold-home report; record-level error text, device details, and timestamps remain not supplied.

Complete a bounded starter and gap analysis using only CB01, F02, F05, F08, F09, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M03-I01 · F02 — Support received 184 contacts across four recorded issue categories by Wednesday.
  • M03-I02 · F05 — The public reset article conflicts with engineering's instruction to preserve diagnostic logs.
  • M03-I03 · F08 — One customer reports an urgent cold-home concern involving an elderly parent.
  • M03-I04 · F09 — Engineering reproduced schedule reset on one model and has no recovery estimate.
  • M03-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M03-S01 · F02, F05, F08, F09 — Build a starter version of “An issue-triage tree plus a bounded triage-record starter using the aggregate unfamiliar-error category, the schedule-reset evidence, and the urgent cold-home report; record-level error text, device details, and timestamps remain not supplied.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Start with observable symptom and urgency, not a diagnosis.
  2. Capture device model, version, time, customer-observed symptom, and prior action as required fields.
  3. Use F05 to stop reset guidance when evidence preservation applies.
  4. Separate customer report F08 from engineering finding F09 and aggregate contact fact F02.
  5. Route urgent safety language and technical diagnosis to qualified owners.
  6. Quality-check every branch for a source ID, open question, owner, and truthful pending status.
Field-by-field guidance
Element
Name the process node, asset, state, or transition. Module use: Use the tree to preserve diagnostic evidence and separate report, observation, and engineering conclusion.
From or trigger
State the observable event that activates the path. Module use: Use the tree to preserve diagnostic evidence and separate report, observation, and engineering conclusion.
To or outcome
State the proposed next state without implying execution. Module use: Use the tree to preserve diagnostic evidence and separate report, observation, and engineering conclusion.
Evidence and source ID
Pair the observation with its exact supplied source ID. Module use: Use the tree to preserve diagnostic evidence and separate report, observation, and engineering conclusion.
Owner
Name the authorized operating or specialist role. Module use: Use the tree to preserve diagnostic evidence and separate report, observation, and engineering conclusion.
Open question
Record the unanswered question that prevents a final decision. Module use: Use the tree to preserve diagnostic evidence and separate report, observation, and engineering conclusion.
Status
Use a truthful state such as draft, open—not supplied, review pending, or blocked. Module use: Use the tree to preserve diagnostic evidence and separate report, observation, and engineering conclusion.
Issue-triage decision tree · learning draft
ElementFrom or triggerTo or outcomeEvidence and source IDOwnerOpen questionStatus

Start with 5 rows; the complete workbook specifies 5 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 3 · 2-item formative check

Issue diagnosis and active listening

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 3 · knowledgeWhich statement records a verified observation rather than an inferred cause?
Question 2 of 2 · MODULE 3 · scenarioF05 is conflicting because the public reset article contradicts engineering’s log-preservation instruction; F09 confirms schedule reset on one model with no recovery estimate. No completed triage record is supplied. What is the proper gate?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • Every branch distinguishes report, observation, and conclusion.
  • Required diagnostic fields and preservation stop are explicit.
  • No error code, diagnosis, or safety instruction is invented.

Stop: Stop reset or diagnostic guidance when logs may be lost, facts are incomplete, or safety is implicated.

Go: Continue bounded questioning when observations can be captured without altering evidence.

Escalate: Escalate safety, unknown device state, and conflicting guidance to qualified service/engineering owners.

04 · Evidence to keep

Leave with usable work.

Submit the interview notes, corrected problem statement, and an escalation decision with the reason for that decision.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Customer support professional working with a headset and laptop.
Learn the standard. Practice the work.
Office professional documenting and resolving a customer service case.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

ada-web-accessibility-guidance · Official guidance

Guidance on Web Accessibility and the ADA

U.S. Department of Justice guidance explaining accessibility barriers and responsibilities for businesses and public entities.

Open reviewed external source ↗

ws-customer-service-operating-standard · Academy internal operating standard

Wealth Synergy customer-service internal operating standard

Academy-selected service-promise, case-note, triage, escalation, knowledge, QA, and review controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.