Android SMS Gateway Scenario 1199: Marketplaces contact lists in practice

Summary

Marketplace contact lists in scenario 1199 are handmade-versus-dropship policy holds: a listing needs a maker packet, SMS with listing last-four and hold code, portal for the packet. 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 category, or authenticity serial-photo, this list is a maker-policy packet, not a luxury serial.

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 supplier invoice in SMS is a vendor you leaked. Send listing last-four. Keep the maker packet in trust.

Key takeaways

• Handmade-policy lists are catalog ops: listing last-four and hold code — not a supplier invoice in SMS.
• Union the seller mute sheet with the handmade-policy hold list before the daily drop.
• Keep login OTP off the tablet that dumps policy-hold notices.
• 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.
• Never describe the dropship SKU in an unauthenticated SMS.

Related reading

Start from contacts, lists, and segments, compare device and SMS volume pricing, open two-way SMS inbox, and review FTC marketplace notes where they apply.

Context

Trust desks land here after a muted seller still got a policy nag, or after an invoice leaked in a “helpful” template. Login OTP cannot share that tablet.

Core scenario guidance

Union mute with handmade-policy hold. Template: listing last-four + hold code. Invoice in portal. Isolate OTP.

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

Operations

Daily last-seen, battery, duplicate listing ids. After mute refresh, one staff canary. On-call before unattended policy queues.

Security and compliance

Hold SMS reveal inventory. Encrypt at rest. Never log invoices. Verify TLS on every callback.

Decision guide

Ship when mute union, last-four templates, and OTP isolation exist. Delay if an invoice can leak in SMS. If zero phone ops is mandatory, evaluate CPaaS for that slice.

Checklist

• Mute ∪ handmade-policy hold.
• No invoice in SMS.
• Listing last-four.
• 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 hold-only send still nags muted sellers. Battery exemptions dominate overnight policy queues.

Deep dive: scaling and failure modes

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