Key Takeaways
- Template language follows the user’s saved locale, not the listing city and not the device IP.
- Pickup-point “parcel arrived” is operational. “New lockers in your area” is promo with STOP.
- Free is 1 device, 300 SMS lifetime, and 300 contacts. Platform price is devices plus send volume; you buy phones and airtime.
- Buyer OTP and payout SMS stay off locale-fanout and locker-promo SIMs.
- VIP seller segments still need a source timestamp — GMV over a threshold is not consent.
Summary
Scenario 191 is marketplace contact lists for locale routing and pickup-point alerts — not the generic three-ledger split, not T&S, not geo-radius fan-out. Wrong-language OTP and locker texts are how you burn airtime and trust in the same send. Service pricing is devices plus SMS send volume. You bring the phone and operator credit. Free is 1 device, 300 SMS lifetime, and 300 contacts.
Professional allows 5 devices: OTP, pickup-ops, locale promo, two spares. Uncapped platform volume is not unlimited carrier SMS. Confirm imports in Developer Center.
saved locale · pickup ops · VIP source
listing language does not pick the template
Locale lists are not a language guess
Join the user’s locale at send time. Missing locale → documented default, not “whatever the seller typed.” RTL and concatenated GSM still count as platform volume and operator segments.
If a VIP seller segment is “GMV over $10k,” that is a business tag. It is not an SMS opt-in. Promo still needs a source and STOP. Payout and dispute SMS use the ops ledger.
Locale and pickup matrix
| List | Join key | Failure |
|---|---|---|
| OTP / login | User locale + isolated SIM | French OTP from listing language |
| Pickup arrived | Parcel + point subscriber | Promo locker blast on same device |
| New locker nearby | Promo + STOP | City CSV, no consent |
| VIP sellers | Tag + separate consent | GMV dump used as a blast list |
Pickup-point subscribers
Operational “your parcel is at locker 12” is transactional. “We opened three new points” is marketing. Quiet hours on the latter. Bulk consent, OTP.
High-value sellers are still consented
Source timestamp on promo. Purpose-level STOP. Chat export still quarantined. Google Ads SMS/MMS policy.
Devices, volume, and airtime
Wrong-locale retries double spend. We meter devices and platform sends. Free (1/300/300) is staging.
Launch operations
Canary one locale A user, one locale B, one pickup-ops, one banned-from-promo. Setup, Downloads, pricing, DLR.
Decision guide
Ship when locale is a join, not a guess, and locker promo is separate. Delay if VIP equals blast. No-phone-ops: aggregator.
Locale-list checklist
- Send-time locale join.
- Pickup-ops vs locker-promo split.
- VIP has consent source.
- OTP isolated.
- Chat export quarantined.
- Developer Center fields confirmed.
Next steps
Scenario 11 ledgers, scenario 71 T&S, scenario 131 geo.
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
