Android SMS Gateway Scenario 1369: Ecommerce webhooks in practice

Summary

Ecommerce webhooks in scenario 1369 are class waitlists: class.waitlist_released fires, SMS with class last-four and a window, portal for the door code. 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, dropship.ack_late, or raincheck.ready, this event is a seat clock, not a rain-check ticket.

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 studio door code in SMS is a site token you leaked. Send class last-four. Keep the code in the account. Honor STOP.

Key takeaways

• Class-waitlist webhooks are class last-four and release window — never a studio door code in SMS.
• Verify signatures before the SIM fires. A replayed class.waitlist_released is a second nag.
• Keep checkout OTP off the CX tablet that dumps waitlist 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. Waitlist nags are promotional even when the seat 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 waitlist_released double-nagged a member, or after a door code leaked in a “helpful” template. Checkout OTP cannot share that tablet.

Core scenario guidance

Verify signatures. Template: class last-four + window. Drop door codes. Honor STOP. Isolate OTP.

Canary a staff class 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 studio desk.

Operations

Daily last-seen, battery, duplicate class ids. After a webhook secret rotate, one staff canary. On-call before unattended class cutoffs.

Security and compliance

Waitlist SMS reveal who booked. Encrypt at rest. Never log door 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 door code in SMS.
• Honor STOP.
• OTP isolated.
• Spare paired.

Next steps

Return to App 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 waitlist_released still spends airtime. Battery exemptions dominate overnight class windows.

Deep dive: scaling and failure modes

Scale is classes times releases, 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 class id. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.