Skip to main content

iVerify Insurance Table: Group ID Field Mapping Limitations (CRM)

This article explains the current limitations of Group ID field mapping in the iVerify Insurance Table within Dazos CRM. If you are expecting Group ID to be automatically populated from insurance source data, please read this article before submitting a s

When This Matters

This limitation is relevant when your team is reviewing the iVerify Insurance Table on a Lead or Account record and expects the Group ID field to be automatically filled in based on insurance source data — for example, after running a Verification of Benefits (VOB) or receiving data from an insurance integration.

What iVerify Currently Auto-Maps

The iVerify Insurance Table currently supports automatic field mapping for the following fields only:

  • Member ID

  • Insurance Provider

These two fields are populated automatically from the insurance source data when available.

Group ID Mapping — Current Limitation

Group ID is not a standard field that can be directly mapped from insurance source data into the iVerify Insurance Table. This means the Group ID will not auto-populate, even when the source data contains that information.

⚠️ Note: This is a current product limitation, not a configuration error or bug. It cannot be resolved through field mapping adjustments at this time.

What to Do Instead

Until an alternative solution is available, users should manually enter the Group ID directly into the designated Group ID field in the iVerify Insurance Table on the relevant Lead or Account record.

What's Next

The Dazos team is actively exploring alternative options to streamline the Group ID entry process in a future update. We will communicate any changes through our release notes.

💡 Tip: If this limitation significantly impacts your team's workflow, contact Dazos Support to submit a formal feature request. Providing details about your specific use case helps the development team prioritize enhancements.

How to Submit a Feature Request

  1. Contact Dazos Support and describe your use case for automatic Group ID mapping.

  2. Our team will log your request as a formal feature request for review by the development team.

  3. Feature requests are evaluated alongside other enhancement requests. Submission does not guarantee the feature will be added or provide a delivery timeline, but all requests are reviewed.

Related Resources

  • VOB Demographic Data and Account Field Mapping — Current Limitations (CRM)

  • Insurance Payer Code Mapping Between Dazos and Alleva EMR — Current Limitations (CRM)

  • Troubleshooting Reference Fields Not Showing Insurance Table Data in Workflow Tokens (CRM)

Did this answer your question?