Skip to content
English
Submit a ticket Sign in
  • There are no suggestions because the search field is empty.

Endorsement - Unit Addition [During Rewrites]ites]

Use this process when a client requests an additional unit (gateway) and the policy is still in the Rewrites pipeline.

Step 1: Block a gateway for the new unit

  1. Navigate to Gateways.

  2. Click the Available Gateways tab.

  3. Select a gateway where Availability Status = Available.

  4. Click the Availability Status field and choose Blocked for Endorsement.

A panel will open on the right side.

In the panel:

    • Set Type = Addition

    • Enter the Policy Number

    • Click Apply

    • Click Save


Result:
The gateway is reserved for the additional unit and linked to the policy.

Repeat this step for each additional unit requested.

Step 2: Confirm the policy location and update pipeline (if required)

  1. Open the policy:

    • Option A: Use Global Search


     

    • Option B: Navigate to the Policy object and search by policy number.

  2. Check the Policy Pipeline:

  3. If the policy is still in Rewrites, move it to:

    • Pipeline: New – Endorsement/Replacement

    • Stage: New


    • If already in New – Endorsement/Replacement, no change is needed.

Step 3: Verify prerequisites

  1. In the Overview, confirm:

    • Pre-requisites Status = All conditions met


If not:

    1. Complete any missing requirements.

    2. Go to the Policy Actions tab.

    3. Set Retest Pre-requisite = Yes

    4. Return to Overview and wait for the status to update.

 

Note:
This step triggers the endorsement process in the system.

Step 4: Update the gateway in Policy Center

  1. Open the policy in Policy Center.

  2. Add the new unit and assign the blocked gateway (from Step 1).

  3. Issue or update the policy as required.

Important:
The process continues once the gateway number syncs to the TelematicsDeviceNr field on the HubSpot Policy Vehicle. This sync may take some time.

Result:
Policy Center reflects the correct Addition gateway selection.

Step 5: Confirm automation progress

Once the gateway sync completes, the system will automatically:

  • Move the Policy Vehicle to the Endorsement pipeline.

  • Associate the blocked gateway

  • Move the Policy Vehicle to Gateway Assigned

  • Send a Welcome Email to the Primary Insured

To Verify The Email:

  • Scroll down to the All Contacts section under the Overview tab and navigate to the Primary Insured of the policy.


  • Navigate to the Activities section and scroll down. You will see a welcome email for Endorsements that has been sent to the primary insured's email.


Step 6: Post-email workflow (automated)

  • After the user completes the webflow, the Policy Vehicle stage will be updated to "Webflow Complete," and a task will be generated to ship the device, including the device and type details. This can be viewed under the Tasks section of the Activities tab.





  • Once the device is shipped, the UPS status will be synced to the "Tracking Status" property, and the Policy Vehicle stage will be updated to "Device Shipped."
  • Once the device is delivered, the UPS status will be synced to the "Tracking Status" property, and the Policy Vehicle stage will be updated to "Device Delivered."
  • Policy Vehicles will be enrolled in the installation tracker until the user installs the device.

 

  • Once the device is installed, the Telematics Device Activation Date will be synced from the database to HubSpot and displayed in the "Telematics Device Activation Date" property in the Policy Vehicle. The Policy Vehicle stage will then be updated to "Endorsement Complete."

Expected Outcome

For unit additions during Rewrites:

  • The policy is moved into the endorsement process

  • The new gateway is reserved and assigned

  • Client communication and fulfillment occur automatically

  • The process completes once the device is installed and activated