iGaming CRM: adding the phone channel to your stack

Ask five retention managers what their iGaming CRM is and you'll get five answers: an iGaming-specific platform, a general journey tool such as Customer.io or Braze, a module inside the player account platform, an in-house data warehouse with a sender bolted on, or some mix of all four. They're all right. What matters is less the logo than whether the pipeline does four jobs well.

The four jobs of an iGaming CRM

1. One record per player. Registration data, deposits and withdrawals, sessions, game and sport preferences, bonus history, support contacts and safer-gambling flags, in one place. Blask's overview of iGaming CRM lists much the same set and adds that the data comes from the player account platform, the game servers and the payment gateway (Blask, iGaming CRM).

2. Segments. Recency, frequency and value, plus lifecycle stage: registered but never deposited, active, lapsing, dormant, VIP. Value isn't spread evenly. In a study of 139,152 British online accounts, the top 20% of gaming accounts by amount staked generated just over 90% of operator revenue (NatCen, Patterns of Play). The same study tied that concentration to heavier losses, so the segments that matter most commercially are also the ones that need the most care.

3. Journeys. Triggered sequences: welcome, first deposit, lapse, win-back, birthday, VIP milestone. Each step is a message in a channel, a wait, or a branch on what the player did.

4. Suppression. Before any message goes out: is this player self-excluded, opted out of this channel, opted out of this product, flagged for harm, or under a cool-off? This is the job that general CRM buyers don't think about and gambling regulators think about most.

Suppression is the core feature

In Great Britain, three licence rules shape every send:

Other markets add their own layers. Malta's Player Protection Directive lists "communication-based indicators such as increased player complaints and bonus requests" among the markers of harm a licensee must monitor (MGA, Article 17A), which means your CRM's own contact history is part of the harm picture. National registers differ by country; the self-exclusion registers by country page sets out each one.

The practical consequence: suppression has to sit upstream of every channel, as one list that every sender checks. If email reads one opt-out table and the phone team reads another, a player who self-excluded on Tuesday can still get a call on Thursday. That's the failure regulators fine.

Where phone usually lives, and why that's a problem

Look at the channel list on most iGaming CRM pages and you'll see email, SMS, push, on-site messages and sometimes WhatsApp or Telegram. Phone calls are rarely a channel the CRM controls. Track360's reactivation playbook rates outbound calling by a VIP host as a high-cost channel because of the human time involved, and reserves it for top-tier lapsed VIPs (Track360).

So phone ends up outside the pipeline. A VIP host exports a list, works through it on their own phone, and types notes into a spreadsheet or a support tool. Three things go wrong:

• Suppression drifts. The export was clean on Monday. By Thursday, two players on it have self-excluded and one has opted out of calls.
• Outcomes don't flow back. The player told the host they'd deposit at the weekend. The CRM doesn't know, so on Saturday morning it sends a win-back email with a bigger bonus.
• Nothing is measured. You can't compare phone against SMS for a segment if phone outcomes never reach the place where the comparison happens.

The cost argument for keeping phone small has also changed. An AI voice agent bills for talk time, not for an agent's shift, so a call that nobody answers costs a few cents rather than a slice of someone's hour. That brings mid-value segments, not just VIPs, into range for a call.

Adding phone as a journey step

The cleanest design treats a call exactly like an email step: the journey decides when, the channel does the work, and the result comes back as data.

Out of the CRM: a webhook. Each Dial Milo campaign has a secret "start a call" URL. Your journey POSTs one player, or up to 500, with their number and context:

{
  "phone": "+447700900123",
  "name": "James",
  "player_id": "123",
  "external_id": "evt-1",
  "language": "en",
  "offer_code": "FS50",
  "at": "2026-10-28T18:00:00Z",
  "context": { "segment": "lapsed 30d", "favourite_game": "blackjack" }
}

external_id makes the request idempotent, so a re-fired journey doesn't call the player twice. at schedules the call for later. Numbers on the opt-out or safer-gambling exclusion list are rejected automatically, which gives you a second suppression check after your own. The call then waits for the campaign's calling hours in the player's local time, its contact cooldown and its budget.

How you send that request depends on the tool:

