Customer care — channels, windows, escalation

The support channels, in summary

Email support is the first check. The reader opens the operator’s own page and reads the published support email address. The published email is the source of truth; the desk has read addresses at the operator’s own domain. A support email at a free webmail domain is recorded as a red flag in the comparison ledger. The published response window for email support is also recorded; the desk has read windows ranging from 24 to 72 hours on the published flows.

Chat support is the second check. The reader opens the operator’s own page and reads the published chat channel. The published channel is the source of truth; the desk has read flows that include web chat and in-app chat. A chat channel that is not available 24/7 is recorded with the gap listed. The published response window for chat support is also recorded; the desk has read windows ranging from 2 to 10 minutes on the published flows.

Phone support is the third check. The reader opens the operator’s own page and reads the published phone number. The published number is the source of truth; the desk has read numbers at the operator’s own published entity. A phone number at a free webmail domain or at a personal mobile is recorded as a red flag in the comparison ledger. The published availability window for phone support is also recorded.

In-app support is the fourth check. The reader opens the operator’s own page and reads the published in-app support channel. The published channel is the source of truth; the desk has read flows that include an in-app chat surface, an in-app ticket surface and an in-app callback surface. A surface that demands a fee before a support ticket is opened is recorded as a red flag in the comparison ledger.

Editorial distance and the comparison ledger

The customer-care chapter is editorial guidance, not a personal recommendation. The desk reads published operator material and records the desk’s own test tickets where the operator publishes a verifiable flow. Where the operator publishes a number, a window or a document list, the desk records it; where the operator does not, the desk records the gap. The comparison ledger is a desk record, not a personal recommendation. The reader verifies the operator’s current page before relying on any figure listed in the editorial chapter.

The customer-care chapter is reviewed quarterly. The desk updates each channel when the operator publishes a change to an email address, a chat availability window, a phone availability window or an in-app support surface. The chapter’s last review date is recorded on the page footer; the reader verifies the operator’s current page before relying on the chapter’s published figures.

A support channel that is not available 24/7 is recorded with the gap listed. A support email at a free webmail domain is recorded as a red flag. A support phone number at a free webmail domain or at a personal mobile is recorded as a red flag. An in-app support surface that demands a fee before a support ticket is opened is recorded as a red flag. The comparison ledger records the red flags the desk has read against a published primary source.

Operational reference for this page

The pages on boltfantasy.com are written by the editorial desk. Each page walks through the published material on a single topic; the operator-specific UI is the source of truth and must be verified on the operator’s own published material before the reader commits a rupee. The pages are not legal or financial advice; the pages are editorial guidance on the published rules, the published drop ladder, the published chip math, the published safety surface and the published comparison dimensions. The reader verifies the operator’s current page before relying on any figure listed here.

A published number is a number the operator has published on the operator’s own page. The desk has read the published numbers on a small set of operators; the desk does not synthesise or extrapolate. Where the operator publishes a number, a window or a document list, the desk records it; where the operator does not, the desk records the gap. The reader uses the desk’s record to make their own comparison; the desk does not publish a winner.

A published window is a period the operator has published on the operator’s own page. The desk has read the published windows on a small set of operators; the desk does not synthesise or extrapolate. The reader verifies the operator’s own page before relying on any window listed in the editorial chapter. The comparison ledger records the windows the desk has read against a published primary source.

A published document list is a list the operator has published on the operator’s own page. The desk has read the published document lists on a small set of operators; the desk does not synthesise or extrapolate. The reader verifies the operator’s own page before relying on any document list listed in the editorial chapter. The comparison ledger records the document lists the desk has read against a published primary source.

A restricted-state list is a list the desk has read against a published primary source. The restricted states for real-money rummy, as of the desk’s last review (Edition 342, 06 Aug 2026), include Telangana, Andhra Pradesh, Assam, Odisha, Sikkim, Nagaland, Meghalaya and Tamil Nadu. The desk’s list is a desk record, not a legal interpretation. The reader verifies the local state gaming act before playing. A state change to the restricted list is recorded in the news register with the source date and the desk’s verification status.

A support line is a contact the desk has read against a published primary source. The desk does not operate a support line; the desk links to the published support lines operated by recognised public-health bodies. The reader is encouraged to contact a support line if the play has stopped being a leisure activity. The chapter’s last review date is recorded on the page footer.

A review cadence is the desk’s published review window. The desk reviews each chapter on a quarterly cadence. The chapter’s last review date is recorded on the page footer; the reader verifies the local rule before relying on the chapter’s published figures. A chapter that has not been reviewed in the last quarter is flagged in the chapter’s footer; the reader verifies the operator’s current page before relying on the chapter’s published figures.

A red flag is a published signal the desk has read against a primary source. The desk flags any operator that does not publish a deposit cap, a session timeout or a self-exclusion switch. The desk flags any operator that publishes a dispute window shorter than the desk’s published baseline. The desk flags any sign-in surface that does not match the operator’s published domain. The comparison ledger records the red flags the desk has read against a published primary source.

A primary source is a document the operator or regulator has published on its own page. The desk reads the primary source and records the desk’s own test ticket where the operator publishes a verifiable flow. The desk does not synthesise or extrapolate. The reader verifies the operator’s own page before relying on any figure listed in the editorial chapter.

A chapter cross-reference is the link between chapters on a single topic. The format-split chapter is referenced from the games hub, the strategy hub and the reviews hub. The drop-vs-show chapter is referenced from the strategy hub and the games hub. The dispute-handling chapter is referenced from the reviews hub and the safety hub. The reader uses the cross-references to navigate to the chapter that matches the decision they are facing. The cross-references are not commercial links; the cross-references are the desk’s own editorial navigation.

A reading order is the desk’s recommended sequence for a reader who is new to the chapter. The reader starts with the chapter’s first section, walks through the published material, and finishes with the operational reference. The reading order is not a personal recommendation; the reading order is the desk’s own editorial sequence. The reader may skip sections they are already familiar with; the reader verifies the operator’s current page before relying on any figure listed in the chapter.

A glossary entry is the desk’s published definition of a term used in the chapter. The glossary entries are linked from the chapter’s operational reference; the reader uses the glossary to look up an unfamiliar term without leaving the chapter. The glossary is not exhaustive; the glossary covers the terms the chapter uses most often. The reader uses the desk’s broader editorial chapters to look up terms the chapter does not define.