Skip to content
Secnd
Secnd

Lead routing

Route expressed product needs to the right sales workflow.

Use stated requirements rather than inferring sensitive attributes or personal worth. Keep region, account ownership, and eligibility rules in code.

request
{
  "model": "ren-zero-2026-11-12",
  "type": "choice",
  "situation": "The prospect asks about a shared account, higher request limits, and a data processing agreement for their engineering team.",
  "question": "Which team should follow up on the stated requirements?",
  "options": [
    {"id": "enterprise", "description": "Team access, contractual terms, or larger workloads"},
    {"id": "developer", "description": "Individual API integration and getting started"},
    {"id": "review", "description": "Needs are unclear or span unrelated workflows"}
  ],
  "threshold": 0.9
}

Create a routing suggestion on act; let your CRM enforce ownership and communication permissions. A model decision does not authorize sending an email. Review ambiguous requests and all ask_human results.

Evaluate short messages, existing customers asking for support, and research inquiries that mention enterprise features without purchase intent.