Car emergency / entrapment call.

Trigger, action plan, and escalation criteria.

Related metric

vertical_transport_availability

Trigger

car_emergency_activation = 1 (raises entrapment surface + notify)

Value drivers

Customer experience Operational continuity

Preconditions

The car-emergency / alarm-activation signal is exposed from the controller or OEM interface. This alarm is explicitly framed as surface-and-notify: the building's certified in-car emergency line remains the response path and is never replaced.

Human role

Supporting, not primary response — the certified in-car emergency phone line and its monitoring handle the rescue. Keedian surfaces the event at top priority and notifies the building operator so they are aware in the moment; Keedian never substitutes for the certified emergency line.

Action plan

(1) Surface the event at the highest priority the instant it is read and notify the building operator so they know a car may have an entrapment in progress. (2) Attribute it to the specific car and log the event with its timestamp for the audit trail. (3) Do NOT treat Keedian's notification as the emergency response — confirm the certified in-car emergency line and its monitoring are the acting channel.

Escalation

(1) The building operator is notified immediately every time — there is no hold cadence for this alarm. (2) If the event does not clear and no response is confirmed on the certified line, re-notify the operator; Keedian's role stays notification, not dispatch.

Prevention

(1) Confirm at onboarding that the certified in-car emergency line and its monitoring are the designated response path, with Keedian as an awareness signal only. (2) Verify the car-emergency point mapping per unit so a real activation is never missed and a stuck point does not manufacture false alarms.