> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.aurasos.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.aurasos.com/_mcp/server.

# People Protect

**People Protect** embeds AURA's on-demand safety response into your consumer-facing application or service. It provides emergency armed and private medical response when it's needed most, protecting your users, drivers, staff, and customers wherever they go.

An end user creates a callout from your product (or via a linked wearable device), and AURA's 24/7 control room dispatches vetted responders — security, medical, and related response types — with live GPS tracking through to resolution.

## When to use this

* A mobile app or service where individual users need one-tap access to armed
  security or medical response.
* You manage the user relationship; AURA provides the response network and
  dispatch.

## The integration journey

1. **Authenticate** as your customer source — see [Authentication](/overview/core-concepts/authentication).
2. **Onboard the user** as a customer, with a subscription that entitles them to
   response. You can create the customer and subscription together, or use a
   hosted [signup session](/api-reference/customer-sessions).
3. **Create callouts** on the user's behalf and follow them through the
   [callout lifecycle](/overview/core-concepts/callout-lifecycle).
4. **Receive updates** via polling or [webhooks](/overview/core-concepts/webhooks), and collect a
   rating once resolved.

## Designing the panic journey

AURA's guidance is "Help in 2 Clicks" — make the panic action reachable in as few
taps as possible, placed prominently and available throughout your app. If parts
of your app sit behind a login that can expire, add a pre-login panic button
backed by a [callout-scoped token](/overview/core-concepts/authentication). The
journey should feel simple but reassuring, showing the customer a responder is on
the way.

## Test before subscribing

```mermaid
flowchart LR
    A([Start]) --> B[Landing page]
    B --> C{Try it first?}
    C -- "Free test panic" --> D[Test the service]
    D --> E[Subscribe]
    C -- "No" --> E
    E --> F([Protected])
```

AURA allows **one free test panic per user** before a subscription is required.
Use the customer's `hasPanicked` flag to decide whether to offer the
test-the-service flow or send the user to subscribe. A TEST panic
(`calloutClassificationId: 2`) lets the control centre walk the user through the
experience and close it once confirmed with their safe code.

## Key requirement

Live callouts require the customer to have an **active subscription**. Confirm
entitlement before exposing panic functionality — see
[Subscriptions & coverage](/overview/core-concepts/subscriptions).

## Related

* [Quickstart](/people-protect/quickstart)
* [Customer registration](/people-protect/customer-registration)
* [Subscription management](/people-protect/subscription-management)
* [Creating callouts](/people-protect/creating-callouts)
* [Go-live checklist](/people-protect/deploy/go-live)