Sales · Automate & Route
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.
Works acrossDoeHubSpotSlackGmail
What you get.
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.
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.
What changes.
- 01Time to first touchBefore · Hours to days; worse over weekendsWith Doe · Minutes, on a tight schedule
- 02Thin recordsBefore · Park in "unassigned"; routed by hand laterWith Doe · Enriched first, then routed automatically
- 03Rep attentionBefore · Every form fill pings; reps tune outWith Doe · Only qualified leads alert; non-fits filtered
- 04What the rep getsBefore · A raw form submission to researchWith Doe · Enriched profile, fit reason, draft reply
From form fill to the right rep, in minutes
- 01Catches a new inbound leadHubSpotOn 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
- 02Enriches the record so it can be qualifiedDoeDoe 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
- 03Qualifies it against your ICP and routing rulesDoeThe 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
- 04Routes it and alerts the owner with contextSlackDoe 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
- 05Drafts the first touch for approvalGmailDoe 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"
- 06RecurringEvery 5 minutes during business hoursThis runs as a tight Loop, a scheduled job that sweeps for new inbound every few minutes (the shortest interval Doe supports is five minutes) rather than waiting for a nightly batch. It is not a webhook firing the instant a form posts; it is a dependable poll that turns a two-day hand-off into a few minutes. Each run handles only the leads that arrived since the last one, so nothing is processed twice. Routed in your CRM + owner alerted in Slack with a draft reply.
Start with the right source material.
- 01Add your library and toolsAdd or select the source files Doe should use, then connect the tools this task needs. No API keys, no engineering.
- 02Describe 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.”
- 03It runs on scheduleRuns 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.
Before you delegate.
- 01Is this real-time, instant routing?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.
- 02Why route through Doe instead of my CRM’s built-in rules?CRM routing rules can only act on fields that are already filled in, which is why thin submissions end up unassigned. Doe enriches the record first (company, size, title, verified email) so it can route on complete information, then qualifies against your ICP with a reason and filters out non-fits. Your rules decide the destinations; Doe makes every lead routable and adds the judgment a rule can’t.
- 03Does it send emails on its own?No. Doe drafts the first touch and queues it for the assigned rep to approve and send. The human stays in control of what goes out under their name. The draft removes the cold-start, so the reply is fast and still personal.
- 04How does it avoid sending junk leads to reps?Every lead is qualified against your ICP before anyone is alerted, with a written reason. Obvious non-fits (personal-email sign-ups, students, competitors, out-of-territory) are flagged and held rather than routed, so reps learn the alert means a real, qualified lead and stop tuning it out.
- 05Are the enriched emails verified?Yes, verified on output. Doe verifies the email as part of enrichment and flags anything risky or undeliverable, so a routed lead doesn’t turn into a bounce the moment your rep replies.