Identify what stopped working
Write the last successful action and the first failing one. Was a fixture found? Did the app open? Was a charge taken? Is the problem a particular article or a full-match stream? This determines which evidence is useful.
When to use this route
You need to report a Cricbuzz problem.
What to do, in order
- Choose the failed task: match event, app, account, charge or privacy.
- Identify the exact product and provider before sharing any evidence.
- Use the corresponding publisher-linked channel and preserve the report reference.
How to recognise the result
The request reaches the responsible product with a specific problem.
If it does not resolve
- An unrelated brand’s help number cannot be assumed to handle this profile.
For the publisher and product boundary, read Cricbuzz
If the original account is Sporta’s rather than Cricbuzz, use Dream11 login
For a score correction, name the event
Include competition, full teams, date, innings, ball or player and the field in dispute. Compare the official event record where available. Preserve whether Cricbuzz showed the result as provisional or final.
When to use this route
You need a score-event correction.
What to do, in order
- Keep fixture URL, innings, delivery and observed time.
- State the disputed value and the attributable event behind your expectation.
- Send the record through the score/support route and retain its response.
How to recognise the result
One match event is identifiable and reviewable.
If it does not resolve
- A general complaint about a score without event context may not identify the error.
For Android feedback, keep the platform context
Use the feedback or publisher contact linked by the identified app. Retain installed version, system version and exact error. No response time, customer-care telephone number or individual case resolution has been verified by D1.
When to use this route
You need to report an app or notification failure.
What to do, in order
- Record platform, installed version and the first exact error.
- Identify whether acquisition, launch, alert delivery or a premium feature failed.
- Send only the relevant device and event context through publisher-linked support.
How to recognise the result
The report localises the failed stage and intended product.
If it does not resolve
- Successful installation does not prove subscription entitlement.
If the missing feature belongs to the original profile, first follow Cricbuzz account recovery
For a payment, identify merchant and product
A Plus receipt and a Willow receipt concern different products. Match the charged account and billing channel before asking about activation or renewal. Retain transaction date, amount and reference privately.
When to use this route
A charge, cancellation or refund needs investigation.
What to do, in order
- Identify merchant, product, amount, currency, time and receipt reference.
- State whether you need to stop future renewal, locate a charge or trace an existing refund.
- Use that billing channel and reconcile any resulting confirmation with the original transaction.
How to recognise the result
The specific charge or future renewal has a documented state.
If it does not resolve
- A cancelled subscription does not by itself demonstrate a completed refund.
Deleting software does not settle a privacy request
Uninstalling removes local software. Cancelling concerns future billing. Deleting a remote account or data needs the provider’s privacy process and may involve retention obligations. State the result you want and keep its acknowledgement.
When to use this route
You want an account-data or privacy action.
What to do, in order
- Identify the provider and exact request rather than only removing software.
- Use the stated privacy/account channel and supply only the required identifiers.
- Keep the acknowledgement and the provider’s stated outcome or retention explanation.
How to recognise the result
The requested remote-data action has a provider response.
If it does not resolve
- Device uninstallation does not establish remote deletion.
A compact report template
Write a short chronology: the exact record that opened, the state that later failed, its time and the unresolved correction. Include platform and version, the fixture or receipt identifier, and a redacted screenshot when it identifies that state.
When to use this route
You need a useful report for a score, app, purchase or privacy problem.
What to do, in order
- Classify the task and name the exact fixture, item or receipt affected.
- Record expected result, last successful stage and the first error with time and platform.
- Send redacted evidence through the publisher-linked route and keep one support reference.
How to recognise the result
The recipient can identify the specific record and the requested correction or account outcome.
If it does not resolve
- Do not include passwords or OTPs in an editorial report.
- D1 can correct its text, but does not administer Cricbuzz subscriptions or accounts.
If your next task is a fantasy entry rather than the score: Dream11 free-league rules
READ THE SOURCE / CHECK THE DATE
Documents & references
Dates below belong to the historical references. The writing date does not represent a new account or file test.
- Google Play India — Cricbuzz main Android app2026-11-02 · play.google.com
- Cricbuzz — Terms of Service and paid-service provisions2026-11-02 · www.cricbuzz.com
- Cricbuzz — Privacy Notice, dated 1 April 20252026-11-02 · www.cricbuzz.com
- Cricbuzz — public login options and terms acknowledgements2026-11-02 · m.cricbuzz.com
- Cricbuzz — Willow linking FAQ and USA/Canada condition2026-11-02 · m.cricbuzz.com
- Google Play India — older language package, returned 4042026-11-02 · play.google.com
More on Cricbuzz
D1 is an independent information publisher. Product providers handle their own accounts, files and transactions. How we write →