How to Start an Online Casino or Sportsbook: The Operations Stack, in the Order You Decide It

You have probably spent the last month on two things: a licence application checklist and a run of platform demos. Both deserve the time. Neither tells you who will answer a depositing player at 2 a.m., or which phone your first VIP host will use. And if that host runs players from Telegram's official app, the app holds three accounts, four with Premium, which is about where a growing desk starts juggling phones.

This guide covers how to start an online casino or a sportsbook as a sequence of operating decisions, in the order a founder actually makes them. Each decision narrows the next. It argues one position: founders budget for the platform and forget the people layer, and the three parts of the CRM stack (player CRM, affiliate platform and the conversation layer) should be planned before launch, not patched in after the first complaint.

It is written for founders, COOs and heads of operations at operators that intend to be licensed in every market they serve. It is not legal advice. Every regulatory point below links the regulator or law it comes from, and anything this guide is not certain of is marked "check with the regulator", because rules, fees and timelines change and differ by market.

Most guides to opening an online casino list the same components. The useful question is which choice constrains which. This is the order in which they constrain each other, whether a founder plans it that way or not:

Decisions 1 to 5 get budgets, lawyers and vendor shortlists. Decision 8 usually gets a line in a hiring plan and a shared phone. The rest of this guide goes through each one, and spends the most time on the part founders skip.

Start with the markets, not the platform. A licence is issued for a jurisdiction, and the jurisdiction decides who you may serve. Never accept players from a market where you are not licensed or where online gambling is prohibited, and get advice from a gambling lawyer before you commit to any of the routes below.

Some of the regulators founders compare most often:

• Great Britain. The Gambling Commission states that you need a licence from it if you provide remote gambling to consumers in Great Britain, and that this applies to businesses based outside Britain too. Its pages set out the licence types and the application service; check the current fees and requirements with the Commission.
• Malta. The Malta Gaming Authority licenses and supervises gaming under the Gaming Act (Cap. 583). Its applications page is the starting point; check the requirements with the MGA directly.
• Curaçao. The National Ordinance on Games of Chance (LOK) made the Curaçao Gaming Authority the regulator for online gaming, replacing the earlier master licence and sub-licence arrangement with licences held directly from the authority. Requirements under the new regime are still settling, so check them with the CGA.
• United States. Online casino games and sports betting are legal only where a state has legalised them, and each of those states runs its own licensing. New Jersey's Division of Gaming Enforcement is one example. Fewer states permit online casino games than sports betting, so check each state's regulator for the product you plan to offer.
• Brazil. Lei 14.790/2023 created an authorisation regime for fixed-odds betting under the Ministry of Finance's Secretariat of Prizes and Betting (SPA). On 25 September 2026, Provisional Measure 1.394 prohibited the operation, offer and advertising of fixed-odds betting nationwide, covering both sports betting and online games, and required betting sites and apps to be unavailable from 6 October 2026. The measure is before Congress and could change, so do not plan a Brazilian launch until the SPA says the market is open again.

The licence also writes most of the rules for decisions 3 to 8: which payment methods are acceptable, how players are verified, what marketing is allowed, how complaints are handled. That is why it comes first. A platform demo that looks right for one jurisdiction can be wrong for another.

There are three broad ways to get a casino or sportsbook front end, wallet and back office. Described neutrally:

Whether a white label arrangement is permitted at all, and on what terms, is a licensing question. Ask the regulator in each target market before signing, because some regulators expect the licence holder to control the operation directly.

For a sportsbook, the platform question splits in two: the betting front end and account system, and the trading side (odds, limits, risk management), which may come from the same provider or a different one. Ask every vendor which parts they run and which they expect you to staff.

One question to put to every platform vendor: what the platform does not cover. The answers almost always include affiliate tracking, some or all payment providers, and every conversation your team will have with a player outside the site itself.

Payment providers decide market by market whether they will process gambling transactions, and regulators set rules on which methods are acceptable. A method that works for one licensed market may be unavailable or restricted in another. Expect to hold several providers, and check each market's rules with the regulator and the provider before you promise a method on launch day.

The operational point founders miss: withdrawal questions are where players get anxious and write in. Whatever your payment stack, someone on your team will spend a lot of each day answering "where is my withdrawal", and that conversation needs an owner.

Verification, age checks, deposit limits, time-outs and self-exclusion are licence conditions, not later features. The detail differs by regulator, so take it from the licence conditions in each market you serve.

Great Britain shows how specific this gets. GAMSTOP, the national online self-exclusion scheme, records that integrating with it became a licence condition for operators serving British customers in 2020, with a check of the whole customer base every 24 hours. The Gambling Commission's guidance on keeping self-excluded customers out of marketing warns against a single point of failure and names staff using manual workarounds as a cause of breaches.

That warning matters for decision 8. A host messaging a player from a phone is a manual workaround by definition. If your people layer is not designed to carry the exclusion flag your compliance team sets, it is the place your responsible gambling process is most likely to fail.

A casino catalogue comes from game studios and aggregators; a sportsbook needs data and odds feeds plus a trading model. Each supplier has its own licensing position, and many regulators expect suppliers to be licensed or certified in the markets you serve. Check with the regulator which supplier licences apply before you sign.

Two practical notes. First, supplier contracts take longer than integrations, so start them alongside the licence application rather than after it. Second, the more games and markets you carry, the more product questions reach support. Your people layer grows with your catalogue whether you plan for it or not.

From here on, the decisions are about the CRM stack, which is really three systems doing three different jobs. Founders tend to buy the first one and assume it covers the other two.

