Skip to content

The field note · 6 min read

How Emergency Contacts Receive and Respond to Decal Relays

Setting up emergency contacts is the single most valuable action an owner takes after activating their decal. Here is how alerts are delivered and escalated behind the scenes.

Eswar ChinthakayalaUpdated 3 Oct 2026
VaahanSafe Editorial Image for emergency-contact-relays
In this story

When a vehicle is involved in a roadside incident or causes a parking obstruction, the speed and reliability of the notification pipeline determine whether the situation is resolved calmly or escalates into tragedy. Behind a simple 3-second QR scan lies an orchestrated, multi-tier notification engine designed on Cloudflare Workers and telecom gateways to guarantee delivery even under degraded mobile networks. Here is the technical architecture of that emergency handshake.

1. The Two Communication Modes: Emergency Incident vs Vehicle Movement

Not all roadside scans are accidents. VaahanSafe differentiates between two distinct operational modes:

Mode A: Vehicle Movement Alert (Parking / Obstruction)

Designed for routine urban congestion, double-parking, or blocked driveways. The passerby selects 'Vehicle Moving Required'. The system immediately dispatches a high-priority push notification and SMS to the registered vehicle owner: 'Your vehicle [MH 12 AB 1234] is causing an obstruction at [Street Name]. Please move it.' No calls are placed to emergency family contacts in this mode.

Mode B: Roadside Emergency / Collision Alert

Triggered when the passerby selects 'Emergency Assistance / Collision'. This activates the high-urgency fallback telephony cascade, dialing pre-registered emergency contacts immediately.

2. The Fallback Escalation Cascade: Timer-Based Routing

In an emergency, if the primary contact is in a meeting, driving, or has their phone on silent, seconds matter. VaahanSafe executes an automated, timer-governed escalation cascade:

01

Primary Emergency Contact Dial (25-Second Window)

TIER 1

The edge gateway dials Priority Contact 1 via masked virtual DID with an automated IVR announcing: 'This is an urgent VaahanSafe emergency alert regarding vehicle [MH 12 AB 1234]. Press 1 to connect to the roadside responder.'

02

Secondary Contact Escalation (20-Second Window)

TIER 2

If Contact 1 does not answer or declines within 25 seconds, the system instantly switches to Priority Contact 2, placing a simultaneous voice call while logging the transition in the audit queue.

03

Multi-Channel Broadcast Burst (Instant Fallback)

TIER 3

If neither voice call is answered, the engine broadcasts an urgent WhatsApp notification and SMS to all registered contacts containing: 'EMERGENCY: Vehicle [MH 12 AB 1234] QR scanned at [Location]. Live GPS: [Maps Link]. Responder is attempting contact.'

3. Preventing Notification Storms: Edge Idempotency

At a major highway accident, ten different bystanders may attempt to scan the vehicle QR code within two minutes. Without rate-limiting, the victim's family would be overwhelmed by a paralyzing flood of simultaneous calls and SMS alerts.

VaahanSafe enforces an edge-backed deduplication window using Cloudflare Queues and D1. When a scan event occurs, an idempotency key `qr_{id}_incident_{window}` is locked for 8 minutes. Subsequent scans within this window are linked to the existing active incident session, allowing additional helpers to view status without triggering duplicate voice calls.

EMERGENCY CONTACT SETUP VERIFICATION
✓Add at least two distinct emergency contacts with verified mobile numbers
✓Verify that Priority Contact 1 and Contact 2 reside in different locations or routines
✓Inform your contacts that calls from the VaahanSafe virtual number represent urgent alerts
✓Test your relay using the 'Test Notification Handshake' button in the customer app
✓Ensure both contacts have consented to receive emergency WhatsApp alerts
✓Update contact numbers immediately whenever a family member changes their phone
Common questions

What number will my emergency contacts see on their caller ID?

Calls originate from our verified telecom virtual DID (e.g., `+91-80-XXXX-XXXX`). The caller ID displays 'VaahanSafe Emergency Relay' on supported networks, ensuring contacts recognize the call as a critical alert rather than spam.

Can an emergency contact call back the number if they miss the call?

Yes. If an emergency contact calls back the virtual DID within 30 minutes of the incident, our IVR recognizes their incoming phone number, retrieves the active incident context, and provides options to connect directly to the roadside helper or listen to incident location coordinates.

Sources & further reading (2)
References
  • TRAI Emergency Communication & Calling Line ID Privacy Regulations

    Standards for enterprise telecom DID relays and emergency IVR announcements

    trai.gov.in
  • Cloudflare Workers & Queues Distributed Event Processing Architecture

    Sub-50ms edge resolution and queue-backed idempotency specifications

    cloudflare.com
#Notification Engine#Cloudflare Queues#Emergency Relay#VoIP Architecture#Fallback Cascade
ABOUT VAAHANSAFE

Learn how the vehicle safety identity works.

Discover how a QR connects a vehicle to the safety information its owner chooses to make available.

Explore VaahanSafe

Keep reading