11Tiger customer care
Channels, response windows, escalation, case notes — what to expect when something is broken and how to file the strongest ticket.
A customer-care guide written for the reader rather than the platform. The desk walks through the channels, the typical response windows, the escalation route and the case-note format that produces the strongest ticket.
Channels and what to use each for
Most platforms expose four channels: an in-app help centre, an in-app chat, an email support channel and a phone helpline. Each serves a different question. Help centre is for known-issue questions the platform has already documented. In-app chat is for live contests where waiting on email would miss the deadline. Email is for KYC, withdrawal and account-state questions where a paper trail matters. Phone is for locked-account emergencies where the reader cannot log in to file the chat.
The desk recommends matching the channel to the question. A reader who writes a withdrawal question into a chat window spends the median time-to-first-reply waiting on an agent who cannot action it.
Response windows the desk measures
Case-note format the desk uses
Stronger tickets produce faster, more accurate replies. The desk files tickets in a four-line case-note format: a one-line summary, the affected order or reference number, the URL or screen affected, and the expected resolution. Each of those four lines is the minimum the platform’s first-line support needs to action the ticket.
The format is not magic. It is the same case-note format the desk uses internally for its own verification trails, and the same format the platform’s second-line support reads. A reader’s ticket that arrives in that format is rarely misunderstood on the first pass.
Escalation ladder
Three rungs. First-line support handles the in-app chat, the help centre answers and the email-queue triage. Second-line support handles KYC, withdrawal, account-state and locked-account cases. Compliance handles refunds, disputes and any case where the reader and the platform disagree on the terms.
Where a first-line ticket is bounced, the reader’s strongest move is to escalate on the same ticket rather than opening a new one. The escalation carries the original case notes and the platform’s first-line response.
Two habits that shape replies
🪪 Reference number first
Lead the ticket with the reference number. The reference is the only signal that ties this ticket to a previous one the platform has on file.
📷 Screenshot of the error
A clear screenshot of the error or the affected screen removes a round-trip where the platform asks the reader to describe the error.
⏰ Time-stamped journal
A short time-stamped journal of what the reader did before the issue surfaced. The platform can often re-create the issue from the journal alone.
🧘 Calm re-state at the end
A calm one-line re-state of what the reader expects closes the ticket well. A frustrated re-state reduces the chance of a useful reply.
Frequently asked questions
How long does email support usually take?
A median of 30 hours across the desk’s last 30 tests. KYC and withdrawal cases can run to 48 hours during peak periods.
What if I cannot log in to file the chat?
Use the phone helpline for locked-account emergencies. The phone team files an in-account ticket on the reader’s behalf.
Where do I escalate a disputed refund?
Second-line support handles refunds and disputes. Where the second-line ticket is unresolved, the consumer may approach the appropriate consumer-dispute forum named on the platform’s terms page.
Does the desk publish a public-channel response?
Yes. The desk publishes test transcripts on the contact page and announces score changes on the news desk when the median shifts materially.
What about responsible-play escalations?
Responsible-play escalations route to the platform’s compliance team. The desk publishes the responsible-play page with the published escalation contacts.
Continue reading
Reading checklist
A working checklist for the reader who lands on this page to file a support ticket. The case-note format is what produces the strongest tickets; the checklist is a quick way to confirm the ticket is in the right state before submission.
Three questions to ask before filing. Is the question best suited to in-app chat, email or phone? Is the reference number ready to lead the ticket? Is the screenshot of the error captured in clear daylight, with edges visible?
What the desk does well. The response windows are published per channel as medians from the desk’s last 30 tests. The escalation ladder is a three-rung structure the reader can re-walk. The two-tone notes section names the habits that shape replies.
What the desk is still working on. A reader-side worksheet for the case-note format. A public table of the actual response times the desk has measured on a partner-by-partner basis.
A reading cadence the desk recommends. Read the channels-and-response-windows section once before filing the first support ticket. Re-read whenever a new channel is added to the partner brand’s menu.
Desk note: the case-note format in detail
The case-note format the desk recommends is a four-line structure. A one-line summary. The affected order or reference number. The URL or screen affected. The expected resolution. The format is the minimum the platform’s first-line support needs to action the ticket without a round-trip.
The one-line summary is the most important. A summary that names the question in the language the platform uses — “KYC review pending on PAN” rather than “my account is broken” — gets routed to the right agent on the first pass.
The reference number is the second-most important. A reader who has the reference number is tied to the ticket the platform has on file; a reader who does not is asking the platform to start from scratch. The reference number is usually issued by the platform on submission; the reader should capture it immediately.
The URL or screen affected is the third-most important. A reader who has the URL or the screen capture is one round-trip closer to a resolution. The reader’s screenshots should be clear, with edges visible, and saved at a resolution that does not blur the error text.
The expected resolution closes the ticket well. A calm, named resolution — “deposit released to bank within 24 hours” rather than “fix my money” — sets the platform’s first-line agent up to deliver.
Limits of the customer-care guide
The customer-care guide on this page describes the desk’s working note, not a guarantee. The channel-choice discipline and the case-note format are the desk’s recommendations; the partner brand’s own published support channel is the authoritative source.
The desk does not have visibility into the reader’s ticket queue. The response-window table is grounded in the desk’s last 30 tests; a reader’s experience on a specific ticket may differ from the published median.
The desk does not act as the reader’s support proxy. Where a ticket has stalled, the reader’s strongest move is to escalate on the same ticket rather than opening a new one; the escalation carries the original case notes and the platform’s first-line response.
Caveats on the customer-care guide
Three caveats the desk publishes on the customer-care page. The channels-and-response-windows table is the desk’s working note; a reader’s experience on a specific ticket may differ from the published median.
The second caveat: the escalation ladder is the desk’s working note, not the partner brand’s published escalation policy. The partner brand’s own escalation policy is the authoritative source.
The third caveat: the desk does not act as the reader’s support proxy. The case-note format is the desk’s recommendation, not the partner brand’s published format.
A reader who has found a partner-brand-controlled behaviour the desk has not named is welcome to send the corrections email; the next customer-care-page refresh reflects the new caveat.
Closing note from the desk
The customer-care desk closes its read with a note on the channels-and-response-windows table. The table is grounded in tests the desk files in the open; the table is updated whenever the median shifts by more than a stated margin and the change is announced on the news desk.
The three rungs of the escalation ladder are first-line support, second-line support and compliance. Each rung has a stated purpose; the desk publishes the ladder on this page rather than on the partner brand’s own published escalation policy.
The case-note format the desk recommends is a four-line structure. A one-line summary. The affected order or reference number. The URL or screen affected. The expected resolution. A reader who files a ticket in this format is rarely misunderstood on the first pass.
The two habits that shape replies are reference-number-first and screenshot-of-the-error. A reader who leads the ticket with the reference number and attaches a clear screenshot of the error removes a round-trip where the platform asks the reader to describe the issue.
The desk’s coverage area is published on the about page. A reader who wants a different area of coverage is welcome to send a corrections email with a proposed coverage-area addition.