Key Takeaways
- Rain-check webhooks are SKU last-four and pickup window — never a register override code in SMS.
- Verify signatures before the SIM fires. A replayed raincheck.ready is a second nag.
- Keep checkout OTP off the CX tablet that dumps rain-check bursts.
- Service pricing is devices plus SMS send volume. You bring the Android phone and operator credit.
- Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year.
- Honor STOP. Rain-check nags are promotional even when the ticket looks transactional.
Summary
Ecommerce webhooks in scenario 1309 are rain checks: raincheck.ready fires, SMS with SKU last-four and a pickup window, portal for the override. Unlike order.paid, restock, refund, subscription, gift-card, BOPIS, split-shipment, RMA, COD, preorder, price-match, remaining-line, warranty, loyalty expiry, backorder, invoice.corrected, donation receipt, wishlist.in_stock, try-on kit_due, sample-sale hold_expiring, or dropship.ack_late, this event is a ticket clock, not a vendor ack.
Service pricing is devices plus SMS send volume. You bring the Android phone and operator SMS credit. Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year. Starter, Professional, and Business list Unlimited SMS as platform send volume; devices and airtime stay metered.
A register override in SMS is a till token you leaked. Send SKU last-four. Keep the code in the account. Honor STOP.
Key takeaways
- Rain-check webhooks are SKU last-four and pickup window — never a register override code in SMS.
- Verify signatures before the SIM fires. A replayed raincheck.ready is a second nag.
- Keep checkout OTP off the CX tablet that dumps rain-check bursts.
- Service pricing is devices plus SMS send volume. You bring the Android phone and operator credit.
- Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year.
- Honor STOP. Rain-check nags are promotional even when the ticket looks transactional.
Related reading
Start from two-way SMS inbox, compare device and SMS volume pricing, open transactional SMS, and review FTC advertising notes where they apply.
Context
CX desks land here after a replayed raincheck.ready double-nagged a shopper, or after an override leaked in a “helpful” template. Checkout OTP cannot share that tablet.
Core scenario guidance
Verify signatures. Template: SKU last-four + window. Drop override codes. Honor STOP. Isolate OTP.
| Lane | SMS body | Fail closed |
|---|---|---|
| raincheck.ready | Last-four + window | Register override |
| Replay | Same ticket id | Second nag |
| STOP | Suppress ticket nags | Keep checkout OTP |
| Checkout OTP | Separate device | Same SIM as ticket burst |
Canary a staff ticket after OS updates. MCP wraps REST. Developer Center owns fields.
Cost and ownership
Devices + volume + operator airtime on every retry. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not a rain-check desk.
Operations
Daily last-seen, battery, duplicate ticket ids. After a webhook secret rotate, one staff canary. On-call before unattended pickup cutoffs.
Security and compliance
Ticket SMS reveal what is reserved. Encrypt at rest. Never log override codes. Verify TLS on every callback.
Decision guide
Ship when signatures, last-four templates, STOP, and OTP isolation exist. Delay if a replay can double-nag. If zero phone ops is mandatory, evaluate CPaaS for that slice.
Checklist
- Verify signatures.
- No override in SMS.
- Honor STOP.
- OTP isolated.
- Spare paired.
Next steps
Return to Laravel SMS gateway guide, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.
Deep dive: production hardening
Signature checks before radio are non-negotiable. Replayed raincheck.ready still spends airtime. Battery exemptions dominate overnight pickup windows.
Deep dive: scaling and failure modes
Scale is tickets times pickup hours, not a blast of the catalog. Never claim unlimited free cloud SMS credits with no device or volume meter.
Deep dive: integration discipline
Developer Center owns live API parameters. Persist ticket id. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS webhook integrationInbound and status events
- transactional SMS for orders and alertsEvent-driven messages
- SMS API documentationLive endpoint reference
- PHP REST send samplesPHP code examples
