Key Takeaways
- A “cortege left the chapel” SMS dies at the gate. The flower van owns a different family ETA — different SIM, different template.
- Slot A: cemetery / family PINs. Slot B: rural overflow when the hearse is offline — never funeral 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.
- Family portal OTP stays on the director chassis, not the hearse radio that already texted “en route.”
- Idempotency is service-id plus leg (hearse / flowers) — not the family phone. No names of the deceased in SMS.
Summary
Scenario 831 is dual-SIM routing for funeral cortege versus flower-van last mile — not CIT, not blood units, not white-glove sofas. The hearse dies at the cemetery gate. A florist van finishes a different stop. Those legs must not share a default SIM or a single “we’re on the way” 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: hearse dual-SIM plus a spare florist chassis. Uncapped platform volume is not unlimited carrier SMS. Confirm routing in Developer Center.
chapel · gate · florist PIN
one service-id, one public status per leg
A hearse ETA is not the flower van
Hearse SMS ends at cemetery gate scan. Florist SMS is a separate assign. Do not let the chapel-departed template keep firing while the van is still loading sprays. Slot A on the director phone owns family PINs. Slot B is backup on rural stretches.
If chapel-depart and florist-assign both fire “we’re 10 minutes out,” the family opens the gate for the wrong vehicle. Suppress hearse family templates the moment the inbound gate posts — then run florist as its own leg.
Funeral dual-SIM matrix
| Leg | Radio | Failure |
|---|---|---|
| Chapel / hearse | Hearse device, no PIN | Cemetery code sent from the chapel |
| Gate scan | Suppress hearse ETA | Two “nearby” texts |
| Florist assign | Slot A PIN / status | Promo SIM used at the grave |
| Rural no-reg | Slot B backup | OTP on the hearse radio |
Chapel-to-van handoff
Persist service-id plus leg. Signed webhooks. Webhooks, DLR. MCP wraps REST only. No names of the deceased in SMS.
Cemetery PIN and privacy
Hash, short TTL, director slot A only. After OEM updates, canary both slots. NFDA is practice language — not a reason to text the service sheet.
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 service proof.
Director operations
Charge both chassis, pairing, slot balances. Setup, Downloads, pricing.
Decision guide
Ship when hearse ETAs die at the gate. Delay if one SIM does both legs and promo. Not a CodeCanyon funeral pack.
Funeral checklist
- Leg-keyed idempotency.
- Hearse suppress on gate scan.
- Florist as its own leg.
- No deceased names in SMS.
- Developer Center fields confirmed.
Next steps
Scenario 651 white-glove, scenario 711 CIT.
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
