Skip to main content

How to Map an Instant VOB 'Coverage Network' Field to a Custom Insurance Policy Field (CRM)

Overview

This guide walks through mapping the Instant VOB Coverage Network field (returned from Demographics + Eligibility) to a custom field on the Insurance Policy (Insurances) table — for example, a custom Policy Type field — so the value populates automatically whenever an Instant VOB is run.

Before You Begin, You'll need:

  • Admin permissions to access CRM Settings.

  • The destination custom field (e.g., Policy Type) already created and saved in the Insurance Policy (Insurances) table.

  • Access to Settings → Data Mapping → VOB Insurance Policy.

Steps

  1. Navigate to VOB Insurance Policy Mapping: Go to Settings → CRM Settings → Data Mapping → VOB Insurance Policy Mapping.

  2. Locate the VOB / Instant VOB → Insurance Policy section: Find the mapping section that controls how Instant VOB fields write data to the Insurance Policy record on the Account.

  3. Map the Coverage Network field: In this section, find the Instant VOB source field labeled Coverage Network (from Demographics + Eligibility) and map it to your destination field — for example, a custom field called Policy Type — in the Insurance Policy table.

  4. Save your configuration: Save the mapping settings to activate the data flow.

Screenshot


Verification / Expected Result

After completing these steps, when an Instant VOB is run, the Coverage Network value returned from the VOB response will automatically populate your custom Policy Type field (or whichever custom field you mapped it to) on the Account's Insurance Policy record.

Important Notes

  • Custom fields in the Insurance Policy table are supported as mapping destinations. The destination field does not need to be a standard system field — custom fields in the Insurance Policy (Insurances) table can be used successfully as the target for VOB field mapping.

  • The key requirement is that the destination field must exist in the Insurance Policy (Insurances) table. Fields in other tables (such as standard Account fields or Lead fields) cannot be targeted through this mapping.

Related Resources

Did this answer your question?