When to Use / Why It Matters
The iVerify iFrame is useful when you want to collect insurance verification requests from your website visitors in a seamless, branded experience. Instead of directing users to a separate portal or requiring staff to manually collect information, the iFrame handles the intake process automatically and feeds submissions directly into your Dazos CRM.
This is particularly valuable for admissions teams and business development workflows, where speed and ease of access to benefits verification can directly impact patient intake outcomes.
How It Works
The iVerify iFrame is embedded into a page on your website using a snippet of code provided through your Dazos iVerify settings. Once embedded, it displays a form that visitors can fill out to request a Verification of Benefits (VOB).
Submissions made through the iFrame are sent directly into the Dazos CRM as leads or VOB records.
The form can be configured to show or hide specific fields, set default values, and reflect your facility's branding.
The iFrame will only function on domains that have been authorized in your iVerify settings.
Key Configuration Options
Field visibility: You can hide specific fields (such as BD Rep or Intake Stage) by setting default values for them, keeping the patient-facing form simple while still capturing required data.
Domain authorization: Only authorized domains can display and submit the iFrame. This is configured under Settings > CRM Settings > Integrations > iVerify iFrame Settings.
Styling: The iFrame will inherit your website's global font and styling rules. If fonts don't appear correctly, your web developer may need to define global styles (e.g., using
.bodyand.inputtags).
Tips & Notes
š” Tip: If you are embedding the iFrame on a new domain, make sure to authorize that domain in your iVerify iFrame Settings before testing. The form will not load on unauthorized domains.
ā ļø Note: Avoid placing both a custom-built form and the iVerify iFrame on the same page. Having duplicate forms can cause display and submission issues.
ā
Best Practice: Work with your web developer to ensure your site has global font and input styles defined so the iFrame inherits your site's appearance automatically.
Related Resources
How to Hide Fields and Set Default Values in iVerify iFrame (CRM)
Troubleshooting iVerify iFrame Font and Styling Issues (CRM)
Troubleshooting iVerify Submit New Lead Function Freezing Issues
How to Control iVerify Button Access by User Role (CRM)