• Customer.io has a webhook action in any journey, with a JSON body you personalise from person attributes, an X-CIO-Idempotency-Key header, and retries on timeouts and 5xx errors (Customer.io docs). It points straight at the campaign URL.
• Braze, HubSpot workflows or an in-house system can do the same with their own webhook steps.
• Optimove is the one to check carefully. For triggered campaigns, its webhook carries the customer details. For scheduled campaigns, it sends only a notification, and your service then calls Optimove's API to fetch the customer list (Optimove developer docs). That second case needs a small piece of middleware between Optimove and the calling service.

Back into the CRM: attributes and events. With Customer.io, Dial Milo writes the result to the person after every call (milo_last_call_at, milo_last_call_status, milo_last_outcome, milo_last_campaign, milo_last_script, milo_callback_at, milo_opted_out_calls, milo_safer_gambling_flag) and fires events your journey branches on: milo_call_completed, milo_offer_accepted, milo_offer_declined, milo_callback_requested, milo_opted_out and milo_wrong_person. With other tools, you build the write-back from the same outcomes.

The full setup, step by step, is in the Customer.io phone calls guide.

The fields your CRM needs for phone

Before you add a phone step, check that the player record can hold these:

The last three are the ones teams forget, and they're the ones that matter when something goes wrong.

A worked journey: registered, no deposit

This is the chain we use as the reference case. Every figure is illustrative.

1. 1

   Welcome pack

   A player registers. Your CRM sends the usual welcome email and push.

2. 2

   Wait 48 hours for a first deposit

   If they deposit, they leave this journey. If they log in but don't deposit, they move to the next step.

3. 3

   Webhook to the calling campaign

   The journey POSTs the player with language and offer_code. Suppression has already run in the CRM; the calling service checks its own exclusion list again.

4. 4

   The call

   Milo calls in the player's language during their local calling hours, says it's an AI, confirms it's speaking to the right person before naming the brand, checks in and offers the welcome bonus with its main condition.

5. 5

   Branch on the outcome

   milo_offer_accepted sends the SMS and email with the code and full terms. milo_callback_requested waits until milo_callback_at. milo_opted_out suppresses phone everywhere. milo_safer_gambling_flag stops all marketing and alerts your team.

6. 6

   One reminder

   If there's no deposit 72 hours after an acceptance, one reminder. Then stop.

Say 1,000 players a month reach step three. If 35% answer and 10% of those accept, the call step produces 35 acceptances. You'd then compare first deposits for those players against a holdout group that got the same journey without the call. Blask lists incremental impact against a holdout among the core CRM KPIs, and it's the only honest way to credit a phone step with anything. The registered no-deposit players guide goes deeper on this segment.

Choosing between an iGaming CRM and a general journey tool

Neither choice is wrong. If you already run a general tool well, adding gambling-specific suppression is a few days of careful work. If you run an iGaming CRM, check how it hands a single player to an outside channel in real time, because that's what a phone step needs.

Measuring what each channel contributes

Two habits make the phone channel comparable with the rest:

• Use the same success metric. For reactivation, that's deposits or net revenue from contacted players against a holdout, not acceptances. Players say yes on a call to be polite. The player LTV calculator helps put a value on one retained player so you know what a contact is worth.
• Read the calls, not just the counts. Dial Milo's AI campaign report labels every player with a next step (likely to deposit, move to VIP support, follow up later, stop contacting, safer gambling) and summarises what players pushed back on. That's qualitative data your email channel can't give you.

Costs are easy to model because they're per minute. Outbound with Dial Milo is the phone line, priced for the exact number dialled and your caller ID country and billed per started minute, plus 9.57¢ per minute of AI talk time. For a UK mobile from a UK number the line starts at 8.5¢, so roughly 18¢ a minute all in. Calls that don't connect have no minute charge. Check any route on the rates page.

A checklist before you switch the phone step on

• One suppression list, read by every channel, updated within your licence deadlines.
• Phone consent stored per product, separately from email and SMS.
• Phone numbers normalised to international format.
• Calling hours and a contact cooldown across campaigns, so a player can't be called by three campaigns in one week.
• Outcome write-back tested end to end: accept, decline, callback, opt-out, wrong person, safer-gambling flag.
• A plan for players who call the number back hours later, which happens more than teams expect.
• A holdout group.

If you'd like to hear what the call step sounds like before building anything, the browser demo lets Milo call you. Accounts are pay as you go from a $10 top-up: create one here. For where phone fits across the whole reactivation programme, start with the player reactivation guide.