When to Use / Why It Matters
This information applies when:
Your CallRail-integrated webforms are receiving submissions but not creating leads in Dazos
You are setting up new webforms to integrate with CallRail
You are auditing existing forms for field mapping compatibility
You are configuring insurance-related fields on webforms
Requirement 1: Separate First Name and Last Name Fields
CallRail cannot natively map a single Full Name field to the lead level in Dazos. If your webforms use a combined Full Name field, submissions will not correctly populate the name fields on the Lead record.
Your webforms must use two separate fields:
First Name
Last Name
If Splitting the Field Is Not Feasible
If your website cannot be updated to use separate First and Last Name fields, a custom Full Name field can be created in Dazos as a workaround. However, this requires staff to manually split the name into First Name and Last Name fields after the lead is created in the system.
⚠️ Note: The manual split workaround adds ongoing administrative overhead. Wherever possible, updating the webform to use separate First Name and Last Name fields is the recommended approach.
Requirement 2: Consistent Phone Field Label Across All Forms
Phone number fields must use the exact same label across every webform that is mapped to CallRail. Inconsistent labels — such as using Phone on some forms and Phone Number on others — will prevent the field from mapping correctly to the Lead record.
✅ Best Practice: Standardize all phone fields across your webforms to use a single consistent label, such as Phone Number, to match how the field is mapped in Dazos.
Requirement 3: Insurance Policy Field — Use a Text Field on the Webform
If your webforms include an insurance policy field, it should be configured as a text field on the webform — not a global picklist. Using the global picklist on the webform can cause conflicts during form submission.
Once the lead is created in Dazos, staff can manually update the insurance field to the correct value from the global picklist for accurate insurance verification.
💡 Tip: This approach ensures the lead is created successfully from the form submission, while still allowing staff to apply the correct standardized picklist value inside the CRM.
Summary: Field Mapping Requirements at a Glance
Field | Requirement | Notes |
Name |
Use separate First Name and Last Name fields | CallRail cannot natively map a single Full Name field; a custom Full Name field is available as a workaround but requires manual splitting |
Phone | Use a consistent label across all forms (e.g., Phone Number) | Mismatched labels (e.g., Phone vs. Phone Number) will break the mapping |
Insurance Policy |
Use a text field on the webform | Avoids conflicts with the global picklist; staff manually update to the correct picklist value after lead creation |
Tips & Notes
⚠️ Important: All three requirements above must be met for webform submissions to reliably create leads in the Dazos Leads module. Missing any one of them can cause submissions to fail or fields to remain blank on the lead record.
💡 Tip: After making any changes to your webform field labels or structure, submit a test form and verify that a lead is created in Dazos with all fields populated correctly before going live.
✅ Best Practice: When setting up new webforms for CallRail integration, configure First Name, Last Name, and a consistently labeled Phone Number field from the start to avoid mapping issues later.
Related Resources
How to Map Webform Fields From CTM to Dazos (CRM)
How to stop CTM/CallRail Caller ID from populating or overwriting City, State, and Zip fields (CRM)
Understanding How Mandatory Fields Work for Webforms vs CRM Records (CRM)