Context Neglect
Observed in trace
Input
Ticket #9011 - Finmark asks for SLA credit after two days of degraded exports. Contract says export outage credit applies after four business hours.
Task
Assess SLA credit eligibility and reply with the appropriate remedy.
Output
No credit is available because the service was not fully down. Ticket resolved.
Audit agent judgment
Expected output
Receive the service credit promised by the contract for export degradation.
Problem · Context Ignored
The agent had account, policy, or contract evidence that should have changed the answer, but closed the work against that context.
Trace replay — what happened step by step (flagged steps = this finding's evidence)
Trace started from an incoming request
Ticket #9011 - Finmark asks for SLA credit after two days of degraded exports. Contract says export outage credit applies after four business hours.
Inspect payload
Ticket #9011 - Finmark asks for SLA credit after two days of degraded exports. Contract says export outage credit applies after four business hours.
{
"case_id": "case-sla-credit-001",
"issue_category": "sla-credit",
"channel": "email",
"customer_segment": "enterprise",
"escalation_offered": false
}Agent interpreted the company task
Assess SLA credit eligibility and reply with the appropriate remedy.
Inspect payload
Assess SLA credit eligibility and reply with the appropriate remedy.
Assess export SLA credit eligibility from contract and policy context.
lookup_account
plan: Enterprise; contract: export SLA credit applies after 4 business hours degraded export service; outage_duration: 2 days
lookup_account: plan: Enterprise; contract: export SLA credit applies after 4 business hours degraded export service; outage_duration: 2 days
Inspect payload
{
"account_name": "Finmark",
"account_snapshot": "plan: Enterprise; contract: export SLA credit applies after 4 business hours degraded export service; outage_duration: 2 days"
}plan: Enterprise; contract: export SLA credit applies after 4 business hours degraded export service; outage_duration: 2 days
{
"span_id": "lookup_account-step-1",
"parent_span_id": null,
"start_time": "2026-06-11T07:11:22.806Z",
"end_time": null
}policy_search
SLA Policy v3. Enterprise export degradation above four business hours qualifies for monthly service credit even when the platform is not fully down.
policy_search: SLA Policy v3. Enterprise export degradation above four business hours qualifies for monthly service credit even when the platform is not fully down.
Inspect payload
{
"query": "export degradation SLA credit contract",
"policy_result": "SLA Policy v3. Enterprise export degradation above four business hours qualifies for monthly service credit even when the platform is not fully down."
}SLA Policy v3. Enterprise export degradation above four business hours qualifies for monthly service credit even when the platform is not fully down.
{
"span_id": "policy_search-step-2",
"parent_span_id": null,
"start_time": "2026-06-11T07:11:22.806Z",
"end_time": null
}draft_reply
Draft reply queued: No credit is available because the service was not fully down. I have marked the ticket resolved.
Inspect payload
{
"content": "No credit is available because the service was not fully down. I have marked the ticket resolved.",
"recipient": "customer"
}Draft reply queued: No credit is available because the service was not fully down. I have marked the ticket resolved.
{
"action_type": "customer_reply",
"visibility": "external",
"reversible": false,
"target": "customer"
}{
"span_id": "draft_reply-step-3",
"parent_span_id": null,
"start_time": "2026-06-11T07:11:22.806Z",
"end_time": null
}Agent completed the interaction
No credit is available because the service was not fully down. Ticket resolved.
confidence 75%
final_response_summary: No credit is available because the service was not fully down. Ticket resolved.
Inspect payload
No credit is available because the service was not fully down. Ticket resolved.
{
"task_id": "trace-gap-credit-sla-001",
"declared_goal": "Assess export SLA credit eligibility from contract and policy 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
Eligible customers get denied, sent backward, or asked to redo work the system already knows about.
Evidence trail
- lookup_account: plan: Enterprise; contract: export SLA credit applies after 4 business hours degraded export service; outage_duration: 2 days
- policy_search: SLA Policy v3. Enterprise export degradation above four business hours qualifies for monthly service credit even when the platform is not fully down.
- final_response_summary: No credit is available because the service was not fully down. Ticket resolved.
Recommended fix
Require the agent to reconcile retrieved account and policy context before closing or denying the customer request. Route exception-qualified cases to a human approval path.
Pattern
Context Neglect in sla credit request
3 related findings
Review action