Key Takeaways
- Scenario 1703 is high-value authenticity / escrow contact lists — not auctions, age-gate PINs, seller onboarding, or dispute appeals.
- “Item received at vault” is transactional. “Browse watches like yours” is marketing. Split MSISDNs.
- Free caps contacts at 300. Do not dump every failed authenticity case into the gateway book.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Developer is 25,000 SMS per year.
- Staff console OTP stays on its own phone. A drop-day of vault notices will starve it if shared.
- REST list/send fields live in Developer Center — not a CodeCanyon escrow plugin.
Summary
Scenario 1703 is marketplace contact lists for authenticity and escrow: watches, bags, or art that sit in a vault until a lab says yes. The case owns the item. The Android only sends. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If the release code and the “you might like this Rolex” blast share a SIM, a Friday promo will delay the only text that moves six figures.
Authenticity and escrow lists
Pull MSISDNs from the case parties, not “everyone who viewed the lot.” Marketplace templates. Fields: Developer Center. Industry context: GSMA.
List map
| List | SMS | Device | Rule |
|---|---|---|---|
| Seller — inbound to vault | Received + case id | Escrow transactional | Once per state |
| Buyer — result / release | Portal; no shared code | Same pool or second SIM | Role-specific template |
| Staff | Console OTP | Dedicated OTP phone | Never share drop volume |
| Consign promo | Recruit blast | Promo MSISDN | STOP persist |
Inspection codes vs OTP
Idempotent on case+state. Idempotent send · E.164. Never log release secrets.
Cost
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free: 1 device, 300 SMS lifetime, 300 contacts. Developer: 25,000 SMS per year. Paid plans uncap platform volume; devices still meter. Pricing.
Ops
Spare radio before a drop day. Failover · Doze · setup.
Security
Do not SMS serials in the clear. Trust Center · STOP · OTP.
Checklist
- Role templates; no shared release code.
- Case id on every enqueue.
- OTP isolated.
- Contact cap vs Free 300 understood.
- Promo STOP separate.
Next steps
Marketplace KPIs · SMS API documentation.
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
