Skip to content

Policies

Bound business that stays connected to its history.

A policy record in i23CRM carries the submission, quote, insured and servicing history behind it.

Quote01
Policy02
Documents03
Renewal04
Claim05

The problem

Bound business often becomes a dead end.

  • Policy data is stored separately from the deal that created it
  • Servicing activity is scattered across inboxes
  • Renewal work starts from scratch each term
  • Claims teams can't see the operational history

The approach

One policy record, connected in both directions.

Policies link back to the submission and quote that produced them, and forward to the renewals, claims, documents and activities that follow.

Policy records

Term, premium, insured and carrier held in a structured record.

Linked origin

The submission and selected quote remain attached.

Documents

Policy documents live with the policy, not in a shared folder.

Activities

Servicing notes and interactions stay on the record.

Renewals

Renewal work is created against the policy it belongs to.

Claims

Claims reference the policy and the insured directly.

Workflow

How it moves through the platform

  1. Bind
  2. Issue
  3. Service
  4. Renew
  5. Claims
  • Complete operational history per policy
  • Servicing context available to the whole team
  • Renewals that start from real data
  • Claims handled with the policy in view

See i23CRM in action.

Tell us a little about your MGA and we'll show you how i23CRM fits your workflow.