Android SMS Gateway Scenario 119: Marketplaces contact lists in practice

Summary

Marketplace contact lists in scenario 119 are seller KYC and onboarding: document-expiry nudges, payout-hold notices, entity-name mismatches. This is not the buyer/seller promo split. It is identity traffic on an Android SIM you operate, with counsel-shaped copy and a mute set that marketing must not overwrite.

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 Unlimited SMS. Paid plans may uncap platform send volume; devices and airtime remain metered.

A KYC reminder sent from last week’s festival extract is not “re-engagement.” It is the wrong purpose on a number that already trusted you with identity.

Key takeaways

• KYC and onboarding lists are identity traffic. A festival promo extract must never join that file.
• Seller verification nudges need locale and legal entity. A buyer shipping list is the wrong join.
• Dashboard OTP stays on a dedicated device. KYC bursts will otherwise starve sign-in.
• 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.
• Store KYC purpose with the number. A warehouse “all sellers” dump is not permission.

Related reading

See bulk SMS from Excel and CSV, how an Android SMS gateway works, SMS API documentation, and FATF for KYC programme context (not legal advice).

Context

Trust-and-safety teams land here after a growth export “all sellers incomplete” included buyers and muted accounts. Radio reality: an offline ops tablet means KYC deadlines pass while the queue looks empty. Seller-console OTP cannot share this burst.

Core scenario guidance

Require purpose=kyc, legal entity, locale, and expiry date on import. Join suppress. Canary staff sellers first. Pace to the SIM, not a cloud ESP fantasy.

Acceptance: “zero promo purpose codes in the KYC send log.” Developer Center owns request shapes.

Cost and ownership

Devices + volume + airtime. Wrong-purpose retries burn credit and goodwill. Assign who signs the extract and who tops up the SIM. Free (1 / 300 / 300) is a hygiene lab. Starter / Professional / Business uncap platform volume vs Developer; they still cap devices.

Operations

Daily pairing, battery, queue, DLR, purpose-mismatch rejects. After OEM updates, ten staff KYC rows. Spare charged device. On-call before weekend verification deadlines.

Security and compliance

Protect keys. Do not put document IDs or full names in SMS if a portal link suffices. Avoid logging OTP bodies. Verify webhooks if a KYC vendor event appends numbers. STOP still applies if you later promo from this CLI — better: never promo from it.

Decision guide

Ship when purpose gates and fallbacks exist. Delay if offline-phone behavior at deadline is unexplained. If zero phone ops is mandatory, evaluate CPaaS for that lane.

Checklist

• Purpose=kyc required on import.
• Promo extract cannot join.
• OTP isolated.
• Staff canary passed.
• Spare device paired.
• On-call named.

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 purpose and consent metadata. Marketplace seller alerts still need failover when one phone is the SPOF — KYC deadlines do not wait. Never auto-reply into OTP threads. Battery exemptions dominate overnight waves.

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

Deep dive: scaling and failure modes

Scale is cleaner lists and more devices, not a fake unlimited carrier pack. Bulk CSV needs validation before radio send. Scheduled SMS must survive timezone mistakes across seller regions. Never claim unlimited free cloud SMS credits with no device or volume meter.

Deep dive: integration discipline

Developer Center owns live API parameters. Vendor webhooks that append KYC contacts must verify signatures. If zero phone ops is mandatory, evaluate CPaaS. Scenario playbooks still bill by devices and SMS send volume. You bring the Android phone and operator SMS credit.