Architecture Overview

Insurance Flow Architecture

Collaborative system view to align on integration and conversion approach

Race FlowGym FlowHiQOR — System of RecordCarrier Integration

Race Registration Flow (Partner-Controlled Environment)

Primary Integration Flow

HiQOR receives/originates records, normalizes payloads, and routes consent-aware flows to Olly and carriers

Race Platform

Spartan / TicketSocket / Active

  • User registers for race event
  • Consent captured at checkout
Registration + Consent

HiQOR

Central Orchestrator

Consent Decision Point

  • No marketing consent → AD&D/base coverage flow
  • Marketing consent present → AD&D + conversion/upsell
  • Generate UUID for this lead
  • Evaluate consent state (TCPA)
API Integration LayerSecure endpoints + token authAD&D path
Conversion path

Olly Platform

Parallel execution

Track 1 — AD&D Binding

  • Immediate / transactional
  • Policy binding + carrier

Track 2 — Conversion Flow

  • SMS / Email outreach
  • Quote + policy bind
Execution Events + Policy Data Returned to HiQOR

HiQOR Routing Relay

Between Olly and carrier

  • Receives execution events from Olly
  • Reconciles + normalizes payload
  • Routes canonical bind data to carrier

Carrier Layer

Mutual / Allstate

  • Issues AD&D and Term Life coverage
OrchestrationTransactional laneAsync laneClosed-loop return

1) Decision at HiQOR

  • Race or microsite data lands in HiQOR first (not in Olly).
  • HiQOR evaluates consent and decides branch activation.
  • No consent: execute AD&D only. Consent: execute AD&D + conversion.

2) Parallel execution in Olly

  • Path A (no marketing consent): AD&D/base coverage actions.
  • Path B (marketing consent): AD&D plus conversion/upsell actions.
  • Both lanes remain linked to the same HiQOR UUID.

3) Data loops back to HiQOR

  • Olly returns execution data to HiQOR before carrier routing.
  • Application status + policy status.
  • Product type + premium.
  • Lifecycle timestamps for operational reporting and reconciliation.

Integration Model (High-Level)

  • HiQOR exposes secure API endpoints (AWS-based).
  • Endpoints vary by workflow context (race registration, gym/microsite, and partner paths).
  • Partners authenticate using token-based credentials.
  • Requests include user data, consent state, and routing context.
  • Olly processes the selected flow and returns status + event data to HiQOR.
Open Alignment Questions
  • Can upsell / marketing-driven offers (e.g., life insurance, upgrades) be shown without TCPA marketing consent, or must they be suppressed until consent is captured?
  • If a user does not opt into TCPA, what is the allowed engagement scope? Transactional only (e.g., coverage confirmation), In-flow UI offers only (no SMS/email follow-up), or No upsell at all?
  • Where is the optimal moment to capture TCPA consent for highest conversion? Registration (race/gym), Pre-scan, or Post-scan (after value is shown)?
  • Should AD&D (transactional coverage) and marketing consent flows remain decoupled, or do we introduce a progressive (step-up) consent model?
  • What conversion ownership model are we aligning on? Olly owns upsell + conversion, HiQOR owns routing + attribution, or Hybrid model (shared SMS/email engagement, coordinated touchpoints, unified tracking)?
  • What event-level data must Olly return to HiQOR for Attribution (who drove conversion), Billing (tier progression / revenue triggers), and Lifecycle tracking (started → quoted → bound)?
  • Do we support real-time upgrade paths (AD&D → life policy) within the same session, or defer to post-registration engagement?

When Does User Engagement Occur?

Timing of conversion touchpoints relative to the registration event

1. Registration

User completes race sign-up. Consent is captured at this moment.

2. Immediate Redirect

User is sent directly to an Olly-powered insurance flow during or right after checkout.

In-flow — ideal conversion

3. Post-Registration SMS / Email

Olly initiates outreach after registration. User re-engages on their own time.

Post-flow — primary today

Conversion Paths

Two implementation approaches — areas for alignment

A

In-Flow / Embedded

Requires partner integration

Ideal conversion path — insurance offer is part of the registration experience

Race Platform
Olly Embed
AD&D Bind
Upsell
B

Post-Registration

Lower dependency — near term

Scalable async approach — outreach after registration completes

Olly may initiate outreach and manage the full conversion lifecycle

Race Platform
HiQOR
Olly
SMS / Email
User
Bind
Controlled Environment

Gym / Microsite Flow (HiQOR-Controlled Environment)

Direct Integration Path

HiQOR controls the full experience — no partner dependency. Direct connection to Olly with no branching required.

HiQOR Microsite

  • Conversion timing control
  • UI and brand experience
  • No partner embed dependency
Direct — no branching

Olly Platform

  • AD&D binding
  • Conversion flow

Carrier Layer

Policy issuance and binding

  • Issues coverage, returns confirmation

System of Record + Data Requirements

HiQOR responsibilities and the required data contract with Olly

HiQOR Responsibilities

Identity & Matching

  • Lead UUID

    Primary identifier for all downstream systems

  • Email

    Secondary match key for reconciliation

Routing & Orchestration

  • Consent-based routing

    TCPA-compliant flow selection

  • Trigger AD&D vs Conversion

    Downstream flow management

  • Manage downstream integrations

    Orchestrates Olly and carriers

Reconciliation & Billing

  • Policy attribution

    Source of truth for partner credit

  • Revenue tracking

    Partner and channel reporting

  • Billing source of truth

    Canonical billing record

Required Data from Olly

Identity

  • UUID

    Must be returned — primary join key

  • Email

    Match key for deduplication

Application + Policy

  • Application status

    Started, completed

  • Policy status

    Submitted, bound, declined

  • Product type

    AD&D vs Life / Upsell

  • Premium

    For billing and attribution

Event Timestamps

  • Outreach initiated

    Timestamp — required

  • Application started

    Timestamp — required

  • Policy bound

    Timestamp — required

System Responsibilities

Clear ownership boundaries between HiQOR and Olly

HiQOR

System of Record
  • UUID / identity layer across partner and downstream systems
  • Payload transformation and normalization layer
  • Consent-based routing layer for allowed actions
  • Carrier data routing layer
  • Operational reporting layer

Olly

Execution Layer
  • AD&D binding layer
  • Digital insurance experience layer
  • Conversion/upsell execution layer
  • Engagement layer where permitted (SMS/email)
  • Returns event and status data to HiQOR

Flow Comparison

Key differences between Race and Gym integration paths

Race Flow

Partner-led
  • Partner-controlled UI and checkout
  • Limited embedding options without partner work
  • Handoff-based conversion — user leaves partner site
  • Post-registration SMS/Email is primary today

Gym Flow

HiQOR-led
  • HiQOR-controlled UI — no partner dependency
  • Flexible embedding and entry point control
  • Immediate handoff supported natively
  • Direct conversion paths with higher conversion potential