CHINZY / FDE and robotics acceptance fieldbook / 04
Support tickets and handoff
Use fictitious devices and tickets from intake through closure. A reviewer should recover the original question, final owner and unresolved items by ticket ID, independently of the chat transcript.
Acceptance checks
Exact serial-number matching
Assign adjacent serial numbers to two devices with different tickets. A missing digit calls for a label check, not another device’s history.
02Human handoff context
Trigger handoff and open the ticket as the receiving agent. Verify the symptom, attempted fix and open question so the customer need not start again.
03Routing a mixed-intent ticket
Report a fault and ask for an invoice in one ticket. Preserve both intents and assign a primary owner and referral, rather than losing the second request.
04Unverified warranty eligibility
Provide purchase date but no warranty terms or installation record. List missing evidence and route to review rather than promising a free replacement.
05Duplicate fault reports
Report one device fault through two channels, then change the fault code. Deduplication must retain both sources without merging a different incident.
06Service deadline clock
Record intake, first human reply and closure separately. Apply the agreed clock across zones or pauses; an automatic receipt is not a human reply.
07Identifiers in translated tickets
Translate the symptom but preserve the serial, fault code and units. Retrieve the ticket by the original string and compare against the source.
08Evidence before closing a ticket
In a pilot requiring customer confirmation, test advice sent versus recovery confirmed. Keep the confirmation time and channel before closing.