Enrich Contact Skill

The Enrich Contact Skill takes any contact — a name and company, an email address, or a LinkedIn URL — and returns their current verified profile via Lusha. Title, seniority, department, direct dial, business email, and tenure in their current role. If they’ve moved on, the skill flags it and returns where they went. If their email has changed, it returns the current one.

This is the skill for the moment before you reach out. Before you draft the email. Before you build the brief. Before you add the record to the CRM. One call to the Lusha in Claude connector and you know exactly who you’re dealing with — not who they were six months ago.

No list needed. No batch process. Just a contact, a question, and a verified answer.

What it does

  • Current title and seniority verification — confirms the contact is still in the role on record, or returns the updated title if they’ve been promoted or moved.
  • Live email verification — returns a verified business email address confirmed against Lusha’s database. Flags bounced or invalid emails and returns a replacement where one exists.
  • Direct dial enrichment — returns a verified direct dial or mobile number where available. Flags when none is found rather than returning a switchboard.
  • Departure detection — if the contact has left the company, flags it immediately and returns their new employer and title where Lusha has the data.
  • Tenure signal — returns how long the contact has been in their current role. Under 6 months flags as a recent hire — a timing signal worth knowing before you reach out.

Use cases

Before any outreach

You have a contact from a list, a CRM export, or a referral. Before you write the email, run the skill. Thirty seconds to confirm they’re still in seat, their title is current, and the email won’t bounce. The alternative is finding out after you send it.

Before updating the CRM

A rep is about to log a call or update a contact record. Run the skill first. If the contact has moved on or been promoted, the CRM gets the right data from the start — not a stale record that quietly degrades for months until someone bounces an email.

During deal review

You’re reviewing an open deal and want to confirm your key contacts are still in seat. Run the skill on each one. A champion who left two months ago is a deal risk — this surfaces it before the manager has to ask.

Skill definition

The instructions Claude uses to run this skill. Copy it into a .md file in your Claude Code skills folder, or paste it into a Claude project as a custom instruction.

Example outputs in this skill are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the skill with your own data and connectors to see live results.

---
name: enrich-contact-skill
description: >
  Look up any contact's current verified profile via Lusha.
  Takes a name and company, email address, or LinkedIn URL.
  Returns current title, seniority, department, verified email,
  direct dial, tenure, and departure flag if the contact has
  moved on. Single contact lookup — fast, verified, no guessing.
connectors:
  required: lusha
campus_url: https://www.lusha.com/campus/plays/enrich-contact-skill/
category: Skills
---

# Enrich Contact Skill

Look up a contact's current verified profile via Lusha. Return
their current title, verified email, direct dial, seniority,
department, and tenure. Flag departures. Flag recent hires.
Return one clean, verified record.

## Input

The user will provide via $ARGUMENTS one of:

- Name and company (required if no email or URL supplied)
- Email address — used to look up the contact directly
- LinkedIn URL — resolved to a Lusha contact record

If none of these are supplied, ask once. If the user provides
a list of contacts, process them one by one and return a table.

## Workflow

1. Resolve the contact via Lusha.
   Use contacts_search with the supplied identifier:
   - Name + company: search by name and company name
   - Email: search by email address directly
   - LinkedIn URL: resolve via Lusha's LinkedIn matching

   If no confident match is found, flag it clearly and ask
   the user to confirm the name spelling or company before
   continuing. Never guess.

2. Verify and enrich.
   For the matched contact, retrieve:
   - Current title and job function
   - Seniority level
   - Department
   - Verified business email
   - Direct dial and mobile number
   - Current company and tenure in current role
   - Previous company (if recently changed)

3. Classify the contact status.
   Based on the data returned, assign one of:
   - Active — contact is confirmed in the role on record
   - Promoted — title has changed, still at same company
   - Departed — contact has left the company
   - Recent hire — tenure under 6 months at current company
   - Unverifiable — contact not found in Lusha database

4. Return the enriched record.
   One clean output. Privacy rules applied.

## Output Format

### Contact profile

| Field | Value |
|---|---|
| Name | [initials only — e.g. J.K.] |
| Current title | |
| Previous title | [if changed] |
| Seniority | |
| Department | |
| Company | |
| Tenure | |
| Status | Active / Promoted / Departed / Recent hire / Unverifiable |
| Verified email | [domain only — j.k@[company].com] |
| Direct dial | [masked — +1 415 555 ••••] |
| New employer | [if departed — company name only] |

Contact confirmed live via Lusha connector, [date]

---

Flag notes:
- Recent hire (under 6 months): likely evaluating inherited
  tools and vendor relationships. Higher receptivity window.
- Departed: do not reach out at old address. If new employer
  is returned, consider whether to follow the contact.
- Unverifiable: contact not found in Lusha database. Recommend
  verifying name spelling, company, or trying LinkedIn URL.

---

If the user supplies multiple contacts, return a table:

| Name | Title | Company | Status | Email | Direct Dial |
|---|---|---|---|---|---|

Flag any departed or unverifiable contacts below the table.

---
Built by: Lusha
Tools: Claude, Lusha
Type: Skill

FAQ

  • Do I need anything beyond Lusha in Claude?

    No. The skill runs entirely through the Lusha in Claude connector. Connect it once in Claude settings and it’s available for every contact lookup from that point on.

  • What identifiers does it accept?

    Any of three: a name plus company name, a business email address, or a LinkedIn URL. Name and company is the most common starting point. If you have the email already, that’s the fastest lookup. LinkedIn URL works well when the name is common and you need to pinpoint the right person.

  • How is this different from the Data Quality Skill?

    The Data Quality Skill is built for lists — it runs verification, enrichment, and deduplication across hundreds of records in one pass. This skill is built for a single contact in the moment before you act on them. Faster, simpler, no list required.

  • What happens if the contact has left the company?

    The skill flags it immediately as Departed and returns their new employer and title where Lusha has the data. It also suppresses the old contact details so you don’t accidentally reach out to a dead address. If you want to follow the contact to their new company, the new employer name gives you a starting point.

  • What does the tenure signal tell me?

    How long the contact has been in their current role. Contacts with under 6 months of tenure are flagged as recent hires — they’re likely still evaluating their inherited tool stack and vendor relationships, which makes them more receptive to outreach than someone who has been in seat for three years and has everything locked in. It’s a small signal but a consistently useful one.

Related Plays

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs