> 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.

# Customer journey & capabilities

The white-label app supplies a configurable customer experience on top of the
Panic API. AURA builds and operates the shared application; your brand,
commercial model, enabled features, and store presence shape what customers see.

## The standard journey

```mermaid
flowchart LR
    A[Install app] --> B[Sign up or sign in]
    B --> C[Complete profile]
    C --> D[Activate subscription]
    D --> E[Request help]
    E --> F[Track response]
    F --> G[Cancel or complete]
```

1. **Install and onboard** through your App Store or Play Store listing.
2. **Register or sign in** using the authentication journey configured for the
   brand.
3. **Complete the safety profile** needed by the enabled product and region.
4. **Activate access** through a hosted payment option, your
   [third-party gateway](/white-label/integrations/payment-gateway), or another
   subscription option agreed during onboarding.
5. **Request help** through the branded panic experience.
6. **Track the callout** while AURA coordinates response.
7. **Cancel or complete** the journey and return to the app.

## Capability model

| Area          | Standard foundation                               | Configured per brand or integration                                                           |
| ------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Identity      | Customer registration and authenticated sessions  | Copy, required profile fields, terms, and supported sign-in journey                           |
| Brand         | Shared app structure                              | Name, logos, icons, and content                                                               |
| Subscription  | Panic API entitlement                             | Hosted payment, third-party gateway, access code, plan presentation, and cancellation choices |
| Panic         | Callout creation, current location, and tracking  | Personal-safety or fixed-location journey, response types, medical fields, and test behaviour |
| Devices       | Supported device linking and events               | Supplier, device type, templates, and onboarding journey                                      |
| Communication | Push-notification foundation and support surfaces | Firebase/store setup, notification choices, contact details, and languages                    |
| Release       | Shared build and publishing pipeline              | Store ownership, bundle IDs, signing, rollout, and release approval                           |

Not every capability is enabled for every brand. Confirm the agreed customer
source configuration before designing marketing, support, or payment flows.

## What you own

You own the customer proposition, pricing and commercial terms, brand assets,
store accounts unless agreed otherwise, first-line support, and any third-party
systems connected to the app.

AURA owns the shared application platform, Panic API integration, emergency
response workflow, and the build/release work agreed for your brand.

## Plan the experience

Before build work starts, document:

* target countries, regions, languages, and response types;
* personal-safety or fixed-location product model;
* signup, terms, payment, renewal, cancellation, and support journeys;
* profile, medical, dependent, location, and device features;
* brand assets and store metadata;
* analytics, privacy, notification, and deep-link requirements;
* staging acceptance criteria and production launch owner.

Continue with [Branding & config](/white-label/integrations/branding-config),
store setup, and the [white-label go-live checklist](/white-label/deploy/go-live).