Client profile
GoldRiver Casino, a Gibraltar-based online casino with 140 staff.
Challenge and scope
Frontline agents escalate 28% of withdrawal queries to payments in the baseline. Handling can require checks in several provider portals.
A status shown in the casino’s console may lag a provider response or show a different stage of the transaction. Agents can escalate simple enquiries while asking the operator to confirm information that already exists in the account history. Some cases still need the operator to decide on a hold or release.
Delivery workflow
Handle 5,800 monthly withdrawal questions on a 24/7 roster across six payment providers. Reconcile status in the approved tools and escalate holds or release decisions to the operator.
Match the withdrawal reference with the operator console and authorized provider records. Explain the last confirmed status using approved language and log any discrepancy. Refer unresolved holds, suspected provider errors, or approval decisions with the payment reference, timestamps, and supporting data.
Create a request reason for missing status, provider delay, and cases requiring operator review. Sample replies against the confirmed status at the time of response. Track repeated enquiries by provider and flag recurring visibility gaps to the payments owner so guidance can be updated.
Delivery team
Poland, about 10 FTE. 1 payments support lead, 2 QA reviewers and 7 associates.
Systems and tools
Zendesk, client payments console, provider portals.
Client decision rights
The operator owns payment release, account decisions, and responsible-gambling interventions.
Early milestone
The week 3 record shows a 5.4-minute withdrawal-query resolution time.
Outcomes
Company-reported results, with the baseline, measurement window and supporting record described for each measure.
| Measure | Baseline | Result | Window | Supporting record |
|---|---|---|---|---|
| Withdrawal-query resolution | 11 min | 2.2 min | 4 months | Zendesk analytics |
| Escalation to payments | 28% | 6% | 4 months | Zendesk analytics |
| Player CSAT | 3.7/5 | 4.6/5 | 4 months | Zendesk analytics |
Interpreting the results
In this case, withdrawal-query resolution drops from 11 to 2.2 minutes and fewer contacts go to the payments team. Count support resolutions and updates consistently across providers. Review a sample of referrals and repeat contacts and compare the settlement timestamps separately where the client holds that data.
Recommendations for new clients
For casinos with payments backlogs, test the accuracy of player updates and measure query resolution separately from withdrawal approval and settlement time.
Bring a provider status map and sample withdrawals at pending, approved, sent, and returned stages. Define which data agents can read and which decisions require the operator. Check that responses are accurate for each stage and that escalated cases contain enough evidence for the payments team to act.