This article explains what the integration does support, why this limitation exists, and what options are available to you.
When This Limitation Applies
You will encounter this limitation when attempting to:
Map CallRail Detail Tags to a custom text or picklist field in the Leads, Call Logs, Patients, or Intake Opportunities modules
Use an incoming CallRail tag value as a condition or trigger in a Dazos CRM workflow
Automate follow-up actions or pipeline changes based on specific CallRail tag strings
How CallRail Tags Currently Work in Dazos CRM
When a call comes in through CallRail with associated tags, the integration receives the tag data and appends it directly to the lead as a record-level tag. This means the tag appears on the lead record itself, but the tag value is not extractable into a standalone CRM field.
Due to how the CallRail integration payload is structured, the tag data cannot be:
Mapped to a custom text field
Mapped to a custom picklist field
Used as a workflow trigger condition in any CRM module
This behavior applies across all modules, including Leads, Call Logs, Patients, and Intake Opportunities.
Why This Limitation Exists
The CallRail integration delivers tag data in a notification format that is designed to append tags directly to records. The integration payload structure does not expose tag values in a way that allows the CRM to extract and route them into discrete custom fields or evaluate them as workflow trigger criteria.
This is a current platform limitation and not a configuration issue. No amount of field mapping or workflow adjustment on the front end will resolve this behavior.
What You Can Do
Submit a Feature Request If this functionality is important to your team's operations, you can request that our product team consider it for a future integration enhancement. To submit a feature request, contact Dazos Support and provide the following details:
A description of the specific tags you want to capture
Which modules you need the field to appear in (e.g., Leads, Intake Opportunities)
The workflows or automations you intend to trigger based on the tag value
⚠️ Note: Submitting a feature request does not guarantee the feature will be built. Our development roadmap is planned quarters in advance and is prioritized based on the volume and frequency of customer requests. If the feature is prioritized, the team will follow up directly.
Use Record-Level Tags as a Manual Reference While tag values cannot drive automated workflows, they are still visible on the lead record as standard CRM tags. Your team can use these tags as a manual reference when reviewing records, even if automation cannot be triggered from them at this time.
Tips & Notes
💡 Tip: If you are exploring other ways to capture call categorization data for automation purposes, consider whether your team can log this information manually into a custom field at the time of call review, then trigger workflows based on that field update instead.
⚠️ Warning: Creating custom fields and mapping them in the CallRail integration settings will not cause tag data to populate those fields. This has been confirmed through investigation — the tag payload is not delivered in a way that supports this mapping.