SaaSOnboarding

Personalized Onboarding

Customize onboarding flows using each signup's role, seniority and company size.

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

Welcome, Sara 👋

Set up for marketing leads · 51–200 team

1Connect your CRM
2Invite your team

The problem

Your onboarding treats a solo hobbyist and a VP rolling out to 200 seats identically, which means it's wrong for at least one of them. Asking users to self-describe adds friction exactly where drop-off hurts most.

With Encrata

Enrich the signup email in the background and branch onboarding on what comes back: role, seniority, company size. The VP sees SSO setup and team invites; the hobbyist sees the quickstart. Nobody filled in a survey, and both think your product just gets them.

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

Personalized Onboarding 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
}

Branch the first run quietly

Enrich in the background during account creation and branch the first-run experience on what returns: role maps to use-case templates, company size maps to team-vs-solo flows, seniority maps to depth of technical detail. Always keep a generic default path, enrichment is a progressive enhancement, not a gate.

Activation follows relevance

Activation metrics respond because the first session stops being one-size-fits-none: the developer lands in the API quickstart, the VP lands in team setup, and neither wades through the other's onboarding. The same enrichment keeps paying after day one, lifecycle emails segmented by actual role outperform 'one sequence for everyone' by default.

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