Cash Desk Live Chat

Use this page for real-time communication on urgent transaction issues.

Interface Reference #

Purpose #

• Resolve active payment/withdrawal issues quickly.
• Coordinate between support, operations, and cash desk teams.
• Reduce response latency for high-impact incidents.

Standard Handling Flow #

1. Open incoming chat and classify issue type.
2. Confirm user identity and transaction reference.
3. Verify issue in operations pages before replying.
4. Provide action + ETA (or escalation notice).
5. Close chat only after confirmation.

Priority Model #

• P1: payment stuck, large-value issue, repeated system failure.
• P2: delayed processing, verification mismatch.
• P3: informational or non-blocking query.

Agent Response Checklist #

• Include ticket/reference ID in first response.
• Share next action and expected timeline.
• Avoid ambiguous statements; use policy-safe language.
• Capture escalation reason if transferred.

Troubleshooting #

• Chat not updating: refresh socket/session.
• Wrong queue assignment: re-route to correct team queue.
• Missing transaction context: request reference ID before action.

Best Practice #

Use short, structured responses: status, action, ETA, next update point.