Android SMS Gateway Scenario 1439: Marketplaces contact lists in practice

Summary

Marketplace contact lists in scenario 1439 are used-auto VIN holds: a listing needs a VIN packet, SMS with listing last-four and hold code, portal for the VIN. 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, authenticity serial-photo, handmade-policy, brand-takedown, hazmat UN, or live-animal permits, this list is a vehicle packet, not a wildlife permit.

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 VIN in SMS is a vehicle identifier you leaked. Send listing last-four. Keep the VIN in trust.

Key takeaways

• Used-auto lists are catalog ops: listing last-four and hold code — not a VIN in SMS.
• Union the seller mute sheet with the VIN-hold list before the daily drop.
• Keep login OTP off the tablet that dumps VIN-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 put the VIN 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 NHTSA VIN notes where they apply.

Context

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

Core scenario guidance

Union mute with VIN hold. Template: listing last-four + hold code. VIN 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 VIN queues.

Security and compliance

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

Decision guide

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

Checklist

• Mute ∪ VIN hold.
• No VIN in SMS.
• Listing last-four.
• 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

Mute union before radio is non-negotiable. A hold-only send still nags muted sellers. Battery exemptions dominate overnight VIN 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.