Starting event & channel
Choose the event that opens the journey and its approved app, website or assisted-sales channel. Define the permitted data and field mappings.
Platform capabilities
The depth behind
a connected partnership.
Products, journeys, fulfilment, service and financial records belong to one operating story. Explore the capabilities that connect the work while keeping authority clear.
Product preparation
Bring approved products into the partnership.
Import fields available from the insurer source. Complete missing information under insurer control, then obtain independent approval before publication.
- Insurer-controlled product information
- Completion of missing source fields
- Review by a second authorised insurer person
Product preparationIllustrative operational view
Own permissionsImport source informationAvailable fields are retained
ImportedComplete & reviewInsurer preparation, separate approval
ControlledCapabilities shown as an illustrative workflow.
Journey Planner
Configure the journey around the partnership.
Start from a reusable template, then set the event, channel, approved offers, human-review conditions, consent and notifications. Test the configuration and obtain independent review before publication.
- Approved product versions and insurer options
- Review conditions, consent and response deadlines
- Versioned templates and controlled publication
Journey PlannerIllustrative operational view
Own permissionsCustomer momentPartner app, website or assisted interaction
In contextChoice & consentCustomer chooses insurer and cover
RecordedCapabilities shown as an illustrative workflow.
Request coordination
Keep progress, evidence and outcomes together.
Carry customer choice, consent and supporting information, route the next task, record the response and return outcomes to the relevant views. If an outcome is unknown, verify it before retrying.
- Progress linked to the insurance request
- Evidence available to the responsible role
- Outcome checking before a retry
Request coordinationIllustrative operational view
Own permissionsRoute next actionSend work to the responsible organisation
AssignedVerify an unclear outcomeInsurer checks its system before retry
Check requiredCapabilities shown as an illustrative workflow.
Policy servicing
Connect ongoing help to the issued policy.
Coordinate policy service, claim and cancellation requests with their evidence and insurer decisions. Claims payment follows its own approval.
- Requests linked to an issued policy
- Insurer review and recorded decisions
- Separate claims payment approval
Policy servicingIllustrative operational view
Own permissionsPolicy-linked requestDetails and supporting evidence
SubmittedInsurer reviewAssess and record the decision
With insurerCapabilities shown as an illustrative workflow.
Financial records
Keep the partnership’s financial flow visible.
Maintain premium, approval and payment records. Support accounting exports while retaining full premium remittance and separate commission payment.
- Distributor premium collection records
- Gross remittance and separate commission
- Accounting exports for financial operations
Financial recordsIllustrative operational view
Own permissionsGross premium remittanceDistributor to insurer
RecordedSeparate commissionInsurer to distributor on agreed terms
Separate flowCapabilities shown as an illustrative workflow.
Governance & control
Make authority part of everyday work.
Users work within their organisation and approved role. Configuration moves through validation and independent review, with actions and outcomes recorded.
- Organisation and role permissions
- Independent preparation and approval
- Recorded actions and governed access
Governance & controlIllustrative operational view
Own permissionsOrganisation accessApproved roles within each workspace
ScopedRecorded outcomeWho acted, when and with what result
TraceableCapabilities shown as an illustrative workflow.
Journey Planner
Reusable foundations.
Purposeful configuration.
Business teams can start from acquisition, service or referral templates, then configure the supported steps for a specific partnership.
Shape the experience.
Keep the important controls.
Choose the customer event and channel, link the approved products and insurer options, and define the information and consent each step needs. Add supported human-review conditions and agree how customers and teams hear back.
The planner makes stage ownership and next actions visible. Configuration is tested and independently reviewed before publication; insurer authority and required insurance and financial controls remain in place.
Compare three configured customer moments
Products & insurer options
Link approved product versions within the agreement. Configure one insurer or customer choice between the approved offers.
Human review & deadlines
Set supported referral conditions, responsible roles and response deadlines. Required reviews are completed before the next protected step.
Consent & communication
Configure consent, notification text and channels, document visibility and controlled follow-up attempts. Keep customer choice explicit.
01
Start from a template
Reuse a supported acquisition, service or referral pattern.
02
Configure the partnership
Set approved dependencies, fields, decisions and communications.
03
Test & review
Simulate the configured dependencies and submit for independent review.
04
Publish a version
New work uses the approved configuration; existing requests retain their version context.
Templates and settings work within supported journey stages and controls. System integrations still require agreed setup, testing and certification.
Connectivity and fulfilment
The right route
for each operation.
Insurers may execute through APIs or authorised portal workflows. The route is agreed and configured for the operation being performed.
01
Receive the request
Carry the permitted operation, customer choice and relevant context.
02
Call the insurer interface
Use the configured integration for this operation.
03
Record the response
Link the insurer’s result to the request and its next action.
04
Verify uncertainty
If the outcome is unclear, check before a retry.
01
Receive the request
Carry the operation and evidence into the agreed fulfilment process.
02
Assign insurer work
An authorised insurer user takes the required action.
03
Confirm the result
Record the outcome from the insurer’s system against the request.
04
Return the outcome
Update progress and the customer-facing status appropriately.
Connections require setup, testing and certification before live use. Imported product coverage and operation support depend on the insurer source and adapter. The mock does not represent a live connection.
Distributor channel connections
Connect the customer channel
in both directions.
Distributor ingress and insurer fulfilment have separate connection settings and approval. Together they carry the customer request to the responsible insurer and bring the result back.
Agree authentication, permitted data, response handling and operational ownership during implementation. Each channel and insurer connection needs setup, testing and certification; a configured example is not a live connector.
Financial coordination
One clear flow.
Separate financial responsibilities.
The customer pays the distributor. The distributor remits the full premium. The insurer pays commission separately under the agreed terms.
Customer
Pays the premium to the distributor.
Premium →Distributor
Remits the full premium to the insurer.
Full premium →Insurer
Pays commission separately on agreed terms.
Commission →Distributor
Receives the agreed commission.
Connect tracks the process. Ozoned does not hold customer money. Premium and commission payment dates follow the terms agreed between the organisations.
From collected premium
to a traceable financial record.
Link collection records and amounts due to the approved partnership. Keep payment preparation, approval and receipt confirmation visible, alongside the separate commission obligation.
Connect coordinates these partnership records alongside the Finance module. It does not replace the Finance module or take custody of funds.
Collection & amounts due
Record customer premium collected by the distributor and the full amount due to the insurer, linked to the partnership and its agreed schedule.
Payment approvals
Prepare the full-premium payment record and obtain the required financial approval. Commission remains a separate insurer-to-distributor obligation.
Receipt confirmations
Record remittance evidence and insurer receipt confirmation. Track the insurer’s separate commission payment and distributor confirmation against agreed terms.
Accounting exports
Export linked records for financial operations and reconciliation. Agree account mappings, receiving systems and handoff controls during implementation.
Governance and control
Clear access.
Accountable action.
Separate workspaces
Insurer, distributor and Ozoned setup administration users work within their own organisations and approved roles.
Independent approval
Product publication and governed configuration include a separate review step. Preparation and approval remain distinct.
Recorded progress and outcomes
Keep evidence of who acted, when and with what result. Resolve uncertain outcomes before retrying an operation.
Governed organisation access
Organisation setup is proposed, reviewed and accepted before activation. Pause and restore actions carry a recorded reason.
Ozoned setup administrators do not access customer or payment records. The customer portal remains a distinct customer experience.
Your questions
A few things
worth clarifying.
Clear answers before you plan your partnership.
What does the platform automate?
Connect coordinates the agreed journey steps, request state and routing. API execution is used where configured and certified; authorised insurer teams may fulfil other operations through the agreed portal route. Insurance decisions remain with the insurer.
What can we configure for each partnership?
Business teams can configure the starting event and channel, approved product versions, insurer options and customer choice, required fields, supported human-review conditions, consent, notifications and response deadlines. Reusable templates provide a starting point. The configuration is tested and independently reviewed before publication.
Can we connect to our financial core?
Connect supports accounting exports. Your financial integration, required mappings, controls and implementation scope should be agreed against the receiving system and business process.
What needs to be agreed before launch?
The products, partners, customer journey, permissions, fulfilment routes, financial responsibilities and implementation scope. System connections need setup, testing and certification before live use.
Let’s shape the opportunity
Start with the proposition.
Build the right operating model.
We’ll explore the capabilities and connections your partnership needs.
Discuss your partnershipStart a conversation with Ozoned Digital