Solutions / Use case

Lead routing automation, from form fill to first call.

Every lead passes through forms, marketing automation, enrichment, the CRM and the rep's inbox. When those systems don't talk, leads wait, land with the wrong rep or never get called. Tray.ai connects every handoff, so every new lead reaches the right rep within a few minutes.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.
Jump to the stages
One lead moving from form to first call: a demo request in Marketo, enriched by Clearbit, matched to its account and assigned to a rep in Salesforce, the rep alerted in Slack, the first call made from Outreach, and the first touch logged in Salesforce two minutes after the form.

The short answer

What is lead routing?

Lead routing is the process that takes a new inbound lead to the right salesperson: capturing it, checking the data, enriching it, removing duplicates, matching it to an existing account, scoring it, assigning an owner, alerting that rep and starting the first contact. It runs across forms, the marketing automation platform, enrichment tools, the CRM and the tools reps work in, and most of the delay happens in the handoffs between them rather than in the assignment rule itself.

  1. 1 Capture
  2. 2 Events
  3. 3 Enrich
  4. 4 Dedupe
  5. 5 Account match
  6. 6 Score
  7. 7 Assign
  8. 8 Alert the rep
  9. 9 First touch
of leads to sales in under 3 minutes at DocuSign
90% → 99%
faster lead response at Cisco
80%
fewer invalid leads at Cisco
60%
lead response time at Jellyvision
~30 → ~10 min

Lead routing, stage by stage

Nine stages, each with what breaks and a how-to guide for building it.

  1. 1

    Capture and validate

    Form fills, ad leads and list uploads arrive, and bad rows are caught before anything reaches the CRM.

    Where it breaks: An import reports 1,397 of 1,400 rows loaded and says nothing about the three that failed.

  2. 2

    Events and webinars

    Registrations flow in before the event, attendance is recorded as its own fact, and follow-up starts the same day.

    Where it breaks: A thank-you-for-attending email goes to everyone who registered, including the half who never showed up.

  3. 3

    Enrichment

    Company, size, industry and region are filled in from the email domain, so routing has something to work with.

    Where it breaks: The enrichment call times out and the lead sits unassigned overnight waiting for it.

  4. 4

    Dedupe and merge

    A second form fill from the same person updates their record instead of creating another one.

    Where it breaks: Two records for one buyer, owned by two reps, both calling.

  5. 5

    Lead-to-account matching

    The lead is attached to the account it belongs to, including subsidiaries and their parent company.

    Where it breaks: A lead from a customer with an open deal is routed by territory to a rep who has never spoken to them.

    Example connections

  6. 6

    Scoring and qualification

    Fit and recent activity become one score the CRM shows, and crossing the line sends the lead straight to routing.

    Where it breaks: Marketing sees 85 and sales sees 40, because three systems write the same score field.

    Example connections

  7. 7

    Routing and assignment

    Rules run in a fixed order against current territories, and anything they miss lands in a watched fallback queue.

    Where it breaks: Leads keep going to a rep who left last quarter, because the territory table never changed.

    Example connections

  8. 8

    Rep alert and escalation

    The owner hears about the lead where they work, with the context to call, and a clock escalates it if nobody does.

    Where it breaks: The alert is an email in a folder, and a demo request waits four hours for a call.

    Example connections

  9. 9

    First touch and sequence

    The lead goes into the right sequence, and calls and emails are logged back to the CRM at a level people can read.

    Where it breaks: The sequence keeps emailing a lead who already booked a meeting, because the CRM never told it.

Three ways to connect the systems

  • Built-in routing in one tool. Quick to switch on, but it only sees the data inside that tool, so enrichment, matching and alerts happen somewhere else, on their own schedule.
  • A routing point tool plus scripts. Good at the assignment rule itself. The steps before and after it are still separate jobs, and your team owns the fixes when one of them stalls.
  • An integration platform. Every handoff in one workflow, with the same error handling, logging and access control. This is Tray.ai: marketing and sales operations build the workflows, and IT governs every one of them.

The Tray.ai platform behind it

Tray.ai is the enterprise orchestration platform for data and AI. These are the parts of it that run lead routing.

Intelligent Integration

The iPaaS built for the AI era.

Merlin Agent Builder

Build AI agents that act, not just chat.

The metrics lead routing moves

What marketing operations and sales operations teams measure, and which stage each number depends on.

Speed to lead
Time from the lead arriving to the first logged call or email.
What moves it Alerting the rep where they work, with a clock that escalates when nobody calls. How to build speed-to-lead alerts 
Unassigned lead rate
Share of new leads that reach the fallback queue or have no owner.
What moves it Routing rules that run in a fixed order, with a fallback that is watched. How to build lead routing that assigns in seconds 
Invalid lead rate
Share of incoming leads rejected or held back for bad or missing data.
What moves it Checking each row before it is written, and holding failures where someone can fix them. How to build lead import and validation 
Duplicate rate
Share of new leads that match a person already in the CRM.
What moves it Matching on more than the exact email address, and merging without losing history. How to build lead deduplication and merge 
Account match rate
Share of leads attached to an existing account before they are routed.
What moves it Matching on domain, company name and parent company, with a review queue for near misses. How to build lead-to-account matching 
MQL to opportunity rate
Share of marketing qualified leads that become a sales opportunity.
What moves it A score that both teams trust, built from fit and recent activity. How to build a lead scoring sync 

Lead routing connectors

The systems lead routing runs on, grouped by the seat each one fills. Each links to its connector page.

CRM

Where the lead is owned, matched to an account and worked by the rep.

Marketing automation

Where forms, campaigns and nurture run, and where most leads first appear.

Forms, ads and chat

