Android SMS Gateway Scenario 1739: Marketplaces contact lists in practice

Summary

Marketplace lists in scenario 1739 are ticket-resale holds: mute seller outreach until the barcode last-four matches the event hold. 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, or phytosanitary lots, this list is a barcode match, not a plant cert.

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 barcode in SMS is an entry credential you leaked. Send last-four. Keep the ticket in the listing. Mute until the hold matches.

Key takeaways

• Ticket-resale lists mute sellers until the barcode last-four matches the event hold — never a full ticket PDF in SMS.
• Union mute with STOP, vacation, and authenticity holds — one radio, not four overlapping nags.
• Keep buyer login OTP off the trust tablet that dumps barcode reminders.
• 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 even when a listing comes off hold. A re-list is still promotional unless they opted in again.

Related reading

Start from contacts, lists, and segments, compare device and SMS volume pricing, open SMS auto-reply and STOP keywords, and review FTC ticket-resale notes where they apply.

Context

Trust desks land here after a hold-only send nagged a seller whose barcode still failed the event API, or after a full barcode leaked in a “helpful” template. Buyer OTP cannot share that tablet.

Core scenario guidance

Union mute before radio. Template: barcode last-four + portal. Drop full tickets. 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 a resale desk.

Operations

Daily last-seen, battery, mute-union diffs. After an event-API change, one staff canary. On-call before unattended on-sale cutoffs.

Security and compliance

Barcodes are entry credentials. Encrypt at rest. Never log full tickets 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 barcode match.
• No full ticket in SMS.
• Honor STOP.
• OTP isolated.
• Spare paired.

Next steps

Return to Android SMS gateway API 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 hold-only send still spends airtime. Battery exemptions dominate overnight on-sale queues.

Deep dive: scaling and failure modes

Scale is listings times hold days, 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 listing id + barcode last-four. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.