Empty Means Not Found – Why Guessed Emails Break Hiring
Empty contact fields should mean not found – not a guessed mailbox. Invented emails waste recruiter time, burn trust, and poison ATS data.
Empty means not found. When a contact lookup cannot return an email or phone, the honest response is blank fields – not a pattern-guessed mailbox. Guessed emails break hiring: they bounce, they land in the wrong inbox, they teach bad ATS hygiene, and they make enrichment look like spam infrastructure. Invenitor’s product stance is soft mesh coverage with no invented contacts.
This post is the Week 1 honesty pillar. If you only remember one line from the content wall, make it this: empty ≠ invent.
Why do teams invent emails in the first place?
Desks are under pressure to move. A blank email cell feels like a failed task. Tools that auto-fill first.last@company.com look productive in a demo. Hiring is not a spray game:
- Wrong-person mailboxes create awkward (or hostile) first touches.
- Bounces train spam filters and waste sequences you never needed.
- ATS fields become polluted – later recruiters trust a lie with a green checkmark.
- Candidates notice when outreach has nothing to do with their actual profile.
A contact lookup API should resolve contacts when found, then stop. Category definition: What a Contact Lookup API Actually Does.
What should an honest API response look like?
- Found – email, phone, or both (plus links when available).
- Empty completed find – request succeeded; contacts not available. Treat as not found.
- Error / timeout – retry or fix the request; do not treat as “no contact.”
Builders: map empty to UI copy like “No contact on file,” not “Invalid email.” Recruiters: skip auto-send when fields are blank. Agents: never hallucinate a mailbox to “help.”
How do guessed emails break India staffing desks?
Boutique IT staffing in India often runs on sheets, WhatsApp confirmations, and thin ATS setups. One invented email can:
- Burn a client intro when the message hits finance instead of engineering.
- Waste a consultant’s morning chasing a bounce.
- Create a fake “verified” column that nobody can audit.
Desks that already shortlist on LinkedIn do not need fiction – they need an API that returns what exists. Workflow: India Boutique IT Staffing – Candidate Contacts Without a Sales Cloud. Plain English: Contact Enrichment Explained for Recruiters – Plain English.
How should billing reinforce honesty?
Billing semantics teach product ethics. Invenitor’s frozen credit rule:
1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend.
That means an empty completed find does not punish you for honesty. You can afford to leave cells blank. Pack pricing and Razorpay rails: INR Credit Packs for Contact Lookup – How Razorpay Pricing Feels. Compare seats vs credits: Seat Subscriptions vs Pay-Per-Lookup Credits – A Cost Model. Live numbers: pricing.
What should recruiters do when a lookup returns empty?
- Leave the email/phone blank in the ATS or sheet.
- Try a cleaner profile URL if the input was truncated or a company page.
- Use another channel you already have permission to use (referral, existing thread) – do not invent.
- Move to the next shortlisted profile instead of forcing a send.
Empty is information. It says “do not email this path yet.” That is more professional than a clever guess.
How do agents stay honest with MCP or REST?
Recruiting agents should call a documented lookup and pass through empty fields. Do not let the model “complete” the JSON. Wire MCP without scrapers: MCP for Recruiting Agents – Wire Contact Lookup Without Building a Scraper. Endpoint details: docs. Request shape hub: LinkedIn or GitHub Profile URL → Contact Lookup API.
What is the trust checklist before you buy any contact API?
- Does the vendor say empty means not found – in writing?
- Do they avoid public hit-rate % theater?
- Is billing clear on empty vs error?
- Can you pay in a rail your desk uses (INR/UPI for India)?
- Is the product a lookup API – or a sequencer wearing an API badge?
If a demo never shows an empty response, ask for one. Honesty is a feature you can inspect.
What should you do next?
Sign in, run a few real shortlist URLs, and watch empty fields stay empty. Buy credits on pricing when the path works. Keep the docs open while you wire your sheet or agent. Prefer blank cells over invented outreach – every time.
What language should your team standardize on?
Agree on three phrases and use them everywhere – sheet headers, ATS notes, agent prompts:
- Found – email and/or phone returned by the lookup.
- Not found – empty completed find; do not invent.
- Error – transport or request failure; retry, do not mark as not found.
When juniors, freelancers, and agents share the same vocabulary, empty stops feeling like failure and starts feeling like professional restraint. Keep docs and pricing bookmarked beside the sheet.
What should client-facing teams tell hiring managers?
If a client asks why a row is blank, say: “We looked up the profile; no contact was on file, so we did not invent one.” That sentence protects your brand more than a fabricated address ever will. Pair it with the next profile on the shortlist. Honesty compounds; bounce rates from guessed mailboxes compound the other way. Point internal wiki pages at this post and at What a Contact Lookup API Actually Does.
Questions
What does an empty email field mean in Invenitor?
Not found. The find completed without inventing a mailbox. Soft mesh coverage varies by person.
Why is inventing emails harmful in hiring?
Guessed addresses bounce, hit the wrong person, pollute ATS data, and train teams to spam instead of shortlist.
Do empty completed finds spend a credit?
1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend.
Should my ATS store a guessed email as “verified”?
No. Only store contacts that were returned as found. Mark empty as not found.
How should recruiting agents handle empty responses?
Pass empty fields through. Never hallucinate an email to complete a tool call.
Where can I read the API behavior?
See /docs for the find endpoint and /pricing for credits. The honesty stance is product policy, not a slogan.
