SaaSQualification

Form Identification

Identify who's behind demo and contact form submissions, so sales knows which leads to chase first.

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

Demo request

m.okafor@finch.coIdentified
Head of Data · Finch · 200–500
Route to sales → priority

The problem

Demo requests arrive as an email address and a hope. Is it a VP at a target account or a student doing research? Without knowing, SDRs either waste time qualifying everyone or, worse, respond slowly to the leads that mattered.

With Encrata

Enrich the address the moment the form is submitted. Role, company and seniority arrive before the thank-you page finishes loading, so routing rules can send a Head of Data at a 500-person company straight to a senior rep's calendar while everything else goes to the nurture queue.

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

Form Identification 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
}

Route on facts, not form fields

Fire the lookup from the form's submission handler and route on what returns: seniority and company size map to lead tiers, and each tier has a routing rule. The profile lands in the CRM before the SDR sees the lead, so triage happens on facts. Keep a fallback tier for addresses that resolve thin, a sparse profile on a corporate domain is still worth a human look.

Speed to lead moves first

Speed-to-lead is the metric that moves: when routing is automatic and informed, the high-value demo request gets a calendar link in minutes instead of sitting in a queue behind twenty students. Teams also find their form conversion improves indirectly, once enrichment fills the firmographic fields, you can delete them from the form itself and ask only for the email.

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"}'