> ## Documentation Index
> Fetch the complete documentation index at: https://help.rekkeh.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding Emergencies in Rekkeh

> Learn how Rekkeh handles emergency alerts, who is notified, how staff respond, and how emergencies differ from incidents and accountability checks.

Emergencies in Rekkeh are urgent events that require an immediate response from your security team, gate staff, and designated responders. When an emergency is declared, Rekkeh automatically broadcasts alerts, tracks responses, and guides responders through a defined lifecycle.

## What counts as an emergency

Rekkeh supports three emergency categories:

| Category         | When to use                                                                                                                        |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Emergency**    | A general urgent event such as a fire, medical crisis, or physical threat that requires immediate action from staff and residents. |
| **Silent panic** | A covert distress alert sent without obvious on-screen indicators so the user can request help discreetly.                         |
| **Guard duress** | A high-priority alert raised by a guard who is under threat or coercion, typically at a gate or during a patrol.                   |

## Who is notified

When an emergency is triggered, Rekkeh notifies:

* **Estate administrators and security managers** via mobile push notifications and in-app alerts
* **On-site staff** through the Gate Ops app
* **Designated responders** based on the emergency type and recipient settings
* **Channels integrated** with Rekkeh (such as Slack or Microsoft Teams, if configured)

<Note>
  Emergency notifications override quiet hours and send with high-priority flags where the device platform supports it.
</Note>

## Where staff respond

All emergency management and response tracking happens in the **Estate Admin** dashboard and the **Gate Ops** app:

* **Estate Admin**: Trigger, monitor, and resolve emergencies; view live accountability checks; access the timeline and building breakdown.
* **Gate Ops**: Receive emergency assignments, view responder instructions, and acknowledge or escalate the event.

## Emergency response lifecycle

Emergencies follow a clear lifecycle so nothing falls through the cracks:

| Phase              | What happens                                                                                          |
| ------------------ | ----------------------------------------------------------------------------------------------------- |
| **Triggered**      | A user or admin declares the emergency. Rekkeh broadcasts alerts immediately.                         |
| **Broadcast sent** | Notifications reach assigned recipients. An accountability check may start automatically or manually. |
| **Acknowledged**   | Responders confirm they received the alert and are acting.                                            |
| **In progress**    | Ongoing response operations, linked to patrols, incidents, or gate actions.                           |
| **Resolved**       | The threat is contained or the event is over.                                                         |
| **Closed**         | Final review completed and archived.                                                                  |

## How emergencies differ from incidents and accountability checks

| Feature          | Emergency                            | Incident                       | Accountability check                        |
| ---------------- | ------------------------------------ | ------------------------------ | ------------------------------------------- |
| Purpose          | Immediate threat response            | Log and review an event        | Roll call to confirm safety                 |
| Speed            | Real-time broadcast                  | Logged for later triage        | Broadcast, but non-urgent if unacknowledged |
| Notifications    | Push, in-app, integrations           | In-app and dashboard only      | Push and in-app                             |
| Linked workflows | Can spawn incidents and patrol tasks | Standalone or linked to patrol | Runs during or after an emergency           |

<Warning>
  Do not use a standard incident report when there is an active threat to life or property. Trigger an emergency instead.
</Warning>

## Default emergency SLA

Rekkeh targets a **5-minute response window** from trigger to first acknowledgment. Admins can review response times in the emergency timeline and audit trail.

Emergencies in Rekkeh are urgent events that require an immediate response from your security team, gate staff, and designated responders. When an emergency is declared, Rekkeh automatically broadcasts alerts, tracks responses, and guides responders through a defined lifecycle.

## What counts as an emergency

Rekkeh supports three emergency categories:

| Category         | When to use                                                                                                                        |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Emergency**    | A general urgent event such as a fire, medical crisis, or physical threat that requires immediate action from staff and residents. |
| **Silent panic** | A covert distress alert sent without obvious on-screen indicators so the user can request help discreetly.                         |
| **Guard duress** | A high-priority alert raised by a guard who is under threat or coercion, typically at a gate or during a patrol.                   |

## Who is notified

When an emergency is triggered, Rekkeh notifies:

* **Estate administrators and security managers** via mobile push notifications and in-app alerts
* **On-site staff** through the Gate Ops app
* **Designated responders** based on the emergency type and recipient settings
* **Channels integrated** with Rekkeh (such as Slack or Microsoft Teams, if configured)

<Note>
  Emergency notifications override quiet hours and send with high-priority flags where the device platform supports it.
</Note>

## Where staff respond

All emergency management and response tracking happens in the **Estate Admin** dashboard and the **Gate Ops** app:

* **Estate Admin**: Trigger, monitor, and resolve emergencies; view live accountability checks; access the timeline and building breakdown.
* **Gate Ops**: Receive emergency assignments, view responder instructions, and acknowledge or escalate the event.

## Emergency response lifecycle

Emergencies follow a clear lifecycle so nothing falls through the cracks:

| Phase              | What happens                                                                                          |
| ------------------ | ----------------------------------------------------------------------------------------------------- |
| **Triggered**      | A user or admin declares the emergency. Rekkeh broadcasts alerts immediately.                         |
| **Broadcast sent** | Notifications reach assigned recipients. An accountability check may start automatically or manually. |
| **Acknowledged**   | Responders confirm they received the alert and are acting.                                            |
| **In progress**    | Ongoing response operations, linked to patrols, incidents, or gate actions.                           |
| **Resolved**       | The threat is contained or the event is over.                                                         |
| **Closed**         | Final review completed and archived.                                                                  |

## How emergencies differ from incidents and accountability checks

| Feature          | Emergency                            | Incident                       | Accountability check                        |
| ---------------- | ------------------------------------ | ------------------------------ | ------------------------------------------- |
| Purpose          | Immediate threat response            | Log and review an event        | Roll call to confirm safety                 |
| Speed            | Real-time broadcast                  | Logged for later triage        | Broadcast, but non-urgent if unacknowledged |
| Notifications    | Push, in-app, integrations           | In-app and dashboard only      | Push and in-app                             |
| Linked workflows | Can spawn incidents and patrol tasks | Standalone or linked to patrol | Runs during or after an emergency           |

<Warning>
  Do not use a standard incident report when there is an active threat to life or property. Trigger an emergency instead.
</Warning>

## Default emergency SLA

Rekkeh targets a **5-minute response window** from trigger to first acknowledgment. Admins can review response times in the emergency timeline and audit trail.