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

Install and onboard through your App Store or Play Store listing.
Register or sign in using the authentication journey configured for the brand.
Complete the safety profile needed by the enabled product and region.
Activate access through a hosted payment option, your third-party gateway, or another subscription option agreed during onboarding.
Request help through the branded panic experience.
Track the callout while AURA coordinates response.
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, store setup, and the white-label go-live checklist.