Key Takeaways
- A “bag left the vault” SMS dies at the cage. The run crew owns the branch window — different SIM, different template.
- Slot A: branch / night-drop PINs. Slot B: garage overflow when the truck is offline — never bank promo.
- Free is 1 device, 300 SMS lifetime, and 300 contacts. Developer is 25,000 SMS per year. Platform price is devices plus send volume.
- Teller portal OTP stays on the branch chassis, not the vault radio that already texted “en route.”
- Idempotency is bag-id plus leg (vault / run) — not the branch phone.
Summary
Scenario 711 is dual-SIM routing for cash-in-transit vault-to-branch-run handoff — not white-glove sofas, not specimens, not barges, not city parcels. The vault dies at the cage. An armored run finishes the night drop. Those legs must not share a default SIM or a single “cash is coming” lie. Service pricing is devices plus SMS send volume. You bring the phones and operator credit. Free is 1 device, 300 SMS lifetime, and 300 contacts.
Starter allows 2 devices: run dual-SIM plus a spare vault chassis. Uncapped platform volume is not unlimited carrier SMS. Confirm routing in Developer Center.
vault · cage · branch PIN
one bag-id, one public ETA at a time
Vault dwell is not the branch ETA
Vault SMS ends at cage scan. Run SMS starts after the crew is assigned. Do not let the “left vault” template keep firing while the bag sits on a dolly. Slot A on the branch phone owns PINs. Slot B is backup when the truck’s home operator dies in the garage.
If the cage scan and the run assign both fire “we’re 10 minutes out,” the teller opens the dock for a truck still in the vault. Suppress vault branch templates the moment inbound cage posts.
CIT dual-SIM matrix
| Leg | Radio | Failure |
|---|---|---|
| Vault / cage | Vault device, no PIN | Night-drop code sent from the vault |
| Cage scan | Suppress vault ETA | Two “nearby” texts |
| Run assign | Slot A PIN / ETA | Promo SIM used at the dock |
| Garage no-reg | Slot B backup | OTP on the vault radio |
Vault-to-run handoff
Persist bag-id plus leg. Signed webhooks. Webhooks, DLR. MCP wraps REST only. No amounts in the SMS body.
Branch PIN and seals
Hash, short TTL, branch slot A only. After OEM updates, canary both slots. FFIEC is custody language — not a reason to text bag totals.
Devices, volume, and airtime
Two legs can double volume if you forget suppress. We meter devices and platform sends. Free (1/300/300) is one branch proof.
CIT operations
Charge both chassis, pairing, slot balances. Setup, Downloads, pricing.
Decision guide
Ship when vault ETAs die at the cage. Delay if one SIM does both legs and promo. Not a CodeCanyon CIT pack.
CIT checklist
- Leg-keyed idempotency.
- Vault suppress on cage scan.
- PIN on branch slot A.
- No amounts in SMS.
- Developer Center fields confirmed.
Next steps
Scenario 651 white-glove, scenario 591 specimen.
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
