Configuration workbook

A white-label launch has more configuration than icons and logos. Complete this workbook with AURA before implementation so product, commercial, operational, and store decisions stay aligned.

Market and product

Record:

• launch countries, customer regions, default country and calling codes;
• personal-safety or fixed-location product journey — the app supports one model per brand build, not a combined mode;
• Security, Medical, or other agreed response types;
• default language and whether in-app language switching is enabled. Today’s language set is a small fixed set of English variants, not general translation support — confirm with AURA if your market needs more;
• whether customers can create test callouts and how test mode is identified;
• coverage behaviour before signup, purchase, and panic.

Identity and customer data

Agree which system creates the customer and remains the source of truth. Define:

• signup and sign-in journey;
• external customer identifier and account-linking rules;
• required profile and medical fields;
• mobile-number verification and backup-contact behaviour;
• individual or family plan design and dependant limits per tier. Dependant management itself is a standard app feature available to every brand, not something to switch on or off;
• terms, privacy policy, consent, and minimum-age requirements;
• deletion, subscription deactivation, and support escalation flow.

If your backend provisions users, document how its customer and subscription IDs map to AURA IDs and how changes are reconciled.

Subscription and payment

For every plan, capture:

• display name, price, currency, duration, and eligible market;
• individual or family entitlement;
• hosted gateway, third-party gateway, access code, or externally provisioned access;
• renewal, grace period, failed payment, cancellation, and refund ownership;
• whether cancellation is immediate or effective at the end of the paid period;
• production merchant identifiers and separate staging test values.

See Third-party payment gateways for the callback and entitlement boundary.

Panic experience

Confirm:

• available response types and the default selection;
• personal or Fixed Location callout model;
• location permissions and location refresh. There is no in-app coverage-map UI today — confirm with AURA if your product needs one built;
• test-callout option and production safeguards;
• cancellation reasons and any soft-cancel confirmation;
• customer-visible ETA, map, responder details, route, and completion state;
• post-callout rating and support journey;
• device linking (panic buttons, GPS trackers) is a standard app feature available to every brand, not something to switch on. Apple Watch, CarPlay, and Android Auto are marked coming soon in-app, not currently live.

Not every item is available for every region or brand. Treat this list as a decision register, not a promise that all combinations are supported.

Communications and content

Provide:

• support email, telephone number, hours, and escalation copy;
• transactional and optional notification choices;
• push-notification credentials for each app and environment;
• onboarding, how-to-panic, empty-state, error, and support content;
• copy reviewed against the enabled language variant(s) — today that means the fixed English-variant set (standard, Samsung, Telecom), not translated languages;
• universal links, deep links, and any external support or account URLs.

Brand and stores

For each iOS, Google Play, and supported AppGallery listing, capture:

• legal publisher and account owner;
• unique bundle/application ID and app display name;
• icons, splash assets, screenshots, descriptions, keywords, category, and privacy disclosures;
• countries of availability and planned release track;
• signing, API access, push credentials, and account-expiry owner;
• person responsible for approving the listing and each future update.

Continue with Branding & config and Release & store operations.