GUIDES · BETSLIP DOCTOR
What should I include when asking support about a missing community alert?
Include the kind of activity you expected, the relevant club or discussion context, the approximate date and time with time zone, and what you actually observed. Say whether the in-app community inbox loaded or showed an error, and include device or app details only when appropriate for the support channel. Do not send passwords, sign-in codes, secret URL values, internal account identifiers, or the private body of a club reply. A concise report helps investigation but does not promise that the alert can be recovered.
For BSD members asking for help because an expected community alert is missing · Updated
Identify the activity without copying private content
Say whether you expected a reply or like notification and name the club or discussion in general terms. If an item title was visible, describe the generic title and the approximate time you noticed it missing. You do not need to paste a private reply or expose an internal record ID to explain the issue.
- Expected activity type and club context.
- Approximate time and time zone.
- What happened in the inbox, including any visible error wording.
Add device context only when it is useful and safe
A device model, operating-system version, or app version can help reproduce a display issue when the support channel requests it. Share only the details needed for that investigation, through an appropriate channel. Do not include session tokens, credentials, one-time codes, or private notification content.
Report the alert separately from the source action
If you can access the club discussion, note whether the source activity is present. A missing alert does not establish whether the underlying reply or like happened, so keep those observations separate. This report context supports investigation; it does not imply a particular BSD support workflow or response time.
Hypothetical example: a privacy-safe report
A fictional member might write: “I expected an in-app alert for a reply in the Cedar Club discussion around 10 a.m. Pacific on Monday. The inbox showed a message that the activity was unavailable or could not be checked on iOS. I checked the discussion and can still open the source.” They omit the reply text, credentials, and any private URL values.
Related questions
Should I attach the private reply or a screenshot of its contents?
Do not send private club content unless the intended recipient is authorized and the channel is appropriate. A summary of the activity type, time, and observed error is usually enough to describe the issue.
Should I include a login code or notification link token?
No. Never send passwords, sign-in codes, session values, or secret URL parameters in a support report.