Skip to content
debarko.deproductspherainsurance

Insurance CRM · powered by Phera

Auto, home, and life stay three policies and one relationship

The textbook case for "one person, many funnels" — plus the audit trail a compliance team already wishes it had.

200 monthly searches for "CRM software for insurance brokers"

A client's auto policy, home policy, and life policy are three Deals in three Pipelines, each run by its own underwriting desk with its own stages. But Contact.owner — the trusted advisor the client actually talks to — stays the same person across all three, even as different specialists work each Deal.

That split is deliberate: Salesforce calls it account owner vs. opportunity owner, Pipedrive calls it person owner vs. deal owner. Phera implements the same three-layer shape and lets a workspace pick which layer is required, shown, and used for assignment — a setting, not a fork of the codebase.

A renewal cross-sell that a single lead-status system can't trigger

A workflow watches for a Deal in the Auto pipeline entering the Renewal_due stage while the same Contact has no open Deal in the Home pipeline — and enrolls them in a bundling-discount sequence. This context — what's open, what's conspicuously missing — doesn't exist in a system that already marked the auto policy "closed" the day it was bound.

How it maps to Phera

Pipelines

Auto

Quoted → Bound → Active → Renewal due

Home

Quoted → Bound → Active → Renewal due

Life

Application → Underwriting → Issued → Active

Channels

  • Phone — renewal calls, recorded and transcribed
  • Email — policy documents
  • WhatsApp — claims status updates

Workflow

trigger — deal.stage_changed to Renewal_due on Auto, and no open Deal exists on Home

action — enroll the contact in a bundling-discount WhatsApp sequence

Ownership — contact_centric

One advisor stays Contact.owner across every policy line — the relationship survives even as different desks work each Deal. Every policy change and communication writes an immutable AuditEvent: an E&O defense file that builds itself instead of getting assembled after a complaint arrives.