Change policy coverage

Policyholders can change their policy coverage in the Consumer Service Portal (Service Portal) using the following steps:
  1. Initiate a coverage change.
  2. Enter coverage change details.
  3. Submit a coverage change.

The policyholder steps and the API calls required to complete each change request vary based on the type of policy coverage change.

Initiate Coverage Change

Initiating a coverage change starts with a policyholder deciding to change their coverage and selecting the change type. The types of policies that policyholder has determines the types policy change options that policyholder can select from. Once the Reason for Policy Change is selected, the API retrieves the associated policy change template which includes the information that the portal needs to update the policy.


Process to initiate a coverage change

Enter Coverage Change Details

Updating a coverage on a policy requires the consume to enter detail about the change. API calls then load fields specific to the change request.
Note: The actual field names and steps can vary based on portal configuration. For example, some portals might decide not to preview the impact that a coverage change has on the premium.
Coverage change request Process to enter coverage details
Add Vehicle
  1. The policyholder selects a Policy to Change and enters a Requested Effective Date.
  2. The policyholder enters the vehicle's make, model, and year.
    • If the policyholder knows the VIN, they enter the VIN number and then the portal calls the following API to list the models:
      GET /vehicleModels
      Then, the policyholder selects the vehicle from the listed options.
    • If the policyholder does not know the VIN, they enter a Year and then the portal calls the following API to list the makes: 
      GET /vehicleManufacturers
      After the policyholder selects a Make, the portal calls the following API to list models: 
      GET /vehicleModels
    • If the policyholder cannot find their car using the methods above, the portal displays text fields for the policyholder to enter the vehicle Make, Model, and Year.
  3. The policyholder enters additional vehicle details and proceeds to the next step.
  4. The portal calls the following API to preview the premium change: 
    POST /customerPolicyChangePreSubmit
  5. The portal calls the following API to display the existing premium: 
    GET /policies/systemId/full
Remove Vehicle
  1. Policyholder selects Policy to Change.
  2. The portal calls the following API to load the list of existing vehicles on the policy:
    GET /policies/systemId/lines/PersonalAuto/risks
  3. The policyholder enters the Requested Effective Date and Reason for Removal. They also select the Vehicle to be removed.
  4. The portal calls the following API to preview the premium change: 
    POST /customerPolicyChangePreSubmit
  5. The portal calls the following API to display the existing premium: 
    GET /policies/systemId/full
Add Driver
  1. The portal displays all the driver fields.
  2. The policyholder enters the information about the new driver.
  3. The portal calls the following API to preview the premium change: 
    POST /customerPolicyChangePreSubmit
  4. The portal calls the following API to display the existing premium: 
    GET /policies/systemId/full
Remove a Driver
  1. The portal calls the following API to load a list of existing drivers on the policy:
    GET /policies/systemId/drivers
  2. The policyholder enters the Requested Effective Date and Reason for Removal. They also select the Driver to be removed.
  3. The portal calls the following API to preview the premium change: 
    POST /customerPolicyChangePreSubmit
  4. The portal calls the following API to display the existing premium: 
    GET /policies/systemId/full
Change Billing/Mailing Address
  1. The portal completes the steps to Get policyholder address information.
  2. The policyholder enters the Requested Effective Date, and Reason for Change. They also select the Address to be changed.
  3. The policyholder enters the new address.
Change Vehicle Finance Company
  1. The policyholder selects a Policy to Change.
  2. The portal calls the following API to load the interest types: 
    GET /coderefs/UW/ai/interest-type/vehicle-finance-company
  3. The portal calls the following API to load the list of finance companies available on the policy:
    GET /policies/systemId/additionalInterests
  4. The policyholder enters the Requested Effective Date and selects the Vehicle Finance Company to be Changed. They also enter the Reason for change.
  5. The policyholder provides details on the new finance company.
Remove Vehicle Finance Company
  1. The policyholder selects a Policy to Change.
  2. The portal calls the following API to load the list of finance companies available on the policy:
    GET /policies/systemId/additionalInterests
  3. The policyholder enters a Requested Effective Date and Reason for Removal. They also select a Vehicle Finance Company to be Removed.
Add Vehicle Finance Company
  1. The policyholder selects a Policy to Change.
  2. The portal calls the following API to load the interest types: 
    GET /coderefs/UW/ai/interest-type/vehicle-finance-company
  3. The portal calls the following API to load the list of vehicles available on the policy:
    GET /policies/{systemId}/lines/PersonalAuto/risks
  4. The policyholder picks a vehicle from Select Finance Vehicle.
  5. The policyholder enters the fields in the New Vehicle Finance Company Information panel.
Change Property Deductible
  1. The policyholder selects a Policy to Change.
  2. The portal calls the following API to load the policy details: 
    GET /policies/systemId
  3. The policyholder selects a New Deductible and Requested Effective Date. They also can enter a Reason.
  4. The portal calls the following API to preview the premium change: 
    POST /customerPolicyChangePreSubmit
  5. The portal calls the following API to display the existing premium: 
    GET /policies/systemId/full
Change the Property Mortgagee
  1. The policyholder selects a Policy to Change.
  2. The portal calls the following API to load additional interests on the policy:
    GET /policies/systemId/additionalInterests
  3. The policyholder selects a Requested Effective Date, a Mortgagee to be changed, and then clicks Next.
  4. The portal calls the following API to load the mortgagee interest types: 
    GET /coderefs/UW/ai/interest-type/mortgagee
  5. The policyholder selects a Reason for Change and enters additional fields in the Current Mortgagee Information panel.
Add Property Mortgagee
  1. The policyholder selects a Policy to Change.
  2. The portal calls the following API to load the building risks associated with the policy: 
    /policies/systemId/lines/Homeowners/risks
  3. The policyholder enters the Requested Effective Date, selects one of the Properties, and clicks Next.
  4. The portal calls the following API to the load the mortgagee interest types:
    GET /coderefs/UW/ai/interest-type/mortgagee
  5. The policyholder enters the Reason for Change and the fields in the New Mortgagee Information panel.
Remove Property Mortgagee
  1. The policyholder selects a Policy to Change.
  2. The portal calls the following API to load the additional interests on the policy: 
    GET /policies/systemId/additionalInterest
  3. The policyholder enters the Requested Effective Date and a Description. They also select a Mortgagee to be Removed.
Request New Property Coverage
  1. The policyholder enters the Requested Effective Date and a Description of the items they want to cover and their items values.
  2. If the policyholder wants to add pictures of the items, see Add attachments in a service portal.

Submit Coverage Change

Submitting a coverage change requires a policyholder to submit their request and then the portal calls an API to update the policy.
Process to submit a coverage change