Webhooks & EventsSchema
lead.qualified Event Schema
Consume qualification scores, captured attributes, and the reasons behind a qualified outcome.
8 min readUpdated 25 Sept 20264 guides in this section
The lead.qualified event is emitted when an agent determines that a caller meets the configured qualification criteria. Treat the score as decision support and preserve the reasons that led to the outcome.
{
"id": "evt_01JZQ9A2QF",
"event": "lead.qualified",
"createdAt": "2026-09-25T10:34:00.000Z",
"data": {
"callId": "call_01JZQ6Y7AF",
"leadId": "lead_01JZQ8MT2K",
"qualified": true,
"score": 86,
"intent": "high",
"attributes": {
"budgetRange": "7500000-9000000",
"timeline": "30_days",
"financing": "pre_approved",
"preferredLocality": "example"
},
"reasons": [
"Budget and timeline met the configured threshold",
"Caller requested a property consultation"
],
"nextAction": "schedule_site_visit"
}
}Qualification fields
Recommended CRM update
- Resolve or create the CRM contact using a stable external identifier.
- Write captured attributes only when they are present and allowed by the field mapping.
- Attach the qualification score and reasons to a qualified activity or lead record.
- Create follow-up tasks for explicit commitments, not inferred preferences.
- Deduplicate using the event id and callId.
Threshold governance
Need implementation help?
Search the help center or talk with the OP26X telephony team.