How Connect works

Independent organisations.
One connected journey.

Each participant keeps its responsibilities. Connect coordinates the requests, evidence and outcomes that turn a partnership into a working customer experience.

Distributor

Customer channels, relationships, sales and service initiation.

Own users. Own permissions.

Send customer requests
Receive progress & outcomes

THE CONNECTING LAYER

Common orchestration controller

Carries choice, consent and supporting information. Routes the next task, records the response and returns the outcome to the relevant views.

Route→Record→Return

Relevant visibility. Clear next actions.

Insurer

Products, quotations, policy issuance and insurance decisions.

Own users. Own permissions.

Receive the responsible task
Return insurer decisions & outcomes

The customer experience

Choice, consent, payment and access to issued policy details—within the agreed partner journey.

Follow a customer

Ozoned Digital sets up both insurer and distributor organisations and initial access in a separate administration workspace. This is distinct from the controller’s operational coordination; setup administrators do not access customer or payment records.

Responsibility is part of the design

Know who can act.
Know who decides.

Participant	Owns or controls	In the connected journey
Insurer	Product terms, quotations, policy issuance and insurance decisions.	Returns offers and outcomes; reviews service, claims and cancellation requests.
Distributor	Customer channel, customer relationship and premium collection.	Introduces approved offers, supports customers and initiates sales or service requests.
Customer	Selection of insurer and cover, consent and payment choice.	Reviews the offer, confirms consent and accesses issued policy information.
Ozoned Digital	Organisation setup and access administration.	Proposes and reviews setup, supports access acceptance and manages activation. Setup administrators do not access customer or payment records.
Common orchestration controller	Shared request progress, routing, evidence and recorded outcomes.	Makes the next responsible action visible across the approved partnership; does not take insurance decisions or hold customer money.

Partnership setup & agreements

From two organisations
to one agreed proposition.

Organisation access, published products and permission to sell are separate foundations. The accepted relationship and bilateral agreement connect them.

Accept the relationship.
Agree what it permits.

After Ozoned sets up both organisations and initial access, the insurer and distributor accept their relationship. Together they define the products, activities and commercial terms the partnership permits.

Each organisation reviews and approves the arrangement independently. A published product becomes available for sale only within that approved scope and an approved customer journey.

Review product preparation

Two colleagues independently review agreement folios connected by an orange route

Set up both organisations

Ozoned provisions insurer and distributor organisations and initial access through separate setup review.

Accept the relationship

The counterpart accepts the invitation; both sides establish the intended activities and responsibilities.

Agree the permitted scope

Select approved product versions and define the commercial and operational terms.

Approve on both sides

Each organisation records its own approval before the arrangement supports a live journey.

What the agreement makes explicit

Products & versions: The exact approved product revisions and activities the distributor may offer.
Effective dates: When the agreement and relevant product permissions apply.
Markets & currencies: The agreed countries, customer scope and transaction currencies.
Responsibilities & data: Who carries out each activity and the permitted purpose of shared information.
Premium & commission: Distributor collection, full premium remittance to the insurer, and separately paid commission.
Settlement schedule: Amounts due, payment timing, confirmation requirements and agreed accounting handoff.

Independent approval remains visible. A change in terms or product version is reviewed through the applicable approval process. Published versions govern new work; existing requests retain their recorded context.

Connected progress

A request carries its context.

The same insurance request passes through distinct responsibilities. The relevant progress and outcome are visible without merging the organisations’ authority.

From customer choice
to insurer-confirmed issue.

Connect carries customer choice, consent and supporting information into the request. It routes the next task to the responsible organisation, records the response, and returns relevant progress and outcomes to the appropriate insurer and distributor views. Distributor payment is recorded separately from the insurer’s issuance result.

If the result is uncertain, the insurer checks its system before the request is retried. Progress should reflect what is known.

Follow the normal purchase journey

Shared request progressIllustrative purchase sequence

Customer choice & consent

The customer selects the insurer and accepts the offer.

Recorded

Distributor payment

The distributor confirms premium collection.

Confirmed

Insurer issuance

Only the insurer can confirm the policy result.

Confirmed

Policy access

The customer receives issued policy information.

Available

Organisation setup and access

Both organisations.
Separate access administration.

Ozoned sets up the insurer and distributor organisations and their initial administrators. Each organisation then manages its own authorised users and roles.

Propose setup

Ozoned prepares both organisations and their initial administrator access.

Review separately

An authorised reviewer validates the proposed configuration.

Accept access

The organisation’s administrator accepts access before activation.

Activate & manage

Activate approved access; record a reason when access is paused or restored.

Separate administration. Ozoned setup administrators manage organisation setup and access. They do not access customer or payment records.

Two practical routes to fulfilment

Coordinate with insurer systems
and authorised teams.

API execution

Connect sends the agreed operation to the insurer’s configured interface and records the returned result.

Send the operation with its request context.
Receive the insurer’s response.
Record the outcome and next action.

Authorised portal fulfilment

An authorised insurer user completes the operation through the agreed portal route and records the outcome.

Route work to the responsible insurer team.
Complete the operation in the agreed system.
Record the result against the request.

The fulfilment route is configured per operation. Connections require setup, testing and certification before live use. Uncertain outcomes require checking before retry.

A practical adoption path

Build on the systems
and teams you have.

Connect is designed to work alongside the insurer’s existing systems. Products and insurance decisions remain under insurer control, with operations fulfilled through agreed system connections or authorised portal processes.

Agree the proposition

Confirm participants, approved products, permitted activities and commercial terms.

Configure the journey

Set the customer event, channels, connections, responsibilities and controls.

Test the outcomes

Check customer choices, role permissions, responses, exception handling and financial records.

Approve launch

Complete independent reviews and required connection certification before live use.

Explore both sides of connectivity

Let’s shape the opportunity

Map your partnership.
Connect the work.

Start with the organisations, products and customer journey you want to bring together.

Discuss your partnershipStart a conversation with Ozoned Digital

Independent organisations.One connected journey.