GUIDES · BETSLIP DOCTOR
Does sending a saved BSD slip to my phone place a bet?
No. An explicit phone handoff asks BSD to send a notification about the selected saved ticket to the account's registered device. It does not place a wager. The phone opens BSD for review, and you choose whether to tap through to the sportsbook. A request, notification delivery and opening the ticket are separate events.
For bettors reviewing a saved BSD slip · Updated
A request for a link is not a request for a phone alert
You can ask an authorized agent to review a saved slip or prepare its supported sportsbook handoff without asking for a phone notification. Saving a slip is also separate from sending it. BSD's tool contract requires an explicit request before the agent sets sendToPhone for that exact saved ticket.
Be specific about which slip you want sent. The phone handoff is bound to the saved ticket's identity, digest and sportsbook; it is not a blank instruction to open another account's ticket or switch the selected book. An unavailable or invalid target remains unavailable rather than becoming an invented success.
- Choose the exact owned saved slip.
- Review the same-book handoff and its limitations.
- Ask separately to send that slip to your BSD phone.
- Keep an unavailable delivery or unsupported tool result explicit.
Requested, delivered and opened mean different things
The connected tool can report the result of requesting the phone handoff. That response should not be rewritten as proof that you saw a notification. A device must be registered to the account, the connected tool must support the parameter, and notification access still matters.
Read the actual phone status instead of assuming every stage happened. A skipped, failed or unavailable result is not a delivered alert. Likewise, a request to send the slip is not evidence that the phone opened it. If you do not see the alert, use the supported link or open the saved slip in BSD; do not repeatedly generate push requests without deciding that you want another one.
The sportsbook action still belongs to you
The phone first opens BSD's review path for the saved ticket. The client checks the current account and saved-ticket binding before showing the supported review. Only a deliberate customer tap opens the sportsbook destination.
At the sportsbook, inspect what actually loaded, the available selections and the stake before making any decision. A BSD phone alert is not sportsbook confirmation, and an agent cannot place the wager for you. Link preparation, a notification request and an accepted bet must never be collapsed into the same status.
Example: ask for the alert only after reviewing the saved ticket
Imagine that you have two saved slips in a connected conversation. Select one and review its handoff first. If you then ask to send that exact slip to your BSD phone, the agent may request the supported notification and report its actual result. A requested status means the request was made; it does not show that you received or opened it. You still open BSD and decide whether to continue to the sportsbook. This example contains no real ticket, odds, customer transaction or wager outcome.
Related questions
Will saving a slip automatically send it to my phone?
No. The phone handoff requires an explicit request for that exact saved ticket. A save or a request for a link does not grant notification permission.
What if my connected tool does not support phone delivery?
Keep that limitation visible and use the supported link instead. Do not guess a sendToPhone parameter or claim that a notification was sent.