Key Takeaways
- Pickup-point and locker lists are location traffic. A GMV promo extract must never join that file.
- PIN and locker codes are authentication. They do not belong in a bulk contact import.
- Dashboard OTP stays on a dedicated device. A locker-ready burst 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. Developer is 25,000 SMS per year.
- Store locker id and hold window with the number. A warehouse “ready for pickup” dump is not permission.
Summary
Marketplace contact lists in scenario 239 are pickup-point and locker-ready buyers: hold windows, site codes (not PINs), expiry nags. This is not GMV promo splits, KYC, or dispute cases. It is location traffic on an Android SIM. A PIN in the CSV is an incident.
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; that is not unmetered carrier SMS. Paid plans may uncap platform send volume; devices and airtime remain metered.
A locker-ready SMS that includes the PIN in the same file as a coupon list is not “convenience.” It is a code you published to marketing.
Key takeaways
- Pickup-point and locker lists are location traffic. A GMV promo extract must never join that file.
- PIN and locker codes are authentication. They do not belong in a bulk contact import.
- Dashboard OTP stays on a dedicated device. A locker-ready burst 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. Developer is 25,000 SMS per year.
- Store locker id and hold window with the number. A warehouse “ready for pickup” dump is not permission.
Related reading
See bulk SMS from Excel and CSV, how an Android SMS gateway works, SMS API documentation, and UPU for last-mile / pickup context.
Context
Ops teams land here after a “ready at locker” export included PINs, or after a promo join resurrected muted buyers. Radio reality: an offline tablet means parcels expire in the box. Console OTP cannot share this burst.
Core scenario guidance
Require locker id, hold-until, locale. Fail rows with PIN/OTP-like columns. Canary staff lockers first. Pace to the SIM.
| List | Allowed SMS | Reject |
|---|---|---|
| Locker ready | Site + hold window + portal | PIN, festival copy |
| Hold expiring | Hours left + portal | Upsell SKU |
| Staff | Canary | Skipped for “peak” |
| PIN / OTP | Dedicated device, not this CSV | Same import as ready-blast |
Acceptance: “zero PIN-like columns in the ready send log.” MCP wraps REST. Developer Center owns shapes.
Cost and ownership
Devices + volume + airtime. Wrong-purpose retries burn credit. Developer is 25,000 SMS per year. Free (1 / 300 / 300) is a hygiene lab.
Operations
Daily pairing, battery, queue, DLR, PIN-column rejects. After OEM updates, ten staff locker rows. Spare charged device. On-call before weekend hold expiries.
Security and compliance
Protect keys. Never put locker PINs in bulk files. Avoid logging OTP bodies. Verify webhooks if a locker vendor appends numbers. Never promo from the locker-ready CLI if it ever carried PINs.
Decision guide
Ship when purpose gates and fallbacks exist. Delay if offline-phone behavior at hold expiry is unexplained. If zero phone ops is mandatory, evaluate CPaaS for that lane.
Checklist
- PIN columns fail the file.
- Promo extract cannot join.
- OTP isolated.
- Staff canary passed.
- Spare paired.
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 hold metadata. Hold windows do not wait for a dead tablet. Never auto-reply into OTP threads. Battery exemptions dominate overnight locker waves.
Deep dive: scaling and failure modes
Scale is cleaner lists and more devices, not a fake unlimited carrier pack. Never claim unlimited free cloud SMS credits with no device or volume meter.
Deep dive: integration discipline
Developer Center owns live API parameters. Locker-vendor webhooks must verify signatures. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator SMS credit.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- contacts, lists, and segmentsAudience hygiene
- bulk SMS from Excel and CSVSpreadsheet campaigns
- bulk SMS with consent best practicesHigh-volume outreach
- SMS API documentationLive endpoint reference
