Key Takeaways
- Scenario 1643 is local meetup / in-person handover contact lists — not escrow vaults, age-gate lockers, auctions, or seller KYC.
- “Saturday 10:00 at the station — code 4412” is transactional to the deal. “More listings near you” is marketing.
- Free caps contacts at 300. Do not import every expired meetup 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 weekend of handover codes will starve it if shared.
- REST list/send fields live in Developer Center — not a CodeCanyon meetup plugin.
Summary
Scenario 1643 is marketplace contact lists for in-person handovers: local pickup of a couch, a bike, a console. The deal owns the pin. The Android only sends. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If the meetup code and the “listings near you” blast share a SIM, Saturday morning promo will delay the only text that keeps two strangers from waiting in a car park.
In-person handover lists
Pull MSISDNs from the deal parties, not “everyone in the postcode.” Marketplace templates. Fields: Developer Center. Industry context: GSMA.
List map
| List | SMS | Device | Rule |
|---|---|---|---|
| Buyer / seller — meetup | Window + code | Handover transactional | Role-specific; no group blast |
| LATE inbound | Patch the deal | Same inbox | Not a promo unsubscribe |
| Staff | Console OTP | Dedicated OTP phone | Never share Saturday volume |
| Nearby listings | Promo | Promo MSISDN | STOP persist |
Meetup code vs OTP
Idempotent on deal id. Never log the code in Slack. Idempotent send · E.164.
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 weekend of meetups. Failover · Doze · setup.
Security
Do not SMS home addresses in the first ping if a public landmark will do. Trust Center · STOP · OTP.
Checklist
- Role templates; no group pin blast.
- LATE mapped; promo STOP separate.
- OTP isolated.
- Contact cap vs Free 300 understood.
- Code not in shared chat.
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
