Lead qualification

Goal: every inbound lead (contact form, chat, e-mail) gets a purchase-intent score, a priority, a lead score and a destination team in a few hundred milliseconds, and obvious spam never reaches your CRM. The template combines three patterns: intent routing, confidence-gated routing and composite scoring.

Create the decisionCopy Anchor Link

In the app, open Templates → Lead Qualification → Create decision. The draft contains:

Test it in the Playground, then Deploy v1.

Call itCopy Anchor Link

curl -X POST https://api.dcision.io/v1/decisions/lead-qualification \
  -H "Authorization: Bearer $DCISION_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: lead-8421" \
  -d '{
    "state": {
      "message": "We need pricing for 500 users and want to start next month.",
      "company_size": 500,
      "source": "website"
    }
  }'

{
  "decision_id": "dec_3fKq9ZtW1mXcV7bN2pLa",
  "execution_id": "exec_8HsT2kQw9ZyR4vMn1cXe",
  "schema": "lead-qualification",
  "version": 1,
  "result": { "purchase_intent": 0.9412, "priority": "high", "route": "sales" },
  "confidence": { "purchase_intent": 0.8824, "priority": 0.69, "route": 0.85 },
  "scores": { "priority": 2.81 },
  "composites": { "lead_score": 0.8414 },
  "action": "continue",
  "action_reason": { "type": "default" },
  "metrics": { "latency_ms": 412, "engine": "jev", "model": "jev-1.13.0", "estimated_cost_usd": 0.00001575, "input_tokens": 375, "output_tokens": 36 }
}

Other outcomes you will see:

The confidence of a probability is |2p − 1|, so rule 2 escalates every lead whose purchase_intent is between 0.2 and 0.8 — see Confidence and probabilities.

Act on itCopy Anchor Link

async function qualify(lead) {
  const response = await fetch("https://api.dcision.io/v1/decisions/lead-qualification", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.DCISION_API_KEY}`,
      "Content-Type": "application/json",
      "Idempotency-Key": `lead-${lead.id}`,
    },
    body: JSON.stringify({ state: { message: lead.message, company_size: lead.companySize, source: lead.source } }),
  });
  if (!response.ok) return crm.assign(lead, "sdr"); // on errors, a person decides
  const { action, result, composites, execution_id } = await response.json();

  switch (action) {
    case "block":
      return crm.discard(lead, { reason: "spam", execution_id });
    case "escalate":
      return crm.assign(lead, "sdr", { note: "needs review", execution_id });
    default: {
      const sla = { critical: "1h", high: "4h", medium: "1d", low: "3d" }[result.priority];
      return crm.assign(lead, result.route, { sla, score: composites.lead_score, execution_id });
    }
  }
}

Sort each team's queue by lead_score to work the best leads first. Fields the decision doesn't declare are still forwarded to the engine, so you can add context such as country or page without changing the schema.

Tune itCopy Anchor Link

• Describe your business in the decision's context: what you sell, to whom, your price range. It's sent with every lead.

• Sharpen the boundaries between sales, sdr and nurture with exclusions ("not for existing customers", "no budget or timeline mentioned"). If the Playground flags a near tie, the descriptions overlap.

• Escalate critical leads to a person even when routing is confident:

  Copy Text

  { "field": "priority", "on": "output", "operator": "gte", "value": "critical", "action": "escalate" }

• Escalate on the weighted level to catch leads that lean critical even when high is the most likely level: { "field": "priority", "on": "score", "operator": "gte", "value": 3.5, "action": "escalate" }.

• Require confident routing with "minConfidence": 0.7 on route: below it, the fallback action applies.

• Tune lead_score by changing its weights, or add terms — a − 3 × spam probability, a company_fit score — then route on it: { "field": "lead_score", "operator": "gte", "value": 0.8, "action": "continue" }.

• Replay real leads: in Executions, open a run and Re-run this input in the Playground to check that an edit improves it before you deploy v2.