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.

json
{
  "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

FieldTypeDescription
callIdstringCall that produced the qualification result
leadIdstringPlatform lead identifier when available
qualifiedbooleanWhether configured qualification criteria were met
scorenumberModel or rule-based confidence score configured by the workspace
intentstringNormalized intent classification such as low, medium, or high
attributesobjectStructured values captured during the conversation
reasonsstring[]Human-readable explanation of the outcome
nextActionstringRecommended next workflow step
  1. Resolve or create the CRM contact using a stable external identifier.
  2. Write captured attributes only when they are present and allowed by the field mapping.
  3. Attach the qualification score and reasons to a qualified activity or lead record.
  4. Create follow-up tasks for explicit commitments, not inferred preferences.
  5. Deduplicate using the event id and callId.

Threshold governance

PracticeWhy it matters
Version qualification criteriaKeeps score meaning stable across campaigns
Store the score with the callAllows later analysis of threshold performance
Review false positives and false negativesImproves criteria without exposing unnecessary personal data
Keep mandatory disclosures outside scoringCompliance requirements should not depend on model confidence

Need implementation help?

Search the help center or talk with the OP26X telephony team.