How to choose a casino support outsourcing provider

Start with the work you want them to own

List what currently lands with your support team or founders. Separate answering chats from investigating payments, maintaining procedures, reviewing quality and managing the roster. A provider offering agents is not necessarily offering to run the whole operation.

Give each provider the same brief. Include channels, languages, recent demand by shift and the decisions agents can make. For a new casino, explain what is known and what is still a forecast. Ask how the service will be reviewed once real contact data becomes available.

Describe the actual problems you want solved. 'We need 24/7 support' leaves more room for interpretation than 'we need overnight chat coverage, ownership of payment follow-ups and a working knowledge base before launch.'

Use a case walkthrough instead of a sales promise

Ask the provider to walk through a hypothetical pending withdrawal using your process. What would the agent check? What information goes to payments? Who updates the player if the investigation runs into the next shift?

The useful part is their reasoning. They should recognise where your procedures and account permissions determine the answer. Someone who promises to resolve every payment issue without knowing those boundaries has not explained how they will deliver.

Use fictional or anonymised cases. There is no need to share live player records during an initial supplier conversation.

Separate availability from capacity

Ask how many people can be working on your queue at once, what workload the fee includes and what happens during a peak. 'Available all day' does not describe how many simultaneous conversations a team can handle.

For shared support, discuss competing demand across clients. For a dedicated team, check the roster, absence cover and whether supervision is included. In both cases, agree how additional staffing is requested and priced.

Ask which response targets apply to which channels, how they are measured and what the provider does after a missed target. A written target is useful only if the report makes it possible to check.

Check how training and access will work

Ask who builds the knowledge base, who confirms policy questions and how agents are assessed before working independently. You should not need a finished documentation library to begin the conversation, but somebody must own producing and approving it.

Request an access plan that fits your tools. Agents need individual accounts, permissions appropriate to their work and a clear process for removing access when someone leaves. Confirm where internal notes and player information will be stored.

Also ask how the team handles account-security concerns, responsible gambling concerns and decisions outside its authority under your approved procedures. These need distinct escalation routes, not a general instruction to message the manager.

Make the pilot answer specific questions

A paid pilot should help both sides judge whether the setup works. Agree its scope, start conditions, reporting and review date before it begins. Choose a workload the team can realistically handle during onboarding.

• Can agents find the correct information and explain their answers?
• Are response targets met across the agreed shifts?
• Do unresolved cases keep an owner and a follow-up time?
• Does the report distinguish support delays from other dependencies?
• How much work is still falling back to your internal team?

Agree how the service can expand, change or end, including the return of documentation and removal of access. Those details are easier to settle while everyone is planning the work.

Roundtide offers shared and dedicated support with a 30-day paid pilot. Our onboarding process covers preparation, training and the move into live coverage.