How to draft cold email replies for approval
How-to guide Updated 12 July 2026
How do you draft cold email replies for approval?
Ask Claude to read a reply in your HotHawk Master Inbox and write the answer as a draft. It sits in the thread and sends nothing until you approve it. Refine the wording as many times as you like, then hit send. The AI does the typing, you keep the final say on every reply.
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
Read this reply and draft an answer, but don't send it.
Claude callsmcp__hothawk__email_messages_drafts_createthreadId the reply thread body suggested replyClaude reads the full thread and writes the reply straight into the draft, ready in the same thread. Nothing goes out. It waits for you.
-
2
You ask Claude
Keep it shorter and open with a question about their timeline.
Claude callsmcp__hothawk__email_messages_drafts_createthreadId the reply thread body revised draftIt rewrites the draft to your note. You can go back and forth as many times as you like until the reply sounds like you, not like a template.
-
3
You ask Claude
Draft replies for all six interested threads from this morning.
Claude callsmcp__hothawk__email_messages_drafts_createthreadId each interested thread body one draft per threadSix drafts, each written to its own thread. You open the inbox, read each one, tweak what needs tweaking and hit send. The typing is done, the judgement is yours.
The problem with both extremes
There are two ways teams usually handle replies and both have a catch. Write every answer yourself and you are the bottleneck: the warm ones wait while you get to them. Let an AI send replies with no check and you save time right up until the day it answers a real buyer in a tone you would never use, and you find out after it has gone.
Drafting for approval is the middle path, and for most reply handling it is the right one. The AI takes the slow part, reading the thread and writing a solid first pass. You take the part that actually needs a person, the read and the send. Nothing leaves without you.
How the draft flow works
You point Claude at a reply and ask it to draft an answer. It reads the whole thread, writes the reply straight into the same thread, and stops. The draft sits there like one you started yourself. Not happy with it? Tell it what to change, shorter, warmer, lead with a question about timing, and it rewrites. You can go round as many times as you need until it reads like you.
When the answer is right, you send. That send is always yours, a deliberate action, never something that happened while you were looking away. And because the reply moves through the same warmed, rotated mailboxes as the rest of your sending, the approval step changes who writes the reply, not how it reaches the person.
It scales without taking over
The quiet win is batching. Ask Claude to draft answers to all six interested threads from this morning and you get six drafts, each written to its own thread and its own context. You open the inbox and it reads like your future self already did the hard part: skim, tweak, send, skim, tweak, send. Ten minutes clears what used to be an hour.
And you stay in control the whole way. Draft is the default, sending is a choice, and you can hand over more only when you trust it. Pair it with triage so the inbox is sorted before you draft, and the warm replies practically queue themselves up for a quick yes from you.
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 replies that need answering -
mcp__hothawk__threads_messages_getRead the thread so the draft fits the context -
mcp__hothawk__email_messages_drafts_createWrite the reply as a draft for you to approve
Frequently asked
Does a draft ever send on its own?
No. A draft sits in the thread and does nothing until you send it. That is the whole point of this flow: Claude writes, you read, you decide. If you want it to send automatically you have to ask for that separately, so a draft is never a send by accident.
Can I edit the draft before it goes out?
Every time. The draft arrives in the thread exactly like one you started yourself, so you can rewrite a line, cut a paragraph or change the ask before you send. Most people nudge the first few, then find the drafts need less and less.
Why draft instead of just letting it send?
Because replies are where the deal is won or lost, and a wrong-tone answer to a real buyer costs more than the minute it saves. Drafting is the middle ground: the AI does the typing, you keep the final say. You get the speed without handing over your voice.
How does Claude know what to write?
It reads the whole thread first, so the draft answers the actual question rather than a generic one. You can also tell it your tone, your usual next step and anything off limits, and it drafts to that. The more you steer it, the closer the first draft gets.
Do I need to write code?
No. The whole flow runs in plain language over the MCP server. The draft action is in the REST API too if you want to build an approval step into your own workflow.