When This Information Matters
Understanding CTM's webhook behavior is important when:
You're planning webhook integrations and need to know when lead data becomes available
You want to trigger workflows based on live call transfers vs completed calls
You're troubleshooting why leads appear before call data is populated
You need to set realistic expectations for real-time lead processing
How CTM Webhooks Work
Initial Trigger: Immediate Lead Creation
When a call first lands in CTM, the system immediately fires a webhook that creates a Lead record in Dazos. This happens in real-time as soon as the call connects, not after the call ends.
What gets created:
Basic lead information (phone number, caller ID data)
Initial call timestamp
Source/tracking information
Update Trigger: Call-End Data Population
After the call concludes, CTM sends a second webhook that updates the existing Lead with captured call data.
What gets added:
Call duration
Audio recordings
AI transcripts and conversation data
Call outcome information
Important Notes
⚠️ No Additional Webhook Needed: The system already creates leads immediately upon call arrival. You don't need to add another webhook trigger for live agent transfers—the Lead record is created instantly when the call first connects to CTM.
💡 Two-Stage Process: This design ensures you have lead records available for real-time workflows while still capturing complete call data for follow-up processes.
✅ Expected Behavior: It's normal to see Lead records appear before call transcripts and AI conversation data are populated.
Related Resources
For more information about CTM integration and webhook configuration:
How to Set Up CTM Text Message Workflow Triggers in CRM
How to Configure CTM Star Rating Triggers for Selective Lead Transfer
Troubleshooting CTM Updates Overwriting Lead Fields