Skip to content

// use case · RevOps and marketing ops engineers wiring forms into a CRM, plus founders setting up their first sales process.

Route every inbound lead to the right team in the first minute

Branch on category first: company leads go to sales, free and isp leads to self-serve, educational to your education program, disposable to the bin. For company leads, add employee_size_estimate and headquarters.country to pick a segment or territory. It is one lookup per lead and the rules live in your own code or automation tool.

The problem

  • Every demo request lands in the same queue and the enterprise ones wait behind students.
  • Round-robin sends a 5,000-person company to the rep who handles startups.
  • We route by a "company size" dropdown that people fill in at random.
  • Speed to lead is slow because someone sorts the queue by hand every morning.

How pingutil solves it

  1. 1

    Look up the lead as it arrives

    Call /v1/lookup from your form handler, Zapier or n8n step, or CRM workflow with the submitted email.

  2. 2

    Route by category

    company to sales, free and isp to self-serve or nurture, educational and government to their own programs, disposable dropped.

  3. 3

    Segment company leads

    Use company.employee_size_estimate for SMB, mid-market or enterprise, and company.headquarters.country for territory.

  4. 4

    Fall back when data is missing

    If company is null or meta.enrichment_error is set, send the lead to a default queue rather than guessing.

Fields you will use

Response fieldWhat to do with it
categoryPick the top-level route
company.employee_size_estimateChoose the segment
company.headquarters.countryAssign territory
meta.enrichment_errorSend to the default queue when no profile is available
const res = await fetch('https://pingutil.com/v1/lookup', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.PINGUTIL_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ input: lead.email }),
}).then((r) => r.json());

const ENTERPRISE = ['1001-5000', '5001-10000', '10000+'];

function route(r: any): string {
  if (r.verdict.is_spam) return 'drop';
  if (r.category === 'educational') return 'education';
  if (r.category !== 'company' || !r.company) return 'self_serve';
  return ENTERPRISE.includes(r.company.employee_size_estimate) ? 'enterprise' : 'sales';
}

await assignQueue(lead.id, route(res));

Compared with the alternatives

Most CRMs and marketing automation tools can route on form fields, and dedicated lead-routing products add round-robin and SLA logic on top. Both still need good data to route on. pingutil supplies that data from the email; it does not replace a routing tool’s assignment rules or calendar logic.

See provider comparisons →

Limits to plan for

  • headquarters.country is free text from the model, so normalize it (for example to ISO codes) before matching territories.
  • employee_size_estimate is an estimate. Treat boundary cases as a hint, not a hard rule.
  • There are no webhooks; your form handler or automation calls the API and acts on the response.

Common questions

Can I use this from Zapier or n8n?
Yes. Both can make an HTTP request with a Bearer token and branch on the JSON response. There is no native app, so you configure the HTTP step yourself.
What if the lookup fails?
Route to a default queue. If enrichment fails, the API returns the category with meta.enrichment_error, or a stale cached profile with meta.served_stale, so you still have something to branch on.
Should students go to sales?
Usually not. category educational covers .edu, .ac.<cc> and .edu.<cc> domains, including subdomains, so you can send them to an education or community track.

Read next