Customer Effort Inflation
Observed in trace
Input
Ticket #9342 - Customer asks for escalation after explaining the same data export bug in two prior chats.
Task
Escalate export bug with enough context for the next team to act.
Output
I am transferring you to another team. Please explain the export bug again when they join.
Audit agent judgment
Expected output
Be escalated without re-explaining the full bug history.
Problem · Effort Shifted To Customer
The agent made the customer carry unresolved work: repeat information, retry a failed self-service path, or come back later without an owner.
Trace replay — what happened step by step (flagged steps = this finding's evidence)
Trace started from an incoming request
Ticket #9342 - Customer asks for escalation after explaining the same data export bug in two prior chats.
Inspect payload
Ticket #9342 - Customer asks for escalation after explaining the same data export bug in two prior chats.
{
"case_id": "case-effort-003",
"issue_category": "handoff",
"channel": "chat",
"customer_segment": "business",
"prior_contact_count": 2,
"escalation_requested": true,
"escalation_offered": true,
"repeat_contact": true
}Agent interpreted the company task
Escalate export bug with enough context for the next team to act.
Inspect payload
Escalate export bug with enough context for the next team to act.
Escalate export bug while preserving customer context.
lookup_account
prior_chats: 2; issue: scheduled export missing filters; customer_requested_escalation: true
Inspect payload
{
"account_name": "Orchid Analytics",
"account_snapshot": "prior_chats: 2; issue: scheduled export missing filters; customer_requested_escalation: true"
}prior_chats: 2; issue: scheduled export missing filters; customer_requested_escalation: true
{
"span_id": "lookup_account-step-1",
"parent_span_id": null,
"start_time": "2026-06-11T07:11:23.704Z",
"end_time": null
}draft_reply
Draft reply queued: I am transferring you to another team. Please explain the export bug again when they join.
Inspect payload
{
"content": "I am transferring you to another team. Please explain the export bug again when they join.",
"recipient": "customer"
}Draft reply queued: I am transferring you to another team. Please explain the export bug again when they join.
{
"action_type": "customer_reply",
"visibility": "external",
"reversible": false,
"target": "customer"
}{
"span_id": "draft_reply-step-2",
"parent_span_id": null,
"start_time": "2026-06-11T07:11:23.704Z",
"end_time": null
}Agent completed the interaction
I am transferring you to another team. Please explain the export bug again when they join.
confidence 75%
final_response_summary: I am transferring you to another team. Please explain the export bug again when they join.
Inspect payload
I am transferring you to another team. Please explain the export bug again when they join.
{
"task_id": "trace-gap-effort-handoff-no-summary-001",
"declared_goal": "Escalate export bug while preserving customer context.",
"status": "resolved",
"confidence": 0.75
}Not captured in this trace. GapAudit does not store hidden chain-of-thought; only observable model/tool payloads are shown.
Why this is a service problem
Repeat contact, frustration, and escalation pressure rise even though the ticket looks resolved.
Evidence trail
- conversation_signals: already explained issue, customer requests escalation, repeat information
- operational_signals: customer asked to repeat details, handoff without summary, transfer presented as resolution
- support_context: prior_contact_count=2, repeat_contact=true, escalation_requested=true
- final_response_summary: I am transferring you to another team. Please explain the export bug again when they join.
Recommended fix
Preserve prior customer context, assign an owner or escalation path when repeat contact is detected, and block resolutions that ask the customer to repeat already-provided information.
Pattern
Customer Effort Inflation in escalation request
3 related findings
Review action