Android SMS Gateway Scenario 2039: Marketplaces contact lists in practice

Summary

Marketplace lists in scenario 2039 are musical-instrument serial holds: mute seller outreach until the serial last-four matches the heel-stamp photo. Unlike mute union, KYC, dispute, locker-ready, seller ban, payout holds, holiday cutoff, listing hold, review-request, inbound dock, IP takedown, serial-returner, VAT hold, vacation mode, MAP floor, gray-import, late-ship strike, age-gated, authenticity serial-photo, handmade-policy, brand-takedown, hazmat UN, live-animal, used-auto VIN, Rx/OTC, sports-card grading, wine DTC ship-to, phytosanitary lots, ticket-resale barcodes, bullion assay, PO-box ship-to, software-license SKU, or used-book ISBN, this list is a heel stamp, not a copyright page.

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 full instrument serial in SMS is theft bait. Send last-four. Keep the serial on the listing. Mute until the heel stamp matches.

Key takeaways

• Instrument serial holds mute seller outreach until serial last-four matches the heel-stamp photo.
• Never SMS the full serial. Last-four plus portal. A full serial is theft bait.
• Keep buyer OTP off the tablet that dumps hold-only 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 on re-list nags. SMS is not a serial registry.

Related reading

Start from contacts, lists, and segments, compare device and SMS volume pricing, open SMS auto-reply and STOP keywords, and review FTC stolen-goods notes where they apply — SMS is not a serial registry.

Context

Trust desks land here after a hold-only send nagged a seller whose heel stamp still failed OCR, or after a full serial leaked in a “helpful” template. Buyer OTP cannot share that tablet.

Core scenario guidance

Union mute before radio. Template: serial last-four + portal. Drop full serials. Honor STOP. Isolate OTP.

Canary a staff listing after OS updates. MCP wraps REST. Developer Center owns fields.

Cost and ownership

Devices + volume + operator airtime on every hold-only send. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not an instrument desk.

Operations

Daily last-seen, battery, mute-union diffs. After an OCR change, one staff canary. On-call before unattended term cutoffs.

Security and compliance

Serials identify instruments. Encrypt at rest. Never log full serials from SMS. Verify TLS on every callback.

Decision guide

Ship when mute union, last-four templates, STOP, and OTP isolation exist. Delay if a mismatch can still nag. If zero phone ops is mandatory, evaluate CPaaS for that slice.

Checklist

• Mute until serial match.
• No full serial 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

Mute union before radio is non-negotiable. A mismatch still spends airtime if you nag. Battery exemptions dominate overnight hold windows.

Deep dive: scaling and failure modes

Scale is listings times holds, not a blast of the book. Never claim unlimited free cloud SMS credits with no device or volume meter.

Deep dive: integration discipline

Developer Center owns live API parameters. Persist listing id + serial last-four. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.