A complaint summary should preserve what the customer alleges, what evidence establishes, and what remains disputed. Compression must not turn frustration into verified fault or a requested remedy into an approved outcome.
Complaint fidelity includes attribution
A faithful support summary records the issue, relevant chronology, customer-stated impact, attempted remedies, requested next step, and unresolved facts. It should distinguish direct customer statements from system lookups and agent inference.
For a proposed evaluation, split consequential summary claims into supported, contradicted, unsupported, or uncertain categories. Separately check required omissions: a summary can avoid invented facts while still omit the one unresolved issue staff need to handle.
Preserve corrections and disagreements. If the customer retracts an earlier date or disputes an internal note, the summary should make the current position clear without erasing the existence of the dispute where relevant.
Review a fictional missed-visit complaint
A customer says a technician did not arrive and asks for a refund. The dispatch lookup fails, and no refund operation runs. A summary saying “technician missed the visit; refund arranged” makes two unsupported upgrades.
A faithful version says the customer reports a missed visit, requests a refund, and needs staff review because dispatch status was not verified. It also preserves the approved contact preference if follow-up is required.
| Summary element | Fidelity check |
|---|---|
| Alleged service failure | Attribution retained |
| Customer correction | Latest confirmed version used |
| Requested compensation | Not described as approved |
| Tool result | Actual completed or uncertain state |
| Unresolved question | Clear next action for staff |
Use fictional transcripts and authoritative tool fixtures. Illustratively, three unsupported claims among 30 reviewed consequential claims is a ten percent claim-level defect rate for that fixture set, not a real-world benchmark.
Keep staff usefulness in the rubric
A summary should help the receiving employee act without replaying the entire conversation. Include a concise issue and next step, with controlled links to source evidence. Avoid unrelated personal narrative or speculative character judgments about the customer.
Human reviewers may disagree about whether wording implies fault or commitment. Calibrate with examples and preserve adjudication rationale. Automated graders can assist triage but should not replace evidence review for material disputes.
This evaluation design is proposed. The voice integration case study describes related support work. Pair it with summary-to-source evaluation.
Complaint summary FAQ
Should customer emotion be summarised as a diagnosis?
No. Use relevant observable statements without unsupported personal judgments.
Is a requested refund a completed remedy?
No. Preserve the actual decision and execution status.
What makes the summary ready for handoff?
Staff can identify the complaint, verified facts, disputed points, requested outcome, and accountable next step.