Automated Reply Enrichment

The workflow

Play 17

Automated Reply Enrichment

1Fire the moment someone replies

Prospect replies to a campaign

Reply event to a Clay webhookInstant

No polling and no hourly batch. Speed to lead is the whole point.

2Normalise every reply

One consistent shape

EmailLinkedIn URLTitleCompanyReply text

Deduped against contacts already in the table before anything reads it.

3Classify, then enrich only Interested

Classify the reply

InterestedNeutralNot interestedOut of office

Everything the rep needsInterested only

Direct phoneFundingHeadcountTech stack

The rep opens the record and it is already complete. The phone is checked live before it is shown.

Phone

BetterContactFullEnrich

Company

Clay

Suppress or re-queueEverything else

Not interested is suppressed. Out of office is re-queued for the return date. Neutral gets a human read.

Queue

Smartlead

4Sync to HubSpot without duplicates

Match foundHubSpot action

Email matches a contact→Update that contact

No email match, domain matches→Create contact on that company

No match at all→Create contact and company

Reply text and classification stamped on the record

5Alert the rep

Slack alertUnder a minute

The full enriched profile in the alert, not just a name, with links to act straight away.

Links

HubSpotLinkedIn

Call

Nooks

Interested replies answered in minutes

The stackSmartleadClayClaudeBetterContactFullEnrichSlackHubSpotLinkedInNooks

Oriel · GTM plays library

Open full size

The diagram as text

1. 1

   Fire the moment someone replies

   Prospect replies to a campaign: Tool: Smartlead.

   Reply event to a Clay webhook (instant): No polling and no hourly batch. Speed to lead is the whole point. Tool: Clay.

2. 2

   Normalise every reply

   One consistent shape: Email, LinkedIn URL, Title, Company and Reply text. Deduped against contacts already in the table before anything reads it. Tool: Clay.

3. 3

   Classify, then enrich only Interested

   Classify the reply: Interested, Neutral, Not interested and Out of office. Tool: Claude.

   Everything the rep needs (interested only): Direct phone, Funding, Headcount and Tech stack. The rep opens the record and it is already complete. The phone is checked live before it is shown. Phone: BetterContact and FullEnrich. Company: Clay.

   Suppress or re-queue (everything else): Not interested is suppressed. Out of office is re-queued for the return date. Neutral gets a human read. Queue: Smartlead.

4. 4

   Sync to HubSpot without duplicates

   Match found → HubSpot action

   • Email matches a contact → Update that contact
   • No email match, domain matches → Create contact on that company
   • No match at all → Create contact and company

   Reply text and classification stamped on the record

5. 5

   Alert the rep

   Slack alert (under a minute): The full enriched profile in the alert, not just a name, with links to act straight away. Links: HubSpot and LinkedIn. Call: Nooks. Tool: Slack.

   Outcome: Interested replies answered in minutes. Tools: Slack and HubSpot.

The stack: Smartlead, Clay, Claude, BetterContact, FullEnrich, Slack, HubSpot, LinkedIn and Nooks.

Open the diagram full size (1180 px wide)

The play in six steps

1. 01

   Step 1: Trigger on the reply

   Reply speed decides whether an interested prospect books. A webhook fires in seconds, a sync job fires in hours.

   • Post every reply event from Smartlead to a Clay webhook.
   • No polling, no scheduled export.
2. 02

   Step 2: Normalise in Clay

   Every later step reads the same fields. Get every reply into one shape first.

   • Store email, LinkedIn URL, title, company and the reply text.
   • Dedupe against contacts already in the table, so a second reply updates the row instead of creating one.
3. 03

   Step 3: Classify the reply

   One AI call decides the path. Enriching every reply wastes credits on people who said no.

   • Run one Claude prompt that returns Interested, Neutral, Not interested or Out of office.
   • Only Interested continues to enrichment.
   • Not interested: suppress across every campaign. Out of office: re-queue for the return date in the message.
   • Neutral replies ("who are you", "send more info") go to a human, not back into automation.
4. 04

   Step 4: Enrich the interested replies

   The rep should open the record and already know who they are calling and why the timing works.

   • Find a direct phone with BetterContact, falling back to FullEnrich.
   • Check the number is live before it reaches the rep. Drop dead or landline-only results.
   • Add company funding, headcount and tech stack from Clay, and the LinkedIn profile.
5. 05

   Step 5: Sync to the CRM without duplicates

   A duplicate record created off a reply splits the history and confuses ownership.

   • Match on email first, then on company domain.
   • Update the contact when found. Create it, and the company if needed, when not.
   • Stamp the reply text and classification on the record.
6. 06

   Step 6: Alert the rep

   The output is a Slack message a human can act on in under a minute.

   • Put the full enriched profile in the alert, not just a name.
   • Link straight to the HubSpot record and the LinkedIn profile, with a call button through Nooks.
   • Reply to the prospect within the hour, ideally while they are still in their inbox.

Tools used

The nine tools this play names. Each links to the other plays that use it.

SmartleadClayClaudeBetterContactFullEnrichSlackHubSpotLinkedInNooks

Related plays

Play 13

