How LoadBounce™ collects SMS consent from shippers and consignees and delivers automated freight delivery status notifications.
This page documents the SMS opt-in Call to Action (CTA) for the LoadBounce™ Delivery Notification campaign. It describes how shippers and consignees provide phone numbers and consent during the freight shipment lifecycle, the disclosure language displayed to them, and the message types they receive. A separate page at loadbounce.ai/sms-opt-in documents the platform's Authentication (2FA) campaign.
LoadBounce™ collects SMS consent from shippers and consignees at the point they participate in a freight shipment lifecycle event on the LoadBounce™ platform. Phone numbers are entered into the LoadBounce™ shipper portal or signing flow, alongside consent disclosure language describing the delivery notification messages that will follow. SMS messages are sent exclusively for automated delivery status notifications tied to that specific shipment — pickup confirmations, signature requests, delivery receipts, and exception alerts. No marketing SMS is ever sent.
An authorized carrier user posts a load tendering a shipment, identifying the shipper and consignee parties involved.
At pickup, the driver requests a digital signature from the shipper. The shipper opens a token-gated signing page on their own device at loadbounce.ai/s/<token> and enters their mobile phone number to receive a delivery receipt and any exception alerts associated with that shipment.
Below the phone number field, an SMS consent checkbox displays the disclosure language shown in Section 3 below. The checkbox must be checked to submit the form. The checkbox is unchecked by default. Without consent, the user can still complete the signing flow, but receives no SMS — only on-page status updates and email notifications.
At delivery, the driver requests a digital signature from the consignee. The consignee opens a token-gated signing page on their own device at loadbounce.ai/r/<token> and may enter their mobile phone number to receive a delivery receipt confirmation. The same consent disclosure and checkbox shown in Section 3 applies.
LoadBounce™ sends automated delivery status SMS messages to consenting parties as each lifecycle event occurs — signature request links, delivery confirmations, and exception alerts (damage noted, refusal at delivery). Messages are scoped to the specific shipment and end when the shipment lifecycle terminates.
Recipient may reply STOP to any LoadBounce™ SMS message to opt out of all further messages. A confirmation reply is sent acknowledging the opt-out. Reply HELP for support contact information.
Below is the rendered consent UI exactly as displayed to shippers and consignees during the signing flow. The SMS consent checkbox and disclosure language appear immediately following the mobile phone number field.
| Item | Detail |
|---|---|
| Program name | LoadBounce™ Delivery Notifications |
| Sender name | LoadBounce |
| Use case | Delivery Notification — automated transactional alerts about freight shipment status |
| Message types sent | Pickup confirmation, signature request link, delivery receipt, exception alert (damage noted), exception alert (refusal at delivery) |
| Marketing SMS | ✗ Never |
| Message frequency | Approximately 1–4 messages per shipment, triggered by lifecycle events on that specific shipment |
| Msg & data rates | May apply per recipient's mobile carrier |
| Opt-in method | Explicit checkbox in shipper or consignee signing flow at loadbounce.ai/s/<token> or loadbounce.ai/r/<token> (unchecked by default). Phone number entry is optional; consent is required only if user wishes to receive SMS. |
| Opt-out method | Reply STOP to any LoadBounce™ SMS message |
| Opt-out confirmation | User receives confirmation: "You have been unsubscribed from LoadBounce SMS messages. Reply START to resubscribe." |
| Help keyword | Reply HELP — response directs to help@loadbounce.ai |
| Phone number sharing | ✗ Never shared or sold to any third party |
| Privacy policy | loadbounce.ai/privacy — Section 9b covers SMS communications |
| Terms of service | loadbounce.ai/tos — SMS & Text Messaging section covers Delivery Notifications |
| Opt-in URL | loadbounce.ai/s/<token> (shipper signing) and loadbounce.ai/r/<token> (consignee signing) |
| # | Message Template | Trigger |
|---|---|---|
| 1 | LoadBounce: Driver requests your signature for delivery of BOL #LB-04829. Sign here: https://loadbounce.ai/r/abc123 Expires in 72hr. Reply STOP to opt out. | Driver requests receiver signature at delivery |
| 2 | LoadBounce: Pickup confirmed for BOL #LB-04829. Driver en route to delivery. Track: https://loadbounce.ai/t/abc123 Reply STOP to opt out. | Shipper signs pickup; driver in transit |
| 3 | LoadBounce: Delivery signed for BOL #LB-04829 at 3:42 PM. Receipt: https://loadbounce.ai/p/abc123 Reply STOP to opt out. | Receiver signs clean delivery |
| 4 | LoadBounce: Damage noted on delivery of BOL #LB-04829. Receiver signed with exception. View: https://loadbounce.ai/p/abc123 Reply STOP to opt out. | Receiver signs delivery with damage exception |
| 5 | LoadBounce: Load #LB-04829 was REFUSED at delivery. Reason: "pallet damaged in transit". View: https://loadbounce.ai/d/abc123 Reply STOP to opt out. | Receiver refuses delivery; alert dispatched to shipper of record |
| OPT-OUT | You have been unsubscribed from LoadBounce SMS messages. You will not receive any more messages from this number. Reply START to resubscribe. | User replies STOP |
| HELP | LoadBounce: For support, visit loadbounce.ai or email help@loadbounce.ai. Reply STOP to unsubscribe. Msg & data rates may apply. | User replies HELP |