Policyholder address and contact change

How do we take a policyholder's address or contact change from any channel with identity verified and consent captured, and write it to policy administration?

Treat the change as a verified instruction. Callvu identifies the policyholder with the step-up verification the change warrants, prefills the policies and the contacts on file, takes the new address or contact details on a secure screen, classifies the consequences (a garaging or risk address change that re-rates an auto or property policy, a move to another state that changes the forms and the agent of record, a mailing-only change), captures the consent for electronic delivery where the contact method changes, routes a re-rating or a state move to the right desk in the Decision Desk, and writes the change to policy administration across every policy with a confirmation to both the old and the new contact. Live at Phoenix Insurance, under national rules outside the US.

Live at PhoenixSimpleCallvu moves: prefill, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The address was changed on the auto policy by a caller who was not the policyholder, and the renewal and the ID cards went to a stranger.

Today, without Callvu

An address change is the most common service request and the easiest to get wrong: taken on one policy and not the others, applied as a mailing change when it was a move that re-rates the car, made for a caller who knew the policy number, or applied without the consent that lets the insurer email instead of mail. The policyholder finds out at renewal.

The change carries security obligations (the insurer's information security program under the state's data security law requires authentication proportional to the risk of the change), rating consequences (the garaging and the risk address are rating factors the filed plan uses), licensing and form consequences for a move across state lines, and consent requirements for electronic delivery. The policy system must hold one address per role per policy, and every policy of the household must agree.

A small change with a long tail is exactly what a rule should handle.

How it runs

From the requestto the system of record.

A policyholder requests an address or contact change in any channel (the app, the website, a call, an agent, an AI assistant). Callvu identifies them and opens the change.

Policyholder: Verifies identity, enters the new details and consents on a secure screen, and receives confirmations.
Agent or service desk: Sends the link on a call and sees the change's status.
Underwriting or rating desk: Decides a re-rating or a state move in the Decision Desk where the rules require.
Callvu: Verifies, prefills, classifies, captures consent, routes and writes.

Verify and prefill
The policyholder is identified with the verification the change warrants (a one-time code to the contact on file, a document check for a change that moves the mailing address and the email together), and every policy and role on file (the named insured, the additional insureds, the mortgagee and lienholder addresses, the billing contact) is prefilled so the change can be applied consistently.
Capture the change and classify it
The new address or contact details are entered on a secure screen with the effective date and which policies the change applies to; the change is classified: a mailing-only change, a garaging or risk address change that re-rates an auto or property policy (with the new premium shown before confirmation), a move across state lines that changes the forms, the rates and the agent of record, or a contact method change that requires the electronic delivery consent.
Decide
A mailing or contact change inside the rules writes by rule; a re-rating above the tolerance, a state move, or a change on a policy with a pending claim or a recent fraud flag goes to the underwriting or service desk in the Decision Desk with the classification and only the allowed outcomes.
Write back and confirm
The change is written to policy administration on every policy and role selected, the re-rating endorsement issues where applicable, the electronic delivery consent is recorded, confirmations go to both the old and the new contact as a security measure, and the ID cards or documents that depend on the address are regenerated.

Where it ends: The change was made by a verified policyholder, classified for its rating and licensing consequences, consented where needed, and written consistently across every policy with confirmations to both contacts. The Decision Trace shows the verification level, the classification and any decision; the Audit Trace shows the request, the consent and the writes.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

US requirements shown. Phoenix runs this process under national rules outside the US; Callvu loads each market's rules as policies the same way.

NAIC Model #668 (Insurance Data Security Model Law) as adopted by the states: The insurer's information security program must include access controls and authentication proportional to the risk of the transaction; a change of address or contact that redirects policy documents is a high-risk change requiring verification of the policyholder's identity and a confirmation to the prior contact, and the event is logged for the program's monitoring.
State rating plans and the state insurance code on garaging and risk address, out-of-state moves and the producer of record: The garaging address and the risk location are rating factors under the filed plan, so a move re-rates the policy by endorsement; a move to another state requires the state's forms and rates and a producer licensed there, and may require the policy to be rewritten.
E-SIGN (15 USC 7001) and the state's electronic delivery rules for insurance documents: Policy documents may be delivered electronically only with the policyholder's affirmative consent after the required disclosures, with the hardware and software requirements stated and the right to withdraw; a change of email that enables electronic delivery captures or re-confirms that consent.

Company policies

The verification level matches the change; a change that redirects documents needs more than a policy number.
Every policy and role on file is shown so the change is applied consistently, with the policyholder choosing which.
A re-rating is shown before the policyholder confirms; a state move goes to the desk.
Policy administration in the policy system is the system of record, with confirmations to both contacts.

Controls

Risk-based identity verification.
Household and role prefill.
Change classification with re-rating and state move rules.
Electronic delivery consent capture.
Decision Desk for exceptions.
Multi-policy write with dual confirmations and document regeneration.

Clocks and deadlines

Effective date: The policyholder's chosen date, not before the request.
Confirmation: To the old and the new contact at write.
Re-rating endorsement: Issued at write with the premium change shown before confirmation.

Documents and checks

The verification record
The change with the policies and roles selected
The classification and the re-rating
The consent
The policy administration writes and the confirmations

In the Decision Trace

The verification level and why.
The classification.
Any decision and the person.

In the Audit Trace

The request with channel and time.
The consent with time.
Each write and each confirmation.

The handoff

Between the front doorand the back office.

The front door

Any channel; the policyholder verifies, enters and consents on a secure screen, sent as a link on a call.

The back office

The desk sees only re-ratings above tolerance, state moves and flagged policies; policy administration is written by the process.

The Decision Desk

A re-rating above tolerance, a move across state lines, or a change on a policy with a pending claim or a fraud flag goes to the underwriting or service desk in the Decision Desk with the classification and only the allowed outcomes.

Proof

Live at Phoenix.Published results only.

Each result is a published claim, with its code on agents.callvu.com, where its status, source and last verified date are kept.

Phoenix Insurance reaches more than 90% completion without human help.

INS-06 · Self-asserted · verified 2026-11-05

Phoenix Insurance has 40% fewer agent-led calls.

INS-02 · Self-asserted · verified 2026-11-05

Phoenix Insurance put more than 100 processes live in under three months.

INS-01 · Self-asserted · verified 2026-11-02

Questions

What buyers ask next,answered plainly.

How is the caller verified?

With verification proportional to the change: a one-time code to the contact on file for a mailing change, more for a change that redirects documents and the email together, as the data security program requires.

Does a move change the premium?

A change of garaging or risk address re-rates the policy under the filed plan; the new premium is shown before the policyholder confirms, and a move to another state goes to the desk.

Why are two confirmations sent?

One to the old contact and one to the new, so a change made by someone else is caught by the policyholder.

Related processes

Policy service requests completed by the customer Add or remove a vehicle or driver Name change on a policy Privacy and data access requests Compared with the alternatives Try it in the sandbox All insurance processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.