Skip to content
vox.

Platform

Your systems. Your data. Vox agents.

Connect existing infrastructure. Unlock intelligence. Put agents to work with customer-controlled access, permissions and human oversight.

The operating model

Your systems. Your data. Vox agents.

Vox is being designed to connect to your existing technology stack through standardised APIs and MCP-compatible interfaces. Your organisation retains control of its data, access permissions and business rules.

01Policy systems
02CRM platforms
03Email & documents
04Data infrastructure
vox.

Intelligence layer

Products · Context · Business rules
Insurance-specific agents
Intelligence
Execution
Growth

Authorised business outcomes

Intended product architecture · connectivity and execution in development
  1. 01

    Connect

    Connect existing policy administration systems, CRM platforms, email, documents and data infrastructure through agreed interfaces.

  2. 02

    Understand

    Agents are being developed to interpret your products, policies, customers, distribution relationships and operational workflows.

  3. 03

    Execute

    Develop agents that prepare actions, automate approved workflows and surface management intelligence within your controls.

Current alpha: enquiry intake, supported fact extraction and activity association. Customer-managed onboarding and the broader operating model are in development.

The insurance-specific work

Useful context takes
more than extraction.

01

Start with agreed sources

An enquiry email and its supporting documents provide the starting facts. The alpha supports intake and supported fact extraction; the connected mailbox and access available are agreed for each scope.

Alpha scope / intake and supported extraction

02

Connect the right records

Associate current activity with the relevant client and risk. Broader links between intermediary, submission, policy and market records are a design direction: similar names alone must not decide the match.

Alpha / activity association · broader relationships in development

03

Keep the evidence attached

The proposed context carries source references, dates and document versions alongside insurance fields. Contradictory territory details, an outdated market response or missing claims history should remain visible for review.

Design direction / provenance, time and conflict handling

04

Carry reviewed knowledge forward

Stored conversation, document and activity records exist in the product. Reusing linked placement outcomes, market responses and validated corrections in later tasks is not yet verified for this alpha. An incoming document is evidence; organisational context is the reviewed set of facts and relationships built around it.

Broader historical context and correction reuse / in development

05

Separate a draft from authority

The intended workflow can suggest an owner, prepare an information request and propose a pipeline update. Your team reviews decisions and approval points. Preparation and authorised execution remain in development; the example does not send messages or update your system.

Preparation and execution / in development

From information to a supported next step

One enquiry.
The context around it.

Illustrative example · fictional data
Interactive illustration, not a live product connection.

Intake and supported extraction: in alpha. Historical-source combination: in development.

S1

Introducer email

Meridian Broking introduces Northstar Marine Ltd. Cargo enquiry: UK and European trading routes. Please progress the submission.

S2

Attached submission · v2

Northstar Marine Ltd · Marine cargo. Trading territory: worldwide. Latest claims history: not attached.

S3

Prior submission · v1

Northstar Marine Ltd · Marine cargo. UK and European routes. Claims information covers 2022–2024 only.

S4

Dated market response

Harbour Market: please confirm territories and provide an up-to-date claims record before further consideration.

Customer-controlled connectivity

Connect your systems. Keep control.

Enterprise software often depends on bespoke implementation and ongoing maintenance. Vox is being designed around standardised connectivity, customer-managed integration and reusable insurance-specific agents.

Your technical team would connect existing systems through defined interfaces, while your organisation controls source access, product logic and approved workflows.

01Customer-controlled data access
02Standardised APIs and MCP-compatible interfaces
03Configurable product and workflow logic
04Reusable insurance-specific agents
05Permissions, approvals and auditability
06Architecture designed to minimise bespoke work

Intended architecture. Interfaces, onboarding and controls require scoping and validation. Integrations are not instantaneous, fully self-service or universally supported today.

Explore the platform direction

Current alpha & evaluation

Prove usefulness.
Then expand.

The public alpha scope is intake, supported fact extraction and activity association. Broader preparation, management intelligence and execution are in development. The interactive example is fictional and is not a performance evaluation.

For an agreed pilot, evaluate correct client and risk associations, source-supported facts, material omissions and the human review required. Compare time to a review-ready output with the same workflow’s manual baseline.

No approved measured alpha results are published here. An evaluation needs the workflow, period, sample size and denominator, method, baseline and exceptions. Faster preparation alone would not demonstrate better conversion or distribution.

Put intelligence to work.

Discover what Vox could unlock within your organisation.