Inbound Lead Triage

Outcome: a central job that enriches and classifies arriving leads before a rep opens them, for roughly 315 credits per 50 leads.

Surface: MCP server
Level: Advanced
Uses: verify_email · find_linkedin_from_work_email · enrich_person · enrich_organization · find_company_techstack
Credits: ~315 per 50 leads
Prerequisite: Lesson 03

Why this runs centrally

A rep receiving a raw form fill spends five minutes researching it. Fifteen reps doing that is a job nobody chose to create.

Run once, centrally, every lead arrives with a company profile, a verified address and a classification — and the rep’s five minutes goes into the conversation instead.

Verify first

The cheapest step goes first, and it changes the economics of everything after it.


verify_email → resolve profile → enrich person → enrich company → stack
   cheap          moderate          moderate        cheap        cheap

On a normal inbound stream, verification removes typos, disposables and dead addresses before you pay to research them.

The chain

verify_email

Drop invalid and disposable. Flag catch-alls per policy.

find_linkedin_from_work_email

Resolve to a profile. Free-mail addresses take a different path.

enrich_person

Current title, seniority, company.

enrich_organization

Firmographics on the company domain.

find_company_techstack

Only where a stack signal changes your qualification.

Classify

Free. Fit band, intent band, and a confidence flag.

The prompt


Using the SyncGTM MCP server, triage these inbound leads:
[paste 50 rows: email, source, message]

Steps:
1. verify_email on all. Drop invalid and disposable — list them separately.
2. Separate free-mail addresses (gmail, outlook, etc.) into their own group.
3. For corporate addresses: find_linkedin_from_work_email, then enrich_person.
4. enrich_organization on each company domain.
5. find_company_techstack.

Then classify each lead:
  FIT: High / Medium / Low / Unknown  (size, industry, country, stack)
  INTENT: High / Medium / Low         (source and what they wrote)
  CONFIDENCE: High / Low              (did enrichment complete?)

Return a table: email, name, title, company, headcount, fit, intent,
confidence, and a one-line reason.

Cap at 50. If a step fails for a row, leave the field blank and continue.
Do not call any other tools.

The classification bands drive routing, not eligibility

Fit	Intent	Route
High	High	Immediate rep response, phone if available
High	Low	Nurture with a personal touch
Low	High	Fast response — self-serve or a different tier
Low	Low	Automated response, low-touch nurture
Any	Any, low confidence	Human review, quickly

Never let the classification decide whether someone gets a reply. Everyone who asks a question gets an answer; the band decides speed, channel and who sends it. The leads that enrich worst are small companies, non-English markets and personal addresses — a description of a segment, not of intent. Treating an unenriched lead as a low-quality one systematically ignores exactly the people you cannot afford to ignore.

What it costs

Step	Rows	Cost	Total
Verify	50	~0.3	15
Resolve profile	42	~1	42
Enrich person	30	~1	30
Enrich company	42	~0.5	21
Tech stack	42	~1	42
Classify	—	0	0
			~150–315

The spread depends on resolution rate and on whether you run the stack check on everything or only where it changes the answer.

Handing it to reps

Attach the triage output to the CRM record, not to a separate sheet. The rep should open the lead and see the profile, the classification and the one-line reason without opening anything else.

Include the message the person wrote, verbatim. It is the best personalization input in the whole record and it is free.

Do this now

Take 50 recent leads

Real ones, ideally from a week you remember.

Run the triage prompt

Compare the classification against what happened

Did the high-fit, high-intent leads convert?

Check the low-confidence rows

Were they genuinely worse, or just harder to enrich?

Adjust the bands

Based on that comparison.

Wire the output to the CRM

Including the verbatim message.

Schedule it

Daily, or on arrival if you have the inbound pipeline from Automated Inbound.

Check your work

Verification runs before any enrichment
Free-mail addresses have their own path
Every lead has a confidence flag alongside its bands
No band means “no response”
Output reaches the CRM record, not a separate sheet

Where this breaks

Triage that arrives after the rep has already responded is wasted spend. If your process has a rep touching leads within minutes, a nightly triage job adds nothing — the enrichment has to be part of the intake, not a batch behind it. Either move triage to arrival, or accept that its value is in the follow-up rather than the first touch.

Further automation

The full real-time version is Automated Inbound: the same chain, triggered by the form submission rather than by a schedule, completing before the rep opens the notification. This lesson is the batch version, and it is the right starting point — prove the chain, then move it earlier.

Next lesson

06 — Weekly signal digest, the third and last central job.

Reference for this lesson: verify_email, enrich_person, enrich_organization, Automated Inbound.