# Queue handoff and conventions

Assessment date: October 20, 2026 (PROMPT.md, Task 7). Policy: inputs/policy.md, version October 1, 2026. Only supplied records and customer claims were used. Deliverables are drafts; no messages sent, refunds issued, inspections performed, shipping arranged or escalations actually routed.

## Files
- triage.csv: all ten tickets, exact requested columns; row-level evidence citations.
- replies.md: one independently usable draft per ticket, each under 120 words including citations.
- handoff.md: conventions, checks and remaining work.

## Interpretation and routing
- All requests/reports are assessed as received October 20. Calendar elapsed days exclude the delivery/purchase day; delivery day + 30 is the last standard-return request date (inputs/policy.md, Returns).
- refund_cad is the calculable merchandise amount for an eligible or conditional refund, not money already paid. Conditional amounts must not be summed as approved refunds. T703's CAD 60 is the alternative to the requested replacement, not a second remedy. 0.00 means no refund under the stated request; blank means undetermined/not assessed (T708 safety, T710 missing order). Taxes and shipping cannot be calculated (inputs/policy.md, Evidence).
- Priority labels are operational assumptions, not policy-specified service levels: highest = required safety escalation; high = payment-team duplicate-charge review; normal = other requests. No response-time promise is implied.
- needs_human=yes identifies mandatory safety/payment review, missing-order follow-up, or outstanding photo/receipt verification. A no does not authorize automatic payment or mean that a human has already handled the ticket. T701 still requires receipt of the unopened item; T703 requires photo verification (inputs/policy.md, Returns; Defects and duplicates; Evidence).
- The alleged manager exception in T704 is unsupported and does not override the supplied policy. T710 must not be linked to A701 merely because both mention headphones (inputs/tickets.csv, T704/T710; inputs/orders.csv; inputs/policy.md, Evidence; Safety).

## Checks actually performed
Python standard-library checks against the written files:
- Exact CSV header; all ten input ticket IDs appear once in the same order in triage and reply sections.
- Each reply is fewer than 120 whitespace-delimited words, including its source note.
- Date differences computed from the order export against October 20, 2026:
  - A701: 30 elapsed days.
  - A702: 31 elapsed days.
  - A703: 5 elapsed days.
  - A704: 11 elapsed days.
  - A705: 12 elapsed days.
  - A708: 3 elapsed days.
  - A709: 12 elapsed days.
- Reply word counts: T701: 63, T702: 53, T703: 66, T704: 67, T705: 65, T706: 66, T707: 56, T708: 74, T709: 49, T710: 94.

## Remaining limitations and next steps
No access exists beyond the supplied export and claims. Receipt, damage photos, payment-team verification, a matching T710 order, private contact confirmation and actual safety routing are not available or completed. Safety eligibility has deliberately not delayed the T708 escalation recommendation. A human should route T708 first, review the remaining drafts, and carry out the indicated follow-up in authorized systems. T701's request is timely as of the assessment date; its receipt need not occur on that date under the supplied policy.

Estimated human effort: 15–25 minutes to review drafts and initiate follow-ups, not measured. Full resolution time cannot be estimated from these inputs because customer evidence, returned goods and payment/safety-team review are pending.
