Android SMS Gateway Scenario 59: Marketplaces contact lists in practice

Summary

Marketplace contact lists on an Android SMS gateway are a three-lane problem: buyers waiting on shipping, sellers waiting on payouts, and staff canaries. Scenario 59 is the week a data engineer re-exports “all users” and the promo SIM texts people who STOPped last quarter — on a number you own.

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. Do not title this Unlimited SMS. Paid SKUs can uncap platform send volume; devices still meter and the carrier still bills.

A marketplace extract without a mute column is not a list. It is a complaint generator with prepaid airtime attached.

Key takeaways

• Marketplace lists are three populations: buyers, sellers, and staff. Mute metadata must travel with the MSISDN.
• A seller “payout ready” text is operational. A weekend promo dump is not. Do not share the OTP SIM.
• Re-importing a warehouse extract without suppress is how STOP guests return on Monday.
• 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.
• Name who owns list hygiene before GMV week, not after the first complaint ticket.

Related reading

See bulk SMS from Excel and CSV, how an Android SMS gateway works, SMS API documentation, and messaging best practices.

Context

Operators and marketplace GMV teams land here after a “seller festival” blast hit buyers, or after OTP for the seller console queued behind 40,000 shipping nags. Radio reality still wins: an offline tablet in the ops cage means lists sit unsent while support tickets pile up. Consent lives in your CRM, not in last month’s spreadsheet name.

Marketplace seller alerts need multi-device failover when a single phone is the SPOF. Buyer shipping texts can share an ops SIM. Seller login OTPs cannot.

Core scenario guidance

Store role, locale, last consent timestamp, and mute reason with every number. Import is a join against suppress, not a paste into Send. Canary staff rows per role before a festival weekend.

Prefer gradual rollout with feature flags when a new category goes live. Write acceptance criteria: “zero muted numbers in the paid send log.” Developer Center owns live request shapes.

Cost and ownership

Devices + volume + operator airtime. Re-sending a dirty list burns credit twice: once outbound, once on apology. Assign who owns SIM top-ups and who signs the extract. Free (1 / 300 / 300) is a hygiene lab, not festival volume.

Starter, Professional, and Business uncap platform send volume versus Developer; they still cap devices and never include carrier SMS. Do not invent rollover “credits” we sold as prepaid packs.

Operations

Daily: pairing, battery, queue, DLR, and a count of suppressed vs attempted. After OEM updates, re-import ten staff rows end to end. Keep a spare charged device. Name an on-call owner before unattended weekend GMV.

Security and compliance

Protect API keys. Rotate after a contractor export. STOP and consent apply on promo lanes even when GMV “needs awareness.” Avoid logging full OTP bodies. Verify webhook signatures if an order event adds a number to a list automatically.

Decision guide

Ship when role columns, mute union, and fallbacks exist. Delay if you cannot explain offline-phone behavior during peak checkout. If zero phone ops is mandatory, evaluate CPaaS for that lane.

Checklist

• Role + mute columns required on import.
• OTP isolated from buyer/seller promo.
• Staff canary per role passed.
• Spare device paired.
• Airtime includes retries.
• On-call named.
• Warehouse extract cannot bypass suppress.

Next steps

Review Android SMS gateway API, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.

Deep dive: production hardening

Contact lists need consent metadata stored with the number. Marketplace seller alerts need multi-device failover when a single phone is the SPOF. Auto-reply and STOP protect promotional lanes — never auto-reply into OTP threads.

Battery exemptions and OEM killers dominate overnight list drains. Name an on-call owner before unattended schedules go live. Canary on staff numbers before customer OTP.

Document who owns SIM top-ups for multi-country seller bases. Prefer honest latency over brochure SLAs on SIM paths.

Deep dive: scaling and failure modes

Scale is more devices and cleaner lists, not a fake unlimited carrier pack. Bulk CSV import needs validation before radio send. Scheduled SMS must survive device sleep and timezone mistakes across seller regions.

Airtime surprise bills happen when loops ignore radio pace. Never claim unlimited free cloud SMS credits with no device or volume meter. Spare charged devices beat brochure SLAs.

Deep dive: integration discipline

Developer Center owns live API parameters. Ecommerce webhooks that append contacts must verify signatures before they mutate the list. If zero phone ops is mandatory, evaluate CPaaS for that lane. Cross-link Setup, Pricing, Downloads, and Developer Center.

Scenario playbooks still bill by devices and SMS send volume. You bring the Android phone and operator SMS credit.