The Follow-Up Automation That Recovered $9,000 in Dead DMs

About 60% of the DMs that reach your business inbox will end in silence. The customer asks a question, gets an answer, and never replies again. Most owners read that silence as "not interested" and move on. I spent a year treating dead DMs as a lost cost. Then I built a follow-up automation and recovered $9,000 in a single quarter from conversations I had already written off.

I am the founder of OT1-Pro, a unified inbox with an AI sales agent, and this post is the exact follow-up system I used — the timing, the scripts, the channel rules, and the numbers.

The dead-DM inventory

Before fixing anything, I counted what was dying. For a typical month:

The quiet 60% — 480 conversations a month at my volume — represents more potential revenue than the 40% that actually ordered. The follow-up automation's job was to reclaim even a tenth of it.

Why a single follow-up is the sweet spot

The industry advice is "follow up 3-5 times." That advice was written for cold email, where the recipient never asked you anything. Your DM prospect is different: she already reached out to you. She is warm. The problem is not awareness — it is timing and confidence. One well-timed message is enough. Two feels like service. Four feels like spam, and spam on WhatsApp gets you blocked and reported.

• One follow-up: perceived as helpful reminder. Recovered the most orders.
• Two follow-ups: still acceptable for high-ticket (above EGP 5,000), neutral for low-ticket.
• Three or more: block risk, report risk, brand damage. Avoid.

My rule: one auto-follow-up at 48 hours for order-sized conversations, a second one only for orders above EGP 5,000 and only after another 4 days.

The 48-hour auto-follow-up, scripted

Timing matters more than wording. The sweet spot in my data was 48 hours after the last message: long enough that the recipient is not annoyed, short enough that the intent is still alive. The script that worked:

"Hey! Just checking in — you asked about the [item] a couple of days ago. It's back in stock in your size and we have 10% off until Sunday. Want me to reserve one? (Takes 10 seconds, no commitment.)"

Three components made this convert:

1. A specific hook — "back in stock in your size" is concrete, not "just checking in" alone.
2. A deadline — "until Sunday" creates a reason to answer now.
3. A zero-pressure closer — "(Takes 10 seconds, no commitment.)" lowers the reply cost.

Channel rules for follow-ups

Follow-up rules differ by platform, and violating them gets you punished:

The key insight: on Meta channels (WhatsApp, Instagram, Messenger), the 24-hour customer service window gives you a free reply inside the window, then a single allowed follow-up outside it. If you miss the timing, the next opportunity is 48 hours later — which is exactly when my follow-up fires anyway.

The numbers after a quarter

16% recovery of a 60% dead bucket does not sound dramatic until you convert it: 231 orders, $9,000, from conversations that were already counted as lost.

The mistake that got me blocked (and the fix)

In week three I tested a "bolder" follow-up: "Are you still interested or should I stop messaging you?" It was supposed to sound confident. It read as aggressive. Two customers blocked me and one reported the number. I reverted to the soft version, and the block incidents stopped immediately. The lesson: on WhatsApp, follow-ups that sound like guilt-trips get you banned. The soft restock hook never did.

What not to automate

Some conversations should never go to a follow-up automation:

• Complaints — a complaint answered with a follow-up automation feels like being ignored. Escalate to a human immediately.
• Refund requests — same logic. Never automate a refund thread.
• Conversations where the customer already said "stop" — respect it instantly. Automations that ignore an explicit "stop" are how numbers get reported.
• High-ticket negotiations — above EGP 10,000, always a human, always a personal follow-up.

Setting up the follow-up automation

1. Define the dead-DM trigger: any conversation with more than one AI message and no buyer reply for 48 hours.
2. Write one soft restock/deadline hook per product line. 30 minutes.
3. Set the channel rules (see table above) so you never violate Meta's window.
4. Exclude complaints, refunds, and "stop" conversations.
5. Monitor the first week for wording that reads aggressive, then iterate.

OT1-Pro handles this natively, and it also does the lead qualification behind your follow-up queue. Pricing is at OT1-Pro Pricing. For how the same automation works on WhatsApp specifically, see WhatsApp Sales AI: How to Turn DMs Into Revenue While You Sleep. And if you are weighing OT1-Pro against a broadcast-focused tool before committing, the OT1-Pro vs WATI comparison walks through where each one shines.

Why 48 hours (and not 24 or 72)

The 48-hour timing looks arbitrary, so here is the reasoning from the data I collected before settling on it:

• At 24 hours, you are chasing. The buyer has not decided to ghost yet — she is busy, and a same-day follow-up reads as pressure. In the twenty hours between the silence starting and the 24-hour mark, the recovery rate was the lowest of the three windows I tested.
• At 48 hours, you are helpful. The buyer has moved on, the original conversation is no longer fresh pressure, and your restock hook arrives as genuinely new information. This is the window where the 16% recovery rate came from — most of the 231 orders landed here.
• At 72 hours, you are late. The impulse and the context are gone. By day three, the serious buyer has either bought from a competitor or forgotten she asked. The follow-up then reads as slow rather than attentive.

The one exception is the high-ticket thread above EGP 5,000 — there the second touch is justified because the buying cycle is longer. Everything below that gets exactly one follow-up. One is service. Two is persistence. Three is the number that gets your brand reported.

The three follow-up hooks that worked (and the copy that flopped)

The recovery rate came from the message itself, not just the timing. These are the three hooks that performed, and the ones that did not:

• Restock, specific to their item. "The [item] you asked about is back in stock in your size" — the killer hook, because it gives a concrete reason to reopen the chat. It worked for the largest share of recovered orders.
• The deadline with a price in it. "10% off runs until Sunday" — works when paired with the restock hook, and fails alone, because a bare discount smells like a broadcast.
• The question that reopens, not the update that closes. "Did you end up going for something else? I can help you compare before you decide." Conversational, zero-pressure, and it recovered orders that the two stock-based hooks missed.

What flopped: the guilt-trip ("should I stop messaging you?" — two blocks and one report in a single test), the generic "just checking in" with no hook (reply rate near zero), and any message that mentioned the number "last chance" (reads as spam even when true). Write your hooks from the stock file, not from desperation — the buyer can tell the difference inside two lines.

Bottom line

The most expensive room in your business is the DM you already answered and then forgot. 60% of prospects go silent after one exchange, but 16% of that silence will order if you follow up once, softly, 48 hours later, with a specific hook and a deadline. One automation, one script, one quarter: $9,000 recovered. Build the follow-up before you buy another ad — it sells to people who already talked to you.

Turn the DMs you're already ignoring into revenue

The fastest revenue lift is not more ads — it's answering every lead in under five minutes, day and night. OT1-Pro puts an AI sales agent on your existing WhatsApp, Instagram, and Messenger that closes while you sleep, then hands you the qualified deals with full context. One inbox, one voice, one monthly bill from $8. Free plan, no credit card.

Start free → · Pricing from $8/mo · Why we beat WATI · How AI sales assistants actually work · Talk to me on WhatsApp