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
- Step or milestone
- SAMPLE-01
- Trigger or date
- Before weekly quality review
- Evidence and source ID
- F02: 184 contacts across four categories; F12: sampling is complaint-only and averages privacy failures.
- Owner
- Quality owner
- Gate or threshold
- Learner proposal: representative category sample plus 100% review of defined critical-risk cases.
- Dependency or gap
- Contact-level sampling frame and approved threshold not supplied.
- Status
- Draft — approval pending
A well-handled evidence gap
- Step or milestone
- SAMPLE-02
- Trigger or date
- Before selecting records
- Evidence and source ID
- F11 reports common note omissions.
- Owner
- Service QA reviewer
- Gate or threshold
- Gate: sampling frame and access authorization must be approved.
- Dependency or gap
- Record list, reviewers, and privacy handling are not supplied.
- Status
- Blocked — not supplied
Flawed approach — do not copy
Marking this quality sampling plan “approved and complete” without the required evidence or reviewer is a flawed submission. Stop selection or review when access, sampling frame, or critical-failure definitions are not approved.
Repair: Rework the quality sampling plan as an evidence-backed draft, not an approved result. Define the review population and four issue categories from F02. Create a representative sampling stratum plus targeted review for privacy, security, safety, and honesty risk. Use F12 to separate critical failures from average scoring. Check the revision against this requirement: Population, strata, cadence, owner, and provisional gate are present. 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 →