Speed-to-Lead with AI Voice and SMS

1Catch the request the second it lands

Demo or contact form submittedConsent box ticked

What the form already tells you

NameWork emailMobileCompanyWhat they asked for

The consent line on the form covers calls and texts about this request, and nothing else.

2Qualify before anyone dials

Enrich the company and the person

HeadcountIndustryRoleSeniority

With

ClayApollo

Verify

Twilioline type lookup, mobile or landline

Gate1

Inside the ICP, real company, real person

Students, vendors and competitors are filtered out here.

× Not a fitpolite email, no call

3Respond inside five minutes

AI voice callMinute 1

Confirms the request, asks two qualifying questions and offers two times from the live calendar.

Call

Retell AI

Book

Cal.com

SMS follow-upMinute 3

One plain text from a named person with a booking link. No marketing copy.

Send

Twilio

If no answer

4Hand the conversation to a human

Booked

The call transcript and answers go onto the contact before the meeting.

Log

HubSpot

Alert

Slack

Asked for a person

The owner gets a Slack alert and calls back the same hour.

Alert

Slack

Call

Nooks

No response

A short email sequence takes over. No more calls.

Send

Smartlead

Every inbound request answered in minutes

The stackHubSpotClaudeClayApolloTwilioRetell AICal.comSlackNooksSmartlead

Oriel · GTM plays library

Play 13Inbound

Speed-to-Lead with AI Voice and SMS

5 steps · Website, Call, SMS, Email, CRM

+4 more

Play 19

Meeting Prep and Follow-Up

1Pull tomorrow's meetings

Booked meetings with an external attendeeDaily run

2Research the company, the people, the history

Company

NewsHiringFunding

Searched inside an absolute date window.

CRM history

Deal stageOwnerLast emails

Falls back to attendee email when no deal is linked.

Past calls

NotesOpen items

What they already said, so nobody asks twice.

3Around the call

The briefDay before

Who is coming, what changed, what is still open, a suggested agenda.

Write

Claude

Post

Slack

Save

HubSpotlink on the deal

Reminder to the attendeeDay of

A short note with the time and the link, sent to the number they gave when booking.

Text

WhatsAppTwiliobooked meetings only

The transcriptAfter

A webhook fires when processing ends. Poll until it has sentences.

Fetch

Fathom

The call

4One meeting, one record

Gate1

Same meeting id

A repeat webhook for one transcript is dropped.

× Repeat webhook

Gate2

Same client, title and date

Several recorders in one call make several transcripts with different ids.

× Duplicate recording

5Recap, route, follow up

Recap

Decisions and open questions, posted to the account channel.

Post

Slack

Action items

Each one goes to the person who committed to it, else the owner.

Extract

Claude

CRM and follow-up

Next step on the deal. The email is drafted, a human sends it.

Log

HubSpot

Draft

Gmail

Text

WhatsAppexisting chats only

Every call prepped the day before, followed up the same day

The stackGoogle CalendarExaHubSpotFathomClaudeSlackWhatsAppTwilioGmail

Oriel · GTM plays library

Play 19Inbound · Outbound

Meeting Prep and Follow-Up

6 steps · Email, CRM, WhatsApp, SMS

+3 more

Play 24

CRM Hygiene

1Audit, read-only

Snapshot and fill rates0 records written

TitleLinkedInCountryEmail validityPhone validitySegment

Export first, measure every field, and trace which integration created each record.

Export

HubSpotSalesforce

2Detect the dirty sets

Dirty setFix

Duplicate person or company→Merge, survivor picked by rule

Contact not linked to its account→Link to the account

Job changer→New contact, old one marked gone

Bounced email or dead number→Replace and verify

Missing fields→Fill blanks only

Lead with no account→Match on domain

3Match duplicates carefully

Gate1

Same company domain

A name match only counts when the domain matches too.

× Different people

Gate2

Not a shared key

A switchboard number or a common firm name is never the key.

× Shared line

Gate3

Not a role inbox

A person's name stamped on info@ is a field to fix, not a merge.

× Fix the field

4Approve, back up, then write

The change set

Saved as a list view or report the owner can open.

Backup export

Every record in the change set, before anything moves.

Then

Owner approves the exact listYes unlocks the write

Write unlocked

Every change is logged with its old value, so any field can be restored.

5Fill blanks, catch job changers

Enrichment waterfall

Only the misses move on. Fill blanks, never overwrite a value someone set on purpose.

Profile

Explorium

Email

ProspeoFindymail

Verify

BounceBan

Phone

Twiliolookup, dead numbers cleared

Job changers

Current-employer scan, customers first. The same company under another domain is not a move.

Scan

ClayLinkedIn

Create

New contact, history kept

6Keep it on

Same rules, every new record

New inboundRep-added recordsJob-change signalsWeekly sweep

Report

Slack

A CRM that stays clean, with every change undoable

The stackHubSpotSalesforceClayExploriumProspeoFindymailBounceBanTwilioLinkedInSlack

Oriel · GTM plays library

Play 24Outbound · Inbound

CRM Hygiene

7 steps · CRM

+4 more

All GTM plays