// guide
How to route work emails to sales and personal emails to self-serve
For growth engineers, RevOps and founders who run both a sales team and a self-serve funnel · Updated · 6 min read
My sales reps waste their mornings on Gmail signups while real company leads sit in the same queue.
To route work emails to sales and personal emails to self-serve, look up each lead's email with pingutil and branch on category: company goes to sales, free and isp go to self-serve, educational and government go to their own queue if you have one, and disposable or verdict.is_spam leads go nowhere. For a finer split, use company.employee_size_estimate to send small companies to self-serve and larger ones to a rep. A fast lookup with skip_enrichment: true is enough for the first split and returns in milliseconds.
The rest of this guide covers the routing table, the code for a form webhook, and the cases where the email alone sends a lead to the wrong place.
What this problem costs you
When every lead lands in one queue, everyone pays a little:
- Reps triage instead of selling. Each personal-email signup a rep opens, researches and discards is a few minutes gone. Across a day that's the time they'd have spent on the lead that needed a fast reply.
- Self-serve users get a sales email they didn't want. Someone trying your product on a weekend gets a "let's book a call" message and leaves. They wanted a docs link.
- Company leads wait. A lead from a target account sits behind the personal signups that arrived first.
- Your funnel numbers blur. Sales conversion looks worse because reps are measured on leads that were never theirs.
The fix doesn't need machine learning. It needs a reliable answer to "is this a company domain?" at the moment the lead arrives.
How pingutil solves it
1. Decide your queues
Write down where each kind of lead should go before you write code. A typical setup has four destinations: sales, self-serve onboarding, a special queue for education or public sector, and a discard log. If you don't sell to schools, education goes to self-serve.
2. Look up the email when the lead arrives
Call POST https://pingutil.com/v1/lookup from your form handler or webhook. For the work-versus-personal split, skip_enrichment: true returns category and verdict without calling the enrichment model. If you also route on company size, drop that flag; the first lookup for a new company domain takes a few seconds while the profile is built, then it's cached.
Try a few of your own recent leads in the live demo to see the categories they get.
3. Branch on category
category is decided by lists first (disposable, then free webmail, then ISP), then by TLD rules (government, then education), and anything left is company. So a lead from cs.stanford.edu is educational even though the registrable domain is stanford.edu, and mail.acme.io collapses to acme.io. Business email vs personal email explains why the list-based approach beats checking for an MX record.
4. Optionally split company leads by size
company.employee_size_estimate is one of 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000 or 10000+. Many teams send 1-10 to self-serve even with a company domain, because a three-person startup usually wants to try the product, not talk to sales. Routing leads by company size goes through picking the cut-off.
Decision table: response field to route
| Field and value | Route | Note for the rep |
|---|---|---|
verdict.is_spam: true |
Discard log | Disposable or machine-generated |
category: "disposable" |
Discard log | |
category: "free" |
Self-serve | Personal webmail |
category: "isp" |
Self-serve | Consumer ISP mail, almost always personal |
category: "educational" |
Education queue, or self-serve | Student or staff |
category: "government" |
Public sector queue, or sales | Different procurement |
category: "company", size 1-10 (with enrichment) |
Self-serve | Optional rule |
category: "company", any other size or no profile |
Sales | Include company.name and industry if present |
verdict.reason: "role_based" |
Route by category | Flag "shared inbox" |
verdict.reason: "sales_outreach" |
Low-priority queue | Often a vendor pitch |
company.confidence below 0.5 |
Ignore size, route as company | Don't send to self-serve on a guess |
| Lookup failed | Sales | Fail toward a human, not away |
Note the last row. When you can't classify a lead, a person should see it. Sending an unclassified enterprise lead to an automated nurture is the expensive mistake.
Complete example: a lead-routing webhook in Python
This Flask endpoint receives a JSON form submission, routes it, and posts sales leads to a Slack channel through an incoming webhook. Replace the destinations with your CRM, help desk or email tool.
# route_leads.py (Python 3.9+, pip install flask requests)
import os
import requests
from flask import Flask, jsonify, request
app = Flask(__name__)
PINGUTIL_KEY = os.environ["PINGUTIL_KEY"] # pk_live_...
SLACK_WEBHOOK = os.environ["SLACK_SALES_WEBHOOK_URL"]
ROUTE_BY_SIZE = True # False = skip enrichment, route on category only
def lookup(email: str):
r = requests.post(
"https://pingutil.com/v1/lookup",
json={"input": email, "skip_enrichment": not ROUTE_BY_SIZE},
headers={"Authorization": f"Bearer {PINGUTIL_KEY}"},
timeout=20,
)
r.raise_for_status()
return r.json()
def route(data: dict) -> tuple[str, list[str]]:
notes = []
verdict = data["verdict"]
if verdict["is_spam"] or data["category"] == "disposable":
return "discard", [verdict["reason"] or "disposable"]
if verdict["reason"] == "role_based":
notes.append("shared inbox")
if verdict["reason"] == "sales_outreach":
return "low_priority", ["likely vendor outreach"]
category = data["category"]
if category in ("free", "isp"):
return "self_serve", notes + [f"{category} email"]
if category == "educational":
return "education", notes
if category == "government":
return "public_sector", notes
if category != "company":
return "sales", notes + ["unclassified"]
company = data.get("company") or {}
if company.get("name"):
notes.append(f"{company['name']} ({company.get('industry') or 'industry unknown'})")
confident = (company.get("confidence") or 0) >= 0.5
if confident and company.get("employee_size_estimate") == "1-10":
return "self_serve", notes + ["company with 1-10 employees"]
return "sales", notes
@app.post("/leads")
def receive_lead():
lead = request.get_json(force=True)
email = str(lead.get("email", "")).strip()
try:
destination, notes = route(lookup(email))
except requests.RequestException:
destination, notes = "sales", ["lookup failed, check manually"]
if destination == "sales":
text = f"New sales lead: {email}. " + "; ".join(notes)
requests.post(SLACK_WEBHOOK, json={"text": text}, timeout=5)
elif destination == "self_serve":
pass # e.g. add to your onboarding email sequence
# store destination + notes with the lead for reporting
return jsonify(destination=destination, notes=notes)
Keep the routing in one function (route here). When sales asks why a lead went to self-serve, you can answer by reading twenty lines instead of a workflow diagram.
Edge cases and limits
- Founders use Gmail. Some of your best leads will arrive from personal addresses, especially early-stage companies and consultants. Give the form an override: a "talk to sales" button or a team-size field that beats the email-based route.
- Some company domains are personal. A freelancer's vanity domain is
companyto any classifier. With enrichment on, it often shows up as1-10, which is one reason the size rule helps. - Regional providers. The free list covers about 100 major webmail domains and the ISP list about 60 consumer ISP domains. A small regional provider not on either list is classified as
company. If you see one in your data, route it manually and tell us. - Profiles can be wrong or missing. The company profile comes from an LLM reading the homepage. Low
confidence,meta.enrichment_error(for exampledaily_enrichment_limitafter 50 fresh profiles in a day, ordomain_unresolvable) or anullcompany all mean: route on category alone. - One lookup per lead. There's no bulk lookup endpoint and no webhooks from pingutil. Your handler calls the API when a lead arrives. At 60 requests a minute per account and, on the Free plan, 2,000 lookups a day and 30,000 a month, that's plenty for form traffic; re-routing a large backlog takes a loop with a delay.
- Routing isn't verification. A
companycategory doesn't mean the mailbox exists. If sales will email the lead directly, consider verifying leads before the CRM as well.
Next step
Create an API key at the dashboard, point a copy of your form webhook at the route function, and compare its decisions with where your team actually sent the last few weeks of leads. Field details are in the API reference. To score company leads instead of just splitting them, see qualifying B2B leads by email.
Questions people ask
- How do I tell if an email is a work email or a personal one?
- Check the domain against lists of free webmail providers, consumer ISPs and disposable services. Anything that isn't on those lists and isn't an education or government domain is most likely a company domain. A lookup API does this in one call and also handles subdomains and international domains.
- Should personal email leads ever go to sales?
- Yes, when they show strong intent. A founder who requests a demo from a Gmail address is still a buyer. Route on the email by default and let explicit signals like a demo request or a large team size override it.
- What should happen to role addresses like info@ in lead routing?
- Route them by the domain like any other lead, but mark them so the rep knows the inbox is shared. A role address at a target company is still worth a reply, it just may not reach a decision maker.