Key Takeaways
- A temperature-probe SMS goes to quality and the driver. It does not go to the patient or retail consignee.
- Slot A is the domestic ops SIM. Slot B is backup when the reefer corridor has no registration — still not a marketing slot.
- Free is 1 device, 300 SMS lifetime, and 300 contacts. Platform price is devices plus send volume; each SIM spends its own airtime.
- Delivery OTP / locker codes stay on an isolated last-mile device, never on the probe radio.
- Weekend depot-closed templates need a human, not an auto “we delivered.”
Summary
Scenario 171 is dual-SIM routing for cold-chain and weekend-depot exceptions — not city last-mile slot maps and not line-haul handoff. Probe webhooks are noisy. Patients and pharmacies should not hear every spike. Service pricing is devices plus SMS send volume. You bring the handsets and operator credit. Free is 1 device, 300 SMS lifetime, and 300 contacts.
Business allows 15 devices: probe dual-SIM, quality on-call, last-mile OTP, depot spare. That is not unlimited carrier SMS. Confirm routing in Developer Center.
probe spike · quality · not consignee
excursion SMS never pages the patient list
Cold-chain exceptions are not public ETAs
Slot A: quality and driver. Slot B: backup operator along the corridor. Public ETA and locker OTP live on last-mile devices after a human clears the exception. Do not bind the probe webhook to the consignee template.
If the weekend depot is closed, auto-reply must not say “delivered.” It says “held, quality will confirm Monday.” A false POD on a reefer load is a compliance event, not a UX flourish.
Pharma dual-SIM matrix
| Event | Radio | Failure |
|---|---|---|
| Temp excursion | Slot A quality + driver | Patient list CC |
| No registration on A | Slot B backup | Promo SIM used “because it works” |
| Weekend hold | Depot device, human confirm | Auto POD |
| Locker / receipt OTP | Isolated last-mile SIM | Probe retry storm on OTP |
Probe alerts vs consignee copy
Persist excursion id. Debounce repeats. Signed webhooks. Webhooks, DLR. Live fields in Developer Center.
Weekend depot and slot B
Slot maps after OEM updates and after a generator bounce. Canary both slots on staff numbers before Monday’s first load. GSMA SIM.
Devices, volume, and airtime
Probe noise can dwarf consignee volume if you forget debounce. We meter devices and platform sends. Each operator meters its SIM. Free (1/300/300) is a single-lane proof.
Quality-desk operations
Charge, pairing, slot balances, on-call named. Setup, Downloads, pricing.
Decision guide
Ship when consignees cannot receive probe SMS and weekend POD is human. Delay if one dual-SIM phone is also marketing. No-phone-ops: aggregator.
Cold-chain checklist
- Probe audience = quality + driver only.
- Debounced excursion ids.
- OTP on a different device.
- No auto POD on weekend hold.
- Slot canary after power events.
- Developer Center fields confirmed.
Next steps
Scenario 51 city slots, scenario 111 line-haul, gateway overview.
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