The first layer is the player CRM: the system that segments the player base from platform data and sends automated campaigns by email, push, SMS or an opted-in bot. Vendors such as Optimove, Fast Track, Smartico and Xtremepush compete here, and our iGaming CRM comparison covers what each one does and does not do, so this guide will not repeat it.

What matters for a founder is timing. The player CRM needs platform data to segment on, so it is usually chosen with the platform, and it inherits every consent and exclusion rule from decision 4. It is built for the many players a person could never message individually. It is not built for the few who expect a named person to answer, and our guide to where automation should stop and a person should take over explains how to draw that line before the first top-value player signs up.

The second layer tracks affiliate traffic and pays commission: tracking links, deal types, reporting, payouts. It is a separate purchase from the platform in most stacks, and it has to be in place before your first partner sends a player, because tracking cannot be applied backwards.

What the affiliate platform does not do is the relationship. Deals with affiliates are negotiated, renegotiated and chased in conversation, and in this industry many of those conversations happen on Telegram. The platform counts the traffic. Someone still has to win the partner.

The third layer is the conversation layer: support agents answering players, VIP hosts looking after the top of the player base, affiliate managers talking to partners. In many operations a lot of that happens on Telegram, from personal accounts, because that is where players and partners already are.

This is the layer founders leave out of the budget, and it fails in predictable ways:

• The accounts belong to people, not the company. A host who leaves takes the account, the chats and the relationships with them.
• The desk outgrows the phone. A few accounts per person is manageable in the official app. A support desk, three hosts and two affiliate managers across several brands is not.
• Nobody can see response times. The player CRM measures campaigns. Nobody measures how long a VIP waited for a reply.
• Compliance flags stop at the platform. The exclusion flag lives in the back office; the host's chat list does not know about it.

Plan it like the other two layers: decide whose accounts these are, who covers whom, and where the exclusion flag shows up, before you open.

This is the layer Entergram is built for, and our Telegram CRM for casinos page covers it in product terms. In short: Entergram runs on real personal Telegram accounts, not bots, and puts 100+ of them in one inbox that you filter by account instead of switching between them. Each account routes through its own unique proxy. An account can be shared with the workspace, which suits a support desk replying from one identity, or kept private to one person, which suits a host or affiliate manager. Every chat has a built-in Assignee field, so one player has one owner. Four inward privacy controls (hide usernames, hide group member information, block message editing, block message deletion) address the realistic risk, which is a team member leaving with the book.

The limits, stated plainly: Entergram does not check KYC, ages, licences or self-exclusion status, and it does not integrate with casino platforms, player CRMs or affiliate platforms. It holds the flags your compliance process sets, as custom fields that broadcasts and views filter on. Its shipped integrations are HubSpot, Zendesk, Notion, Make.com and Slack. If your support team works in Zendesk, private Telegram chats on selected accounts become Zendesk tickets and agents reply from the real Telegram account; Slack can receive a one-way copy of every chat a seat can access, as an audit log. For the step-by-step configuration of accounts, roles, fields and reply targets, follow this casino desk setup walkthrough.

The reason to decide the CRM stack before launch is that each layer is hard to retrofit:

The last row is the expensive one. Once a player is used to writing to a host's personal number, the operator does not own that relationship, and no system bought later can take it back. Starting on company-owned accounts in a shared workspace costs almost nothing on day one and a great deal on day 300.

A pre-launch checklist for the people layer:

1. List every role that will talk to players or partners: support, VIP, affiliate management, payments escalation.
2. Decide per role whether the account is shared (one identity, several people) or private (one person, company-owned).
3. Write a first-reply target per role and per player tier, and decide how it will be measured. Entergram's analytics show response times and busiest hours and days per account, and the raw data is downloadable.
4. Add the exclusion and limit flags to every player chat, sourced from compliance, and make every outbound send filter on them by default.
5. Decide what happens to an account on the day its holder leaves, before anyone is hired.

What is the first step in starting an online casino?
Choosing the markets you will serve and the licence that covers them. Every later decision, from payments to marketing rules, depends on the licence conditions. Speak to a gambling lawyer and the relevant regulator before committing money to a platform.

How is starting a sportsbook different from opening an online casino?
The licence route is often similar, but a sportsbook adds odds and data feeds, a trading and risk function, and in-play operations. Support load also follows the sports calendar, so the people layer needs cover planned around events.

Can I launch under a white label and move to my own licence later?
Some operators do, but whether it is allowed and how the migration works depends on the regulator and the provider's contract. Ask both before signing, and check who owns the player data and the player relationships if you leave.

How much does it cost to start an online casino?
It depends on the jurisdiction, platform model, supplier contracts and team. Licence fees are published by each regulator, so take them from the regulator's own pages rather than from a guide, including this one.

Do we need a CRM before launch?
You need the player CRM chosen alongside the platform, the affiliate platform live before the first partner sends traffic, and the conversation layer decided before the first host or support agent starts using their own phone.

Does Entergram connect to casino platforms or player CRMs?
No. Its shipped integrations are HubSpot, Zendesk, Notion, Make.com and Slack. Flags and fields can be carried onto Telegram chats through HubSpot or Notion field sync, the Make.com app, or a list import.

If your licence application is underway, add one line to the launch plan: who owns the Telegram accounts your support, VIP and affiliate teams will use, and where those accounts will live. Write down the answer before the first hire, and put the exclusion flag on the list next to it. The platform will be chosen by a procurement process; the people layer will be chosen by default unless someone decides it.