SalesRouting

Lead Routing

Route inbound leads to the right rep by company, territory or industry automatically.

Email identity · 1,000 credits per lookup · no monthly fee

lead@fintech.ioFintech team
ceo@bigco.comEnterprise
Auto-routed

The problem

Round-robin routing sends a Fortune 500 lead to the newest SDR and a student to your enterprise AE. Routing rules based on form fields only work when people fill forms honestly, and they don't.

With Encrata

Route on resolved identity instead of self-reported fields. Company, industry and size come back from the email itself, so your fintech specialist gets the fintech leads and enterprise leads land with the team that closes them, automatically, on every lead, within seconds of capture.

How it works

1

Send the address

Call the identity endpoint with just an email address, no name, no company, nothing else required.

2

We resolve the person

Encrata matches the address against public profiles and returns name, role, company, location and social accounts.

3

Use the profile

Route, personalise, verify or investigate with a full picture of who is behind the address. Fields you ask for are the fields you get.

One call, structured answer

Lead Routing runs on the email identity lookup at 1,000 credits per lookup. Same API key, same JSON shape as every other Encrata lookup.

  • A match on 99.86% of addresses, near-zero dead lookups
  • Every field is labelled found or not found, so you never guess what to trust
  • Ask only for the fields you need with the fields parameter
  • One API call replaces minutes of manual research per contact
Terminal
curl -X POST "https://encrata.com/api/agent/email-identity" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email": "jane@example.com"}'
response.json
{
"email": "jane@example.com",
"person": {
"first_name": "Jane",
"last_name": "Doe",
"company": "Acme Inc",
"job_role": "Head of Product",
"city": "San Francisco",
"socials": {
"linkedin": "linkedin.com/in/janedoe"
}
},
"credits": 1000
}

Resolved fields drive the router

Replace form-field routing with resolved-identity routing: enrich on capture, then route on company, industry, size and seniority from the profile. Rules stay in your existing router, only the inputs change from self-reported to resolved. Keep a catch-all queue for thin resolutions so nothing stalls waiting for perfect data.

Specialists get their specialty

Routing accuracy compounds: the right rep gets the right lead while it's hot, specialists actually receive their specialty, and enterprise leads stop leaking into the SMB queue because someone picked 'other' in a dropdown. Audit the router monthly against closed-won data, resolved-field routing gives you the ground truth to tune territories against.

More email identity use cases

View all
Start with 500 free credits
$curl https://encrata.com/api/agent/lookup -H "Authorization: Bearer YOUR_API_KEY" -d '{"e": "satya@microsoft.com"}'