Key Takeaways
- Scenario 903 is cross-dock / transload-bay dual-SIM — not bonded customs, empty-container pickup, reefer dwell, milk-run consolidation, last-mile, yard hold, hazmat, or returns.
- “Bay XD-8 ready — inbound T-3, outbound van 14” is transactional. “Book our extra cross-dock week” is marketing. Split SIMs.
- Dashboard OTP stays on a dedicated Android. A Friday transload pile will starve it.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 1 / 300 / 300. Developer is 25,000 SMS per year.
- Idempotent on bay + clock hour. Radio retries still spend operator credit.
- REST send fields live in Developer Center — not a CodeCanyon cross-dock plugin. MCP, if you use it, is only a REST wrapper.
Summary
Scenario 903 is logistics dual-SIM for cross-dock transload. The WMS owns the bay. SIM A texts inbound and outbound. SIM B never rides that inbox. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If the only “bay is ready” proof is a promo SIM that also sold extra cross-dock weeks, you have mixed a transload clock with a sales blast.
Cross-dock transload
Route bay-ready and van assign to SIM A. Dual-SIM routing · logistics guide. Fields: Developer Center. Industry context: GSMA.
SIM map
| Message | SIM | Idempotency | Do not |
|---|---|---|---|
| Bay / van | Transactional A | Bay + hour | Reuse as a marketing key |
| Extra cross-dock week | Promo B | Consent + quiet hours | Ride the dock inbox |
| Dashboard login | Dedicated OTP phone | — | Share the transload radio |
Same From on bay
Keep the dock number stable so drivers recognize the bay. Idempotent send. DLR ≠ loaded — DLR.
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 Friday transload pile. Doze · setup.
Security
Do not SMS the full inbound manifest. Trust Center · OTP. Promo STOP off the bay inbox. STOP.
Checklist
- SIM A vs B labeled.
- Idempotency on bay + hour.
- OTP isolated.
- No full manifest on SMS.
- Airtime for Friday transload pile.
Next steps
Transactional SMS · SMS API documentation.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- multi-device and dual SIM routingCapacity and failover
- transactional SMS for orders and alertsEvent-driven messages
- SMS delivery reports (DLR)Delivery status tracking
- SMS API documentationLive endpoint reference
