Inbound shouldn’t sit in a queue for two days.
When a lead comes in, Doe enriches it, qualifies it against your ICP, and routes it to the right rep with a reason and a draft first touch, within minutes instead of the next business day. The thin records that break routing rules get enriched first, so the good ones don’t fall through.
Doe watches for new inbound (a demo request, a signup, a form fill), enriches the record with its native tooling, qualifies it against your ICP, and routes it to the right owner within minutes, with a reason and a suggested first touch. It enriches first, so it catches the thin "work email only" submissions a routing rule drops, and it flags low-fit leads instead of waking a rep for them. Run as a tight Loop, it closes the speed-to-lead gap without sending unqualified noise to your team.
What changes
| Dimension | Before | With Doe |
|---|---|---|
| Time to first touch | Hours to days; worse over weekends | Minutes, on a tight schedule |
| Thin records | Park in "unassigned"; routed by hand later | Enriched first, then routed automatically |
| Rep attention | Every form fill pings; reps tune out | Only qualified leads alert; non-fits filtered |
| What the rep gets | A raw form submission to research | Enriched profile, fit reason, draft reply |
From form fill to the right rep, in minutes
HubSpotOn its next sweep, minutes apart, Doe picked up the new form fill or signup that arrived since the last run, including the thin ones a routing rule would have parked as unassigned
Doe used its native enrichment to fill in company, size, industry, the person’s title and seniority, and verify the email, turning "work email only" into a complete, routable record
The Judge scored the lead against your ICP with a reason, decided the right segment and owner, and flagged the obvious non-fits (students, competitors, personal-email tire-kickers) so they don’t page a rep
SlackDoe assigned the lead to the right rep in the CRM and pinged them with the enriched profile, the fit reason, and any buying signals, so the rep opens it already knowing who this is and why it matters
GmailDoe prepared a short, personalized first reply referencing what the lead asked for and a relevant signal, queued for the rep to approve and send, closing the gap between "form filled" and "human replied"
The lead raised their hand. Two days later, a rep noticed.
A buyer fills out your form at 4pm on a Thursday. Your routing rule needs a company-size field to assign them, but they only gave a work email, so the record lands in an "unassigned" bucket nobody owns. By the time someone enriches it by hand on Monday and figures out it should have gone to the enterprise team, the buyer has booked a call with whoever replied first, and it wasn’t you. The single biggest predictor of whether you win an inbound lead is how fast you respond, and the hand-off is where the hours leak.
The other failure mode is the opposite: every form fill pings a rep, including the students, the competitors, and the personal-Gmail tire-kickers, so the team learns to ignore the alerts, then tunes out the one that was a director at a perfect-fit account. Either way, raw routing rules send the wrong volume to the wrong people at the wrong speed.
Get started with the right source material
Add your library and tools
Add or select the source files Doe should use, then connect the tools this task needs. No API keys, no engineering.
Describe what you need
“Every few minutes during business hours, check HubSpot for new inbound leads. Enrich each one, qualify it against our ICP, route it to the right rep by segment, flag obvious non-fits, alert the owner in Slack with the reason, and draft a first reply for them to approve.”
It runs on schedule
Runs every five minutes in business hours. New leads are enriched, routed, and waiting with a draft, so reps respond while the buyer is still in-market.
Inbound Lead Routing FAQ
It’s near-real-time. Doe runs as a Loop on a schedule, and the tightest interval it supports is every five minutes, so a lead is typically enriched and routed within minutes of arriving instead of the next business day. We’re deliberate about this: it’s a reliable poll rather than a webhook, so it never claims to fire the instant a form posts. For closing the speed-to-lead gap, minutes is the difference that matters.
Related tasks
Stop doing the work your tools should do for you.
Set it up once. Doe runs it every time.
