How to Automate Lead Routing to Your Sales Team

Your workflow needs to fire the instant a new lead arrives. Configure a webhook trigger connected to your form builder (Typeform, JotForm, Gravity Forms, HubSpot Forms, or a custom form). When someone submits the form, the form builder sends the submission data to your workflow's webhook URL.

The webhook payload should include every field from the form: name, email, phone, company name, message or inquiry description, the form page URL (tells you which product or landing page they came from), UTM parameters (tells you the acquisition channel), and submission timestamp.

If your leads come from multiple sources (website form, chatbot, email, partner referral), you can point multiple triggers at the same workflow. Add a source field to each trigger so the workflow knows where the lead originated, which feeds into the scoring model.

Raw form data tells you what the lead typed. Enrichment tells you who they actually are. Call an enrichment API (Clearbit, Apollo, ZoomInfo, or similar) with the lead's email address to retrieve company size (employee count and revenue range), industry, job title, LinkedIn profile, company location, technology stack, and funding status.

Add an API node that sends a GET request to the enrichment service with the lead's email. Parse the response and store the enriched fields as workflow variables. If the enrichment API returns no data (personal email addresses, very small companies), the workflow continues with the form data alone, just with a lower confidence in the score.

Enrichment adds 1-3 seconds to the workflow but dramatically improves routing accuracy. Without enrichment, a lead from "John at Gmail" looks the same as "John, VP of Engineering at a 500-person SaaS company." With enrichment, the second John gets routed to the enterprise team immediately.

Lead scoring assigns a numerical value that represents how likely this lead is to convert. You can score leads with a point-based system, an AI model, or a combination.

Point-based scoring assigns fixed points for each attribute: company size 100-500 employees (+10 points), company size 500+ employees (+20 points), email is corporate domain (+5 points), lead source is paid search (+8 points), lead source is organic (+3 points), inquiry mentions specific product name (+15 points). The total score determines the routing tier. This approach is transparent and easy to adjust.

AI-based scoring sends the lead data (form fields plus enrichment data) to an AI model with a prompt like: "Score this lead from 1-100 based on how well they match our ideal customer profile. Our ideal customer is a mid-market SaaS company with 50-1000 employees looking for workflow automation or AI integration. Return only the number." The AI model evaluates the entire context, including the free-text message field, and produces a score that accounts for signals a point system might miss, like the urgency in the lead's language or a mention of a specific use case.

In practice, the hybrid approach works best: use points for structured data (company size, source, domain type) and AI for the unstructured data (message content, intent classification). Add both scores together for the final routing score.

Add conditional logic that routes leads to different paths based on their score and attributes:

• Score 80-100 (hot leads): Route to a senior sales rep. These leads match your ideal profile and showed high intent. Response time goal: under 5 minutes. Send an SMS notification to the assigned rep.
• Score 50-79 (warm leads): Route to the general sales queue with round-robin assignment. Response time goal: under 1 hour. Send a Slack notification to the sales channel.
• Score 20-49 (cool leads): Route to an automated nurture email sequence. No immediate human outreach. Add to the drip campaign and let content warm them up. See Drip Campaigns and Follow-Up Sequences.
• Score below 20 (unqualified): Log the submission but do not assign to a rep. These might be students, competitors, or mismatches. Send an automated acknowledgment email.

Within each tier, you can add secondary routing rules: leads from the enterprise segment go to the enterprise team, leads asking about a specific product go to that product's specialist, leads from specific geographic regions go to the regional rep.

Speed of notification determines speed of response. For hot leads (score 80+), send both an SMS text message and a Slack DM to the assigned rep. Include the lead's name, company, score, and a one-sentence summary of their inquiry so the rep has context before they even open the CRM.

For warm leads, a Slack channel notification is usually sufficient. Include the lead details, score, and a link to the CRM record.

For cool leads entering nurture, no notification to a rep is needed. The workflow handles them entirely through automation until their engagement score rises enough to warrant human outreach.

Write all lead data (original form fields, enrichment data, score, classification, assigned rep, routing decision) to your CRM or database. Set the lead status to "New" and the source to the appropriate channel.

For hot and warm leads, create a follow-up task in the CRM assigned to the rep with a deadline: 15 minutes for hot leads, 1 hour for warm leads. If the rep has not updated the lead status within that window, trigger a reminder notification.

For cool leads, start the nurture sequence: add them to the appropriate email list, schedule the first drip email for 24 hours later, and set a 30-day review reminder to check if their engagement has increased.