Android SMS Gateway Scenario 1969: Ecommerce webhooks in practice

Summary

Ecommerce webhooks in scenario 1969 are booking holds: appointment.hold fires, SMS with booking last-four and a hold window, portal for the PAN. 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, raincheck.ready, class.waitlist_released, subscription.pause_ending, kit.incomplete, storecredit.issued, layaway.due, trade-in.quote_ready, registry.item_purchased, curbside.ready, preauth.expiring, or digital.download_ready, this event is a slot clock, not a download key.

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 PAN in SMS is a payment credential you leaked. Send booking last-four. Keep the PAN in checkout. Honor STOP.

Key takeaways

• Appointment webhooks are booking last-four and hold window — never a card PAN in SMS.
• Verify signatures before the SIM fires. A replayed appointment.hold is a second nag.
• Keep checkout OTP off the CX tablet that dumps hold 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. Hold nags are promotional even when the slot looks transactional.

Related reading

Start from SMS webhook integration, 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 appointment.hold double-nagged a shopper, or after a PAN leaked in a “helpful” template. Checkout OTP cannot share that tablet.

Core scenario guidance

Verify signatures. Template: booking last-four + window. Drop PANs. Honor STOP. Isolate OTP.

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

Operations

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

Security and compliance

Hold SMS reveal slot value. Encrypt at rest. Never log PANs. 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 PAN in SMS.
• Honor STOP.
• OTP isolated.
• Spare paired.

Next steps

Return to Phone as 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 appointment.hold still spends airtime. Battery exemptions dominate overnight hold windows.

Deep dive: scaling and failure modes

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