A practical checklist for launching 24/7 casino support
A staffed inbox is only one part of being ready. Before the first player arrives, the team needs working access, clear answers and someone to contact when a case cannot wait until morning.
1. Decide what support can resolve
Write down the work agents own and the decisions that require approval. Cover account access, deposits, withdrawals, verification, bonuses and technical issues. For each topic, identify what an agent can check, what they can tell the player and when they must escalate.
Keep account permissions aligned with those responsibilities. An agent may need to view payment status without having permission to approve a withdrawal or change an account restriction. Test the actual access instead of assuming a role name gives them what they need.
Document how agents recognise and route responsible gambling concerns, account-security issues and urgent complaints using the operator's approved procedures. These should not disappear into the routine payment queue.
2. Test the player journey and the tools
Walk through registration, verification, depositing, claiming a bonus and requesting a withdrawal in an authorised test environment. Record the status messages a player sees and where the corresponding information appears in the back office.
Use individual agent accounts with the access protections your systems support. Confirm that overnight agents can open the helpdesk, knowledge base and approved escalation channels. Check that emails arrive in the correct queue and that a chat can be handed over without losing its history.
A broken login at 3 AM can turn a fully staffed shift into a team that cannot investigate anything. Include access recovery and a backup contact in the launch plan.
3. Build a small, usable knowledge base
You do not need hundreds of articles before launch. You need accurate answers to the situations the team is likely to face. Start with the actual payment flows, verification steps, active promotions and common account problems.
- For each procedure, name the person who can confirm changes.
- Show where to check information, not just what reply to send.
- Explain exceptions and the point at which the standard answer stops applying.
- Keep player-facing wording separate from internal investigation steps.
A bonus macro is only useful if the agent can check eligibility and find the terms that applied when the player joined. Give the team new promotion details before the offer goes live.
4. Plan coverage and escalation together
A week has 168 hours. Build the roster around the number of agents needed at once, then allow for breaks, leave, sickness and training. Our staffing calculation shows why dividing 168 by a working week is only the starting point.
Separately, decide who is available for payment, technical and account decisions outside normal office hours. If an issue must wait, agents need an honest update they can give the player and a reliable follow-up process.
For a new casino, initial demand is uncertain. Set a review point after launch and agree how you will add capacity if queues exceed the plan. Tell support about campaigns and releases that could change demand.
5. Rehearse cases before opening the queue
Run short practice cases using your own systems and procedures. Include a missing deposit, a pending withdrawal, an expired bonus and a verification request that needs clarification. Add a case that must be escalated immediately.
Ask the agent to explain why they chose the response. You are checking whether they can find and interpret the information, not whether they can recite a macro. Fix unclear procedures while the exercise is still internal.
Issue: withdrawal still pending.
Checked: request found; current status recorded.
Waiting on: payments team investigation.
Player told: we will update them today.
Next action: named owner to follow up at the recorded time.
In the real note, include the case reference and an exact follow-up time with a timezone. Keep sensitive documents in the approved system rather than copying them into general team chat.
6. Review the first week while it is happening
Check the queue daily during launch. Look for repeated questions, stalled investigations, incorrect macros and delays between shifts. Update the knowledge base as you learn rather than waiting for a monthly report.
Track a small set of support metrics, including response time by shift, unresolved-case age and quality review findings. Combine the numbers with a few actual conversations so you can see why a result changed.
Roundtide can help prepare the knowledge base, train the team and run 24/7 live chat support. See how onboarding works for the steps from planning to the first shift.