From complaint to verified resolution
Clear customer update, approved resolution and recurring issue follow-up.
Stop and check if…
- Unverified remedy/date or policy
- Safety issue requires qualified technician
- Public reply exposes private details
- No actual completion evidence
Do not mark a stage done just because AI produced a draft. Use actual evidence and human approval. Keep private records in your approved tools. Prompt Bro never submits, posts, pays or approves anything.
0 of 5 stages verified
Stages unlock in order. Only completion ticks are saved in this browser; no documents, inputs or AI outputs are stored.
All 5 stages verified. Keep the approvals and evidence in your own records; this tick list is not proof.
- What you need
- Verified ticket and customer's reported concern
- What to produce
- Draft reply, ticket ref, known facts and unknowns
- Who checks it
- Agent verifies before sending
Open the tasks
- Daily customer replies · Tested
- Angry complaints · Tested
- Call scripts and call summaries · Tested
If this happens
- Customer threatens legal action or a consumer forum: Acknowledge politely only; route to the manager and lawyer. Switch to: From contract dates to professional review
- Complaint involves safety (fire, shock, injury): Stop. Arrange a qualified technician and inform the manager now.
Handoff template
Workflow: From complaint to verified resolution Stage: Understand and acknowledge (1 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Draft reply, ticket ref, known facts and unknowns Approval status (approved / pending / rejected): [confirm] Approved by (Agent verifies before sending): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Choose route, needs: Policy, order/claim evidence and escalation note
- What you need
- Policy, order/claim evidence and escalation note
- What to produce
- Review-only return/warranty check or manager escalation
- Who checks it
- Manager decides remedy; legal threat to lawyer
Open the tasks
- Escalation summaries · Tested
- Returns and refunds · Not yet tested
- Warranty and AMC claims · Tested
If this happens
- Remedy is outside policy or above your authority: Escalate with a summary; do not promise anything. Use: Escalation summaries
Handoff template
Workflow: From complaint to verified resolution Stage: Choose route (2 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Review-only return/warranty check or manager escalation Approval status (approved / pending / rejected): [confirm] Approved by (Manager decides remedy; legal threat to lawyer): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Fulfil approved action, needs: Approved service action and actual availability
Unlocks after stage 1 is verified.
- What you need
- Approved service action and actual availability
- What to produce
- Technician/parts/claim checklist, held issues
- Who checks it
- Service/dispatch verifies and performs approved action
Open the tasks
- Ticket assignment and technician scheduling · Tested
- Troubleshooting guides · Tested
- Spare parts queries · Tested
- Courier claims · Tested
If this happens
- Promised date, part or technician is not confirmed: Tell the customer what is confirmed and when you will update; don't invent a date. Use: Delay and issue notifications
- Shipment lost or damaged in transit: Open a courier claim with the evidence. Use: Courier claims
Handoff template
Workflow: From complaint to verified resolution Stage: Fulfil approved action (3 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Technician/parts/claim checklist, held issues Approval status (approved / pending / rejected): [confirm] Approved by (Service/dispatch verifies and performs approved action): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Confirm resolution, needs: Actual completed action and approved public/private response
Unlocks after stage 2 is verified.
- What you need
- Actual completed action and approved public/private response
- What to produce
- Customer update, open status or closure evidence
- Who checks it
- Agent verifies actual completion; no invented closure
Open the tasks
- Shift handover notes · Tested
- Delay and issue notifications · Tested
- Review responses · Tested
- Verify complaint resolution and close tickets · Tested
- Refund and replacement reconciliation · Tested
If this happens
- No proof the fix, refund or replacement actually happened: Keep the ticket open; go back and complete the action. Go to stage 3: Fulfil approved action
- Customer says the problem is not solved: Re-open and choose the route again. Go to stage 2: Choose route
Handoff template
Workflow: From complaint to verified resolution Stage: Confirm resolution (4 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Customer update, open status or closure evidence Approval status (approved / pending / rejected): [confirm] Approved by (Agent verifies actual completion; no invented closure): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Learn, needs: Anonymised ticket data and feedback
Unlocks after stage 3 is verified.
- What you need
- Anonymised ticket data and feedback
- What to produce
- Issue patterns, coaching notes, questions
- Who checks it
- Manager assigns corrective action
Open the tasks
- Ticket analysis · Tested
- Chat and call quality audit · Tested
- Satisfaction surveys · Tested
- Root-cause analysis and corrective-action follow-up · Tested
If this happens
- The same issue keeps coming back: Assign a root-cause owner and due date. Use: Root-cause analysis and corrective-action follow-up
Handoff template
Workflow: From complaint to verified resolution Stage: Learn (5 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Issue patterns, coaching notes, questions Approval status (approved / pending / rejected): [confirm] Approved by (Manager assigns corrective action): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: none. Workflow ends after this approval.
Unlocks after stage 4 is verified.