The Casino VIP Host Playbook for Telegram: Tiers, Reply Targets, Shift Cover and Message Templates

A VIP host at an online casino usually carries somewhere between 50 and a few hundred players, and almost all of them have the host's personal Telegram account. Not a ticket portal, not a help widget: the host's own handle, given out on the first call. That is why the job works. It is also why it breaks the moment the host is asleep, on holiday, or working for a competitor.

This playbook covers how VIP desks run that book on Telegram without losing it: how to set up tiers, what reply targets to hold, how to cover shifts from the same identity, what to do on the day a host leaves, and seven message templates hosts actually reuse. It is written for the head of VIP and for hosts. It does not cover bonus design or player value models, which belong to your CRM and retention teams.

Every other decision depends on one question: whose Telegram account is the VIP talking to?

There are two answers, and both are common.

	Host's own personal account	Company-owned account the host works
Who the player thinks they are talking to	The host, personally	The host, personally (the name and photo are the host's working identity)
What happens when the host leaves	The account, the chats and the player go with the host	The account stays, a new host continues the same threads
Cover during sleep and holidays	Only if the host shares a login, which is a security problem	The retention team can reply from the same account
Typical setup	Small desks, early stage	Desks that have already lost a host and their players once

Neither is wrong, but only the second one survives a resignation. If your VIP book is worth anything, run it on company-owned accounts and say so in the host's contract. The rest of this playbook assumes that, and notes where the other model changes things.

A Telegram chat list sorts by last message. A VIP desk needs to sort by value, risk and who owns the relationship. That means fields on every player chat. Keep the list short; hosts will not fill in fifteen fields while a player is typing.

Field	Type	Why it exists
VIP tier	Single select (your tier names)	Sets the reply target and who covers
Brand	Single select	Hosts often cover several brands from different accounts
GEO / language	Single select	Routes cover to someone who speaks the language
Host	Built-in Assignee (not a custom field)	One owner per player, always
Last meaningful contact	Date	Not the last message: the last real conversation
Status	Single select: active, cooling, dormant, closed	Drives the weekly review
Self-excluded or limited	Checkbox	Keeps the chat out of every broadcast and promo, see below

In Entergram these are custom fields on the chat, so a filter like "Tier 1, brand A, no meaningful contact in 14 days" is a saved view, not a spreadsheet exercise. If you already keep the VIP list in a sheet, import it: the columns become CRM fields and each player resolves by username, or by phone number when there is no username.

The self-exclusion checkbox is not optional. Entergram does not check licences, ages or self-exclusion status, and it does not connect to your back office. Your compliance team owns that. What the CRM layer can do is make the flag visible on the chat and make it easy to leave flagged players out of every broadcast segment. Build that habit on day one, before anyone runs a promo send.

Most VIP desks have a reply target in someone's head. Write it down per tier, because it is the number that tells you whether cover works.

A starting point many desks use, to adjust to your own players:

Tier	First reply target	Out of hours
Top tier	Minutes, around the clock	Covered by the on-call host from the same account
Middle tiers	Within the hour during the player's waking hours	Next shift picks up
Entry VIP	Same day	Next shift picks up

These are targets, not industry benchmarks. The useful part is measuring against them. Entergram's analytics show messages sent and received, response times, and busiest hours and days for each connected account, and the raw data downloads. If each host works their own accounts, per-account response time is per-host response time. The response time measurement guide explains how to read those numbers without fooling yourself.

Two things this does not tell you: whether the reply was any good, and whether a slow reply cost you a player. Those still need a human review.

The 3am message is the one that matters. A player writes about a withdrawal that has been pending for two days. If nobody answers until the host wakes up, the player has already complained in a group chat by then.

The fix is not a second support account. Players who have a host do not want to start over with a stranger. The fix is that the on-call person replies from the host's account, and the player sees one continuous conversation.

How that works in practice:

1. Share the VIP accounts with the workspace. In Entergram an account can be shared with the workspace or kept private, per account. Shared VIP accounts are visible to whoever is on call.
2. Use internal comments for handover. Before the shift ends, the host leaves a note on any open chat: what the player wants, what was promised, what not to say. The player never sees comments.
3. Turn anything that needs follow-up into a ticket. A withdrawal question, a KYC document or an account issue becomes a ticket with an owner, an issue type and an SLA, linked to the chat. The next shift sees open tickets, not a scroll of messages.
4. Staff from real traffic. Read busiest hours and days per account and put cover where players actually write, which is rarely 9 to 5 in your office's time zone.

If hosts use their own personal accounts, steps 1 and 2 only work if the host shares the account with the workspace. Many will not, which is the strongest practical argument for company-owned accounts.

VIP desks lose the most money on this day. A host resigns on Friday, starts at a competitor on Monday, and by Wednesday their best players have moved too.

What protects you:

• Accounts the company owns stay with the company. The next host continues the same threads from the same identity. The player may notice a change in tone; they do not have to find a new contact.
• The CRM layer belongs to the workspace. Tickets, fields and comments stay. The new host reads the history instead of starting cold.
• Privacy controls stop the book from walking out in someone's head. Entergram can hide usernames and group member information from team members, and block editing and deleting messages. A host with inbox access does not hold a copy of the VIP list, and cannot quietly delete what they promised a player. The audit trail guide covers this in more depth.
• Slack as a second record. Entergram can relay every chat a seat can access into one Slack channel, one way, as an audit log.

What does not protect you: anything on an account the host personally owns. If it is their account, it leaves with them. No tool changes that.

A handover checklist for the day a host leaves:

1. Reassign every player chat to the incoming host or the head of VIP.
2. Ask the departing host to leave a comment on each Tier 1 chat: open promises, preferences, anything sensitive.
3. Close or reassign their open tickets.
4. Remove their seat. Shared accounts stay connected to the workspace.
5. Send the introduction template below from the same account within a day.

These are starting points. Rewrite them in your own voice and language, and run anything that mentions money, limits or offers past your compliance team. Players can tell a template from a person, so the line that matters most in each one is the one you personalise.

1. First message after the VIP call

Hi {first name}, it is {host name} from {brand}. This is my direct line, so you can write here any time about your account, payments or anything that is not working. I usually reply within {reply target}. If I am off, my colleague {cover name} answers from this chat, so you never have to explain things twice.

2. Withdrawal status, when you do not have an answer yet

Hi {first name}, I have your withdrawal from {date} in front of me. It is with the payments team now and I have asked them for an update. I will write to you here by {time} even if there is no news yet.

The promise to write back by a specific time, even without news, is what stops the 3am complaint.

3. Shift cover, when someone else replies

Hi {first name}, {cover name} here, I work with {host name} on {brand} VIP. {Host name} is offline right now and asked me to look after anything urgent. I can see your earlier messages, so no need to repeat anything.

4. Introducing a new host after someone leaves

Hi {first name}, I am {new host}, and I am looking after your account at {brand} from today. I have read through your history with {previous host}, including {one specific thing}. Same chat, same priority. Anything you need, write here.

5. Check-in after a quiet period

Hi {first name}, it has been a while since we spoke. No agenda, I just wanted to check everything with your account is working the way it should. If anything is not, tell me here.

Do not send this to a chat with the self-exclusion or limits flag. That is what the checkbox is for.

6. Closing the loop on a complaint

Hi {first name}, following up on {issue}. It is now {resolved / changed}, and here is what we changed so it does not happen again: {one line}. Thank you for raising it.

7. Responsible gambling reply, when a player asks for limits or a break

Thank you for telling me, {first name}. I have passed this to our team so your {limit / break} is set up properly, and you will get confirmation from {channel}. I will not send you any offers in the meantime.

Then tick the flag on the chat. The point of template 7 is that the host's next action is visible to everyone else on the desk.

If you send any of these to many players at once (for example the introduction after a host leaves), Entergram broadcasts personalise merge fields per recipient, send from real accounts, and can spread the send across several connected accounts with Telegram-aware pacing. Replies land back in the shared inbox against the player's record.

1. Open tickets by issue type and owner. Anything older than its SLA gets a name next to it.
2. Response time per VIP account against the tier targets you wrote down.
3. Top-tier players with no meaningful contact in 14 days. Each one gets a check-in (template 5) unless flagged.
4. Chats with the self-exclusion flag that received any outbound message. The right number is zero.

If your team uses an AI assistant, the Entergram MCP gives it the raw message events across every connected account, so it can compute first-reply coverage per tier or list top-tier chats waiting on a reply. It does the analysis over your data; it does not replace the review.

If your VIP book currently lives on hosts' phones, do two things this week: move Tier 1 players onto company-owned accounts as hosts change, and add the tier and self-exclusion fields to every player chat. Everything else in this playbook builds on those two.

The Telegram CRM for casinos page shows how the support, VIP and affiliate sides fit in one workspace, and the affiliate manager guide covers the partner side of the same desk. For deciding which players get a host at all and which stay with automated campaigns, read how to split retention between automation and people.