Where buyers raise their hand, outside the marketing platform's own forms.

Events and webinars

Where registrations and attendance come from.

Enrichment and intent

Where company data, contact checks and buying signals come from.

Sales engagement and meetings

Where the first call, email or meeting happens.

People and messaging

Where reps get alerted, and where time off and reporting lines live.

Data and reporting

Where every routing decision and its timings are kept and reported.

Connections between them

Field mapping, templates and common problems for the pairings lead routing depends on.

Anything not listed connects through the full connector library, or directly through its API.

Teams running lead routing on Tray.ai

“Before implementing Tray we were sending 90% of our leads to our sales team in under 10 minutes. After implementing Tray we are sending 99% of our leads to the sales team in under 3 minutes.”

— Kevin Cassidy, Director of Marketing Operations, DocuSign

Processes next to lead routing

These share systems and data with lead routing without being stages of it.

Revenue operations

How to build a CRM to marketing automation sync

Decide field ownership before you build, sync deltas not everything, handle the person-versus-lead model gap, and break loops. The prompts that build it.

Marketing

How to build a campaign attribution pipeline

Stitch touches to accounts, publish more than one model, and reconcile spend against pipeline so the number survives a finance review. The prompts.

Revenue operations

How to build pipeline hygiene automation

Detect the staleness that matters, nudge the owner rather than the report, escalate on the deals that count, and measure whether it worked. The prompts that build it.

Customer success

How to build a product usage to CRM sync

Send the three signals that change a conversation, aggregated and labelled, without turning the CRM into an analytics tool. The Headless prompts that build it.

Data operations

How to build a customer 360 and master data sync

Pick a survivorship order per attribute, resolve identity on more than email, and publish a golden record every system can point at. The prompts.

Data operations

How to build a CRM to warehouse sync

Capture history instead of current state, handle deletes and field changes, land raw then model, and prove the row counts. The Headless prompts that build it.

Reading and resources

eBook

Fix your broken lead funnel

Automate the lead lifecycle across your entire funnel—from capture to routing—and eliminate data issues, delays, and dead leads with the Tray platform.

On-demand webinar

Trapped by your MAP? Strategies for a smarter lead lifecycle

Learn how modern teams are rethinking lead lifecycle management beyond traditional marketing automation platforms to drive faster, cleaner revenue outcomes.

Assessment

Which of your automations breaks first?

Four questions about each RevOps process your team has automated. Get a ranked list of which one is most likely to stop working, and why.

From the blog

BlogLead routing automation: why rules outlive the org chartBlogLead lifecycle management: the six steps and where each one breaksBlogLead processing pipelines: what they are and what stalls themBlogLead list uploads: why leads arrive unroutableBlogLead enrichment automation: where it stalls and whyBlogLead-to-account matching: why leads and accounts drift apartBlogLead scoring: why the score stops matching realityBlogHow to integrate Facebook lead ads data with SalesforceBlogMaximizing HubSpot FormsBlogHow to load LinkedIn lead data into your CRMBlogLead deduplication: why duplicates come backBlogSpeed to lead: where the minutes goBlogWebinar lead follow-up: why event leads go cold

Speaking the same language

Definitions for the terms that come up in this conversation.

Workflow automation

Software that executes a defined sequence of steps automatically — moving data, triggering actions, and routing decisions without manual intervention.

iPaaS

Integration Platform as a Service — a cloud-hosted platform for building, running, and managing integrations between applications.

Frequently asked questions

What is the difference between lead routing and lead assignment?

+

Assignment is one stage, the rule that picks an owner. Lead routing is the whole path from the form to the first call, because an owner picked from bad, duplicate or unmatched data is the wrong owner, and an owner who never hears about the lead is no owner at all.

We already have routing rules in our marketing platform or CRM. Why add this?

+

Those rules assign inside one system. The delays sit between systems, in the enrichment call, the duplicate check, the account match, the score update and the rep alert. Tray.ai runs those steps as one workflow you can watch, so a lead that stalls is visible at the step where it stalled.

Which systems does Tray.ai connect in lead routing?

+

CRM (Salesforce, HubSpot, Microsoft Dynamics 365, Pipedrive), marketing automation (Marketo, Pardot, Eloqua, Salesforce Marketing Cloud), forms, ads and chat (Typeform, Unbounce, LinkedIn, Facebook, Drift, Intercom), events (Zoom, GoToWebinar, Cvent, Eventbrite), enrichment and intent (Clearbit, ZoomInfo, Leadspace, Demandbase), sales engagement (Outreach, SalesLoft, Gong, Calendly), and Slack, Microsoft Teams and Snowflake. Anything without a connector connects through its API.

How fast can leads reach sales?

+

DocuSign went from 90% of leads reaching sales in under 10 minutes to 99% in under 3 minutes. Jellyvision cut lead response time from about 30 minutes to about 10. Cisco saw 80% faster lead response and 60% fewer invalid leads.

Can marketing operations build this without engineering?

+

Yes. GitHub's marketing team built its marketing platform and CRM sync with no engineering effort. Routing rules, scoring tables and alert targets open in Tray Build, so a territory change is an edit by the person who owns territories.

Where do AI agents fit in lead routing?

+

In the judgement calls. Agents classify industry, persona and intent from free text, fill gaps when enrichment comes back empty, and suggest the best account match when the name is close but not exact. The routing rules still decide the owner, so every assignment can be explained.

Do we have to replace our marketing platform or CRM?

+

No. Tray.ai connects the systems you already run and carries the lead between them. The stages above describe what moves between systems, not which ones you use.

Last reviewed 2 October 2026.

See lead routing running on your stack.

Walk through your systems and stages with a Tray.ai expert.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.
Browse the how-to guides