Product:
Dazos CRM
Question:
Under Leads, when my intake team enters information in the Financial Questions section of a lead or account, is it possible for that financial information to automatically map to the Insurance Information section, or does it have to be manually retyped in both areas?
Environment:
Module Affected: Leads / Accounts
Fields Involved: Financial Questions, Insurance Provider, Policy Number
User Type: Intake / Admin
Use Case: Automating data flow between Financial and Insurance sections for intake processing
Answer:
By default, financial and insurance information should map automatically when standard system fields are used. However, in some cases, customers might have replaced standard fields with custom text fields, which prevents proper mapping and disrupts integrations with Insurance Policies and Verification of Benefits (VOB) submissions.
If mapping is not occurring as expected, review the following:
✅ 1. Confirm field usage
Ensure that your Financial Questions section uses standard Dazos CRM fields, not custom ones.
For example:
Insurance Carrier Name → should use the Insurance Provider (picklist) field.
Insurance Policy Number → should use the Member ID (standard field).
If custom text fields are being used, automatic mapping and integrations will not function correctly.
🔄 2. Recommended Fix
If the customer has custom fields already in use:
Move the standard insurance fields from the Patient Demographics block to the Financial Questions section.
Migrate data from old (custom) fields into the correct standard fields using a Workflow Update Field Action:
Create a Time Interval workflow.
Use the Run Now option to execute the data migration immediately.
This process ensures that mappings, VOB submissions, and insurance integrations function as intended.
⚙️ 3. When to Escalate
If the mapping still fails after confirming standard field usage:
Submit a support ticket to verify whether backend field mappings or configurations were modified.
Additional Notes:
Renaming standard insurance fields may cause issues depending on how they are referenced internally.
Renaming typically does not break functionality in the Insurance Table, but could in the Account Module.
Removing standard insurance fields is not supported.
For consistency and reliability, it’s best to retain the default field names and structure.
Consider restricting edit access for these fields to prevent future disruptions.
User Case:
An intake team using custom financial fields noticed that insurance details entered during lead intake were not populating the Insurance Information section. Upon review, the issue was traced to custom fields replacing standard insurance fields, breaking the mapping logic. After migrating data to the correct standard fields using a workflow, mapping and VOB submissions functioned correctly.