Personal Safety

Personal Safety (“People Protect”) embeds AURA’s on-demand emergency response into a consumer-facing app or service. An end user raises a callout from your product, 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.
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.
3. Raise callouts on the user’s behalf and follow them through the callout lifecycle.
4. Receive updates via polling or 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. The journey should feel simple but reassuring, showing the customer a responder is on the way.

Test before subscribing

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.

Related

• Quickstart · Callout lifecycle
• Go-live checklist