Today / Customer care
frumzi customer care

C1frumzi customer care, in writing

frumzi customer care runs by email. The desk responds within a week, and the most common questions are answered on the contact and the responsible play pages.

Editorial photograph for /customer-care/
Editorial photograph for /customer-care/

How to reach the desk

The frumzi desk reads and replies to email at [email protected]. The desk responds within a week, usually within two business days. The desk does not have a phone line, and the desk does not have a live chat.

The desk is for editorial tips, usability notes, corrections, and questions about the site. The desk is not for platform support, KYC help, withdrawal issues, or bonus questions; those go to the platform's own customer support.

What the desk can help with

The desk can help with: a house rule that has changed on a platform, a usability shift that affects the reader, a correction to a published page, a tip on a helpline update, a question about a format or a rule, a suggestion for a new page or a new section.

What the desk cannot help with

The desk cannot help with: a KYC review that is stuck, a withdrawal that is delayed, a bonus that is not credited, a table that is not loading, a device that is not connecting, an account that is locked. The reader who needs help with any of these should contact the platform's own customer support.

What to include in the email

A useful email includes: the reader's name (or a pseudonym), the page the reader is reading, the question or the tip, and (if it is a correction) the URL of the page and the paragraph the reader is referring to. The desk does not need the reader's phone number, PAN, or bank account details, and the desk will not ask for them.

What the desk will not publish

The desk will not publish the reader's name, email, phone number, PAN, or bank account details. The desk will not publish screenshots of the reader's account. The desk will not publish the reader's winning or losing numbers. The desk is an editorial desk, and the desk publishes what the reader has read, not who the reader is.

What to read next

The contact page has the same email and the same response window, with a short form for the reader who prefers a form. The about page has the desk's editorial standards, with the colophon and the second-editor check.

A next read

The contact page has the form

The contact page has the same email and the same response window, with a short form for the reader who prefers a form.

The desk and the platform

When to write to the desk, and when to write to the platform

A short read on the two support channels, because the channels are different and the difference is the reader's job to understand.

When to write to the desk

The reader should write to the desk for editorial tips, usability notes, corrections, and questions about the site. The desk is not a customer support channel; the desk is an editorial channel. The desk reads the field, and the desk responds to the reader's notes on the field.

When to write to the platform

The reader should write to the platform for KYC help, withdrawal issues, bonus questions, account access, and any other account-related matter. The platform is the entity that runs the games, accepts the deposits, and pays the winnings. The platform is the entity that can resolve the reader's account issue.

The desk and the response window

Why the response window is a week, and what the reader can do if the window is too long

A short read on the response window, because the window is the part of the desk the reader should know about.

Why a week

The desk is two editors, and the desk reads and responds to every email within a week. The week is the time the desk needs to read the email, verify the email against the platform's records, and write a response. A shorter window would force the desk to skip the verification, and the desk will not skip the verification.

What the reader can do if the window is too long

The reader who needs a faster response can post the question on the contact page, and the desk will respond on the contact page within the same window. The reader who needs an immediate response should contact the platform's customer support, not the desk. The desk is an editorial channel, and the editorial channel is not a customer support channel.

A short list

Five things the desk can help with, in one paragraph each

A short list, because the list is the part of the desk the reader can use.

Help 01: a house rule that has changed

The reader has read a house rule that has changed on a platform. The desk can verify the change, write it up, and add it to the rule log. The change is the part of the desk the reader can use, and the use is the part of the publication the reader can contribute to.

Help 02: a usability shift on a platform

The reader has noticed a usability shift on a platform. The desk can verify the shift, write it up, and add it to the newsroom feed. The shift is the part of the desk the reader can use, and the use is the part of the publication the reader can contribute to.

Help 03: a correction to a published page

The reader has noticed a correction to a published page. The desk can verify the correction, edit the page, and note the correction in the colophon. The correction is the part of the desk the reader can use, and the use is the part of the publication the reader can contribute to.

Help 04: a tip on a helpline update

The reader has noticed a helpline update (a new line, a new service, a new operating hour). The desk can verify the update, write it up, and add it to the responsible play page. The update is the part of the desk the reader can use, and the use is the part of the publication the reader can contribute to.

Help 05: a question about a format or a rule

The reader has a question about a format or a rule. The desk can read the question, verify the answer against the platform's help centre, and reply within a week. The question is the part of the desk the reader can use, and the use is the part of the publication the reader can contribute to.

A quick reference
Editorial photograph supporting the read pan>

The reading desk, on a single card

A short reference card for the reader who wants the format comparison at a glance, with the three measures the desk uses across every format and every review.

frumzi reading desk

The reading room is a single, direct read for adult rummy players. Three measures on every review (lobby and table finding, cashier and verification, responsible-play controls). Five format notes (points, pool, deals, 13-card, 201). Three strategy disciplines (pure sequence first, track the open joker, drop when the math is wrong). Two lines that exist outside any platform (the Government of India helpline, the iCare Centre). One play action, in the header, in the mobile drawer, in the mobile sticky bar. The reading desk is the part of the publication the reader can use to read the rummy field with a calm eye.

Editorial photograph supporting the read
Editorial photograph of a quiet support desk (figure 2)
A reference

Editorial photograph of a quiet support desk (figure 2). Supporting the read above.

A second beat

What the support inbox is not

The support inbox is not a promo inbox. A reader who sends a promo question to support is a reader who has read the wrong page. A promo question is a deposit-page question, and a deposit page is a separate page. The support inbox reads account questions, verification questions, and responsible-play questions. The inbox does not read promo questions.

The support inbox is also not a verification inbox. A reader who uploads a PAN to support is a reader who has read the wrong page; the document verification is the KYC flow at the cashier. The support inbox reads account questions and route questions.

For the boundary reading, the customer-care shelf points to the /promo-code/ editorial explanation and the KYC reading on the safety hub.

A third beat

Why the support inbox is the right route for some questions

The support inbox is the right route for account questions, verification questions, and responsible-play questions. A reader who has a question about a stuck withdrawal, a missing KYC upload, or a deposit cap is a reader who should write to support. The inbox reads the three question types, and the inbox responds on a working-day schedule.

A reader who has a promo question is a reader who should not write to support; a promo question is a deposit-page question, and a deposit page is a separate page. A reader who has a strategy question is a reader who should read the strategy shelf, not the support inbox. The two routes are different, and the routes live on different pages.

For the route-map reading, the customer-care shelf points to the /promo-code/ editorial explanation and the strategy hub. The two hubs carry the promo stance and the strategy disciplines.

PLAY NOW