This limitation becomes important when you're trying to generate reports that include specific insurance verification fields from Instant VOBs. You may notice that certain reports return no data even though the information appears to be available in individual VOB records.
​

The following fields from Instant VOBs cannot be pulled into CRM reports:

Instant VOB data for these specific fields is stored as a single JSON-encoded field in the database. Unlike Full VOBs, where each piece of information is stored in separate, reportable database fields, Instant VOB data is packaged together in a way that cannot be separated for reporting purposes.
​

This technical limitation means the CRM reporting system cannot access these individual data points from Instant VOBs, even though they are visible when you view the VOB record directly.
​

All Instant VOB information, including the fields listed above, remains fully accessible when viewing individual VOB records directly. The data is displayed properly within each VOB - it simply cannot be extracted for reports.
​

If you need these specific data points in your CRM reports, Full VOBs store this information in separate, reportable fields. Consider using Full VOBs instead of Instant VOBs when detailed reporting on these fields is required.
​

Work with your team to identify which VOB data points are essential for your reporting needs. You may be able to structure your reporting workflow to capture the necessary information through Full VOBs or other data sources.
​

⚠️ Important: This is a structural limitation of how Instant VOB data is stored and cannot be resolved through field mapping or configuration changes.
​

💡 Tip: If you're unsure whether to use Instant VOBs or Full VOBs for your workflow, consider your reporting requirements as part of the decision-making process.
​