Overview
This article explains the current limitations of mapping demographic data — such as Gender — returned from a Verification of Benefits (VOB) back to the Lead or Account record in Dazos CRM. If you are expecting VOB response data to automatically update standard Account or Lead fields, please read this article before submitting a support request.
When This Matters
This limitation becomes relevant when your team runs an Instant VOB and expects demographic information returned in the VOB response (for example, the patient's Gender) to automatically populate the corresponding field on the Account or Lead record. Currently, this automatic update does not occur.
How VOB Field Mapping Currently Works
Fields returned from an Instant VOB can be mapped to insurance fields within the insurance table on the Account record. This allows VOB response data to populate insurance-related fields such as plan details and coverage information.
However, there is currently no setting that allows insurance table fields to be mapped to standard Account or Lead fields. The only fields that are automatically written from the insurance table to the Account record are Payer Code and Member ID — and these are hardcoded by the system, not configurable.
As a result, demographic data such as Gender returned from a VOB response cannot currently be automatically pushed to the Gender field on a Lead or Account record.
What the Reference Field Workaround Does (and Does Not Do)
A common question is whether adding a Reference Field in the VOB module can solve this. It is important to understand what this approach actually does:
A Reference Field added to the VOB module and pointed at the Account's Gender field will display the Gender value already stored on the Account — it mirrors the Account field within the VOB view.
This approach does not flow data returned from the VOB response back into the Account. The data direction is Account → VOB display only, not VOB response → Account.
In other words, the Reference Field is useful for surfacing existing Account data within the VOB, but it does not solve the use case of writing VOB-returned demographic data back to the Account or Lead record.
Summary of Current Behavior
Data Flow | Supported? |
Instant VOB response fields → Insurance table on Account | ✅ Yes — mappable |
Insurance table fields → Standard Account fields (e.g., Gender) | ❌ No — not configurable |
Payer Code and Member ID → Account (from insurance table) | ✅ Yes — hardcoded automatically |
VOB demographic data (e.g., Gender) → Account Gender field | ❌ Not currently supported |
Reference Field in VOB → Displays Account Gender in VOB view | ✅ Yes — but reads from Account, does not write back |
Tips & Notes
⚠️ This is a current product limitation, not a configuration error or bug. It cannot be resolved through field mapping or workflow configuration at this time.
💡 If this functionality is important to your workflow, contact Dazos Support to submit a formal feature request. Describe your specific use case so the development team can evaluate it alongside other enhancement requests.
How to Submit a Feature Request
If the ability to map VOB demographic fields (such as Gender) back to Account or Lead fields is critical to your team's workflow, you can request this as a product enhancement.
Contact Dazos Support and describe your use case in detail.
Our team will log it as a formal feature request for review by the development team.
Submission does not guarantee the feature will be added or provide a delivery timeline, but all requests are reviewed.
Related Resources
Contact Dazos Support — not found in Knowledge Center; this isn't a KB article. Needs a real support-contact URL (or should be removed from Related Resources, since that section is meant for deeper docs rather than a contact action).