BetSlip Doctor

GUIDES · BETSLIP DOCTOR

What should I expect after declining a community message request?

When the current BSD request flow confirms a decline, the pending request ends as a recipient consent decision; it does not become an accepted conversation. The decline state is private to the recipient, so the sender should not expect a visible decline label or reason. A new request from the same pair is not a way to reopen that declined request, and unblocking does not restore consent. Use the action only when the current request view confirms it; a missing message or send error alone does not prove a decline occurred.

For Community members having consented conversations · Updated

The sender does not receive a decline label

The decline marker is private. The sender-facing view does not expose a decline field, and attempts to contact the same pair after refusal use an unavailable response rather than revealing the recipient's decision. Do not infer a specific reason from silence or a generic error.

Hypothetical example: a private refusal stays private

A recipient declines a pending request. The request does not turn into a conversation, and the sender does not see a decline label. If a later contact attempt returns a generic unavailable result, that response does not disclose the recipient's reason. This is a synthetic example, not a real exchange.

Related questions

Will the sender see that I declined?

The canonical decline state is private to the recipient and is not exposed as a decline field to the sender. A generic unavailable response should not be treated as an explanation.

Sources and further reading

Explore BSD research.

Review supported ways to use BSD.