Auto Follow Up After a Reply with AI

How do you auto follow up after a cold email reply?

Build a Sub Sequence in HotHawk and point it at a trigger label. Then have Claude read your Master Inbox, tag the genuinely interested replies, and each tagged thread joins the follow up on its own. You can also enrol any thread by hand, and draft the copy for approval first.

Start your 7 day free trial Connect the MCP server

No credit card required.

Before you start

You need a HotHawk account and the HotHawk MCP server connected to Claude. It takes a couple of minutes and no code. Full setup is on the MCP server page.

Step by step

1

You ask Claude
Create a two step follow up that fires when I tag a reply as Interested.

Claude calls mcp__hothawk__subsequences_create

name "Interested follow up" triggerLabelId "Interested" triggerDelayInMinutes 60 steps 2 steps

The Sub Sequence is built. From now on, any thread tagged Interested joins it on its own, an hour after the tag goes on.
2

You ask Claude
Read today's replies and tag the genuinely interested ones.

Claude calls mcp__hothawk__threads_update

threadId each positive reply label "Interested"

Claude works through the Master Inbox, tags the real buying signals, and each tagged thread drops into the follow up automatically. No hot reply left to go cold.
3

You ask Claude
Add this older thread from last week to it as well.

Claude calls mcp__hothawk__subsequences_subscribe_create

subsequenceId Interested follow up threadId the older thread

That thread is enrolled straight away, no tag needed. Handy for cleaning up replies you sat on.

Time-based follow ups miss the moment

Most follow ups fire on a clock: day three, day seven, day twelve. That works for the people who never answered. It is the wrong tool for the people who did. A "sounds interesting, tell me more" deserves a reply today, not a templated bump next Tuesday because the calendar said so.

The follow up that works is the one that reacts to what the lead actually did. That means it has to start from the reply, not from the send date.

Trigger off a label, not a timer

A Sub Sequence in HotHawk runs off a trigger label instead of the campaign schedule. Tag a thread with the label, and it joins the follow up. The clever part is who does the tagging. Instead of you sifting the inbox, Claude reads each reply and applies the label when it sees a real signal, so the right follow up starts within the hour.

This leans on the two things HotHawk already does well: the Master Inbox that catches every reply, including the forwarded and CC'd ones, and reply management by label. The AI just sits on top, reading and tagging.

Decide how much you automate

There is a spectrum here and you pick the point. Fully hands off, the label triggers the follow up and it sends without you. One step back, Claude tags the reply but drafts the follow up for you to approve. Further still, it only flags the threads and you write everything. All three use the same setup; you are choosing how much to delegate, not rebuilding anything.

Whichever you pick, the follow ups go out across the same rotated pool as the first touch, and every reply to the follow up comes back to the Master Inbox to be tagged again. The loop closes on itself.

The HotHawk tools behind this

Every action here is a real endpoint. Claude reaches it over the MCP server, and you can hit the same endpoints directly from the REST API if you would rather build it into your own stack.

mcp__hothawk__subsequences_create Build the follow up and its trigger label
mcp__hothawk__search_threads Find the replies worth following up
mcp__hothawk__threads_update Tag a reply so it triggers the follow up
mcp__hothawk__subsequences_subscribe_create Enrol a specific thread by hand

MCP server setup Read the API docs

Frequently asked

What is a Sub Sequence in HotHawk?

A Sub Sequence is a short follow up that runs off a reply rather than the original campaign. You point it at a trigger label, and any thread that gets that label joins it. It is how you nurture people who have already answered.

Does the follow up send on its own, or do I approve each one?

That is your call. Point the Sub Sequence at a trigger label and it runs hands off once a thread is tagged. Or have Claude draft the follow up for you to check first. You set how hands off it runs.

How does Claude know which replies are worth following up?

It reads the thread. A "not now, try me in Q4" is different from a hard no, and Claude can tag the first and leave the second. You can also tell it exactly what counts as interested for your offer.

Can I trigger a follow up on something other than a reply?

Yes. Any label can be a trigger, and you apply labels however you like: on a reply, an out of office, or a manual tag. The Sub Sequence fires whenever that label is applied to a thread.

Do I need to write code?

No. Everything here runs in plain language over the MCP server. The same trigger and enrolment actions are in the REST API if you want to wire them into your own workflow.

Keep going

Launch a campaign from Claude Build, fill and send a campaign from a chat Personalise cold email at scale Let Claude research and write to each lead Master Inbox Where every reply arrives and gets labelled AI cold email software The full picture of AI running on HotHawk

How to auto follow up after a cold email reply