How to reply to your positive replies
How-to guide Updated 12 July 2026
How do you reply to positive cold email replies with AI?
Ask Claude to pull your unanswered positive replies from the HotHawk Master Inbox, read the thread, then either send the reply itself or write it as a draft for you to check. It replies on the same thread from the same mailbox, so you clear the warm ones the same day they arrive.
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
Show me the positive replies from this week I haven't answered yet.
Claude callsmcp__hothawk__search_threadslabel "Interested" status unreplied range last 7 daysClaude lists the warm threads sitting in your Master Inbox, including the forwarded and CC'd ones you might have missed, so nothing hot is left waiting on a shelf.
-
2
You ask Claude
Open the one from the ops lead at Northwind and read the whole thread.
Claude callsmcp__hothawk__threads_messages_getthreadId Northwind threadIt reads the full back and forth, so the reply picks up the actual question they asked instead of a generic "thanks for getting back to me".
-
3
You ask Claude
Reply and offer three slots for a call next week.
Claude callsmcp__hothawk__send_emailthreadId Northwind thread body your replyThe reply goes out from the same mailbox that started the conversation, keeping the thread clean. Same day, while they are still warm.
-
4
You ask Claude
For the tricky one, write it as a draft so I can check it first.
Claude callsmcp__hothawk__email_messages_drafts_createthreadId the tricky thread body suggested replyThe draft sits in the thread ready for you to tweak and send. AI does the first pass, you keep the final word on the ones that matter.
The reply you send today is worth more than the one you send Thursday
A positive reply is the whole point of the campaign, and it is also the easiest thing to fumble. The email arrives mid-morning, you are heads down on something else, and by the time you circle back it is three days old. The buying signal is still there. The heat is gone.
Speed is the edge you actually control. You cannot make more people say yes, but you can be the one who answers first, on the same day, while your name is still the one in their head. That is what this flow is for: get the warm threads in front of you and clear them before they cool.
Find them, read them, answer them
The reason this is quick is the Master Inbox. It catches every reply across every mailbox you send from, and it does not miss the awkward ones: the reply that got forwarded to a colleague, the one where you were CC'd in, the "let me loop in our head of ops". Those are often your best leads and the easiest to lose in a normal inbox.
Because reply management runs on labels, Claude can search for exactly the threads you care about, the ones tagged interested that you have not answered, and hand you the shortlist. Then it reads the full thread before writing a word, so the reply answers the real question rather than a polite nothing. You send from the same mailbox on the same thread, and the conversation stays clean.
Send it, or draft it, your call
Not every reply carries the same weight. A "sure, send me a time" you can fire straight back. A reply from the buyer you have been chasing for a quarter, you probably want to read twice. So you get both. Ask Claude to send and it goes out. Ask it to draft and the reply sits in the thread for you to sharpen first.
Everything still moves through the same warmed, rotated mailboxes as the rest of your sending, and every answer that comes back arrives in the Master Inbox to be tagged and handled again. You are not bolting on a separate tool for replies. You are working the inbox you already have, faster.
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__search_threadsFind the positive replies you owe an answer -
mcp__hothawk__threads_messages_getRead the full thread before you reply -
mcp__hothawk__send_emailSend the reply on the same thread -
mcp__hothawk__email_messages_drafts_createWrite it as a draft for you to check
Frequently asked
Will Claude send replies without me seeing them?
Only if you ask it to. Tell it to draft and the reply waits in the thread for you to read, edit and send. Tell it to send and it goes out. On a genuine positive, most people draft the first few, then let it send the simple ones once they trust the tone.
How does it find the positive replies in the first place?
The Master Inbox catches every reply across all your mailboxes, including the forwarded, CC'd and out of office ones, and reply management runs on labels. Claude searches by label and by whether you have answered, so the warm threads surface instead of sitting buried under bounces and auto-replies.
Can I keep the reply on the original thread?
Yes, and that is the default. It replies on the same thread from the same mailbox that sent the first email, so the conversation reads as one clean exchange rather than a fresh cold email out of nowhere.
Why does replying fast matter this much?
A "yes, tell me more" has a short shelf life. Reply the same day and you are still the one they were thinking about. Leave it three days and they have moved on, or a competitor got there first. The Master Inbox surfaces the reply, Claude helps you clear it before it cools.
Do I need to write code?
No. Everything here runs in plain language over the MCP server. The same search, read and send actions are in the REST API if you would rather build them into your own stack.