Inbound Lead Coworker
Reads each new lead, enriches the approved fields, checks fit against your written qualification policy, attaches the reason, routes it to the correct owner, and prepares the first response while the lead is still warm.
Qualify inbound demand, keep the CRM current, and hand closed-won context to the next team.
Leads wait in one queue, call notes stay in documents, follow-ups depend on memory, and the CRM becomes a version of the deal that everyone knows is late. Managers spend the forecast call reconstructing reality instead of deciding what to do next.
Hot inbound leads wait behind low-intent submissions.
Commitments made in calls and email never reach the CRM cleanly.
Customer Success receives a closed-won record without the context needed to deliver.
Reads each new lead, enriches the approved fields, checks fit against your written qualification policy, attaches the reason, routes it to the correct owner, and prepares the first response while the lead is still warm.
Checks the CRM, recent messages, meetings, and next steps on a schedule. Flags deals that have gone quiet, lost a champion, missed a commitment, or carry conflicting stage evidence, then drafts the owner nudge.
After a sales meeting, prepares the recap, extracts customer commitments and rep commitments, proposes CRM updates, drafts the follow-up, and schedules the next required check.
Builds the delivery brief from the opportunity, proposal, emails, meetings, and security or implementation promises. Creates the approved handoff tasks and flags anything Sales promised that has no owner.
Also runsAccount research · Renewal preparation · Signature chase · Lost-deal theme analysis
A form submission or CRM record triggers the coworker immediately.
It checks company fit, territory, existing ownership, duplicate records, and the approved qualification fields.
It assigns or recommends the correct owner, attaches the qualification reason, and prepares the first response using relevant account context.
Strategic accounts, conflicts, missing consent, or uncertain ownership go to Sales Operations before anything is sent.
It can prepare and, where policy allows, send routine messages inside a configured boundary. Strategic accounts, new claims, discounts, legal language, and uncertain cases can require named approval before sending.
No. The CRM remains the system of record. The coworker reads the surrounding conversations and files, then prepares or executes verified updates so the record stays aligned with the deal.
Yes. Translate the ICP and routing policy into explicit fields, evidence requirements, disqualifiers, and escalation rules. The coworker attaches the reason for each qualification instead of returning an unexplained score.
Start with inbound qualification if response speed is the problem. Start with meeting follow-through if CRM hygiene and missed commitments are the problem. Do not launch both in the first pilot.
We will configure the qualification policy, evidence, CRM fields, owner, and approval boundary, then run the Sales Coworker once.