How long should your setter wait before replying?

A setter that answers in 400 milliseconds tells the person on the other side exactly one thing: nobody read this. It doesn't matter how good the copy is. The speed itself is the tell.

So we did the obvious thing and slowed it down. Then we slowed it down too much, watched leads go cold in the twenty minutes we made them wait, and spent six weeks finding the middle. Three channels, about 4,100 conversations, one variable.

What the delay actually buys you

Two things, and they pull in opposite directions. A pause buys credibility: the answer reads like it came from a person who had to think. A pause also costs attention: every second is another second for the tab to close.

Which one wins depends entirely on where the message came from — not on what it says.

Cold traffic needs the pause. Warm traffic doesn't.

Someone who just tapped a reel has no relationship with you. An instant, perfectly-formatted reply confirms they landed in an automation, and the thread dies polite. Twelve seconds is enough to break that read.

Someone who typed their number into a form and then messaged you on WhatsApp is already expecting to be handled. There, waiting is just waiting. Three seconds tested better than thirty.

The delay is not about looking human. It's about matching the speed the person already expects on that channel.

The four rules we kept

1. Never answer faster than a person could have read the message. Under two seconds is a tell.
2. Never make cold traffic wait more than twenty seconds for the first reply.
3. Keep the delay identical inside one thread. Speeding up mid-conversation reads as scripted.
4. Change one channel at a time, in five-second steps, and give it a full week.

What to do on Monday

Set Instagram to twelve seconds, WhatsApp to three, Messenger to eight. Leave them alone for a week, then look at one number: how many people answered the setter's second message. Move in five-second steps, never more.

If a channel gets worse when you slow it down, that channel's traffic is warmer than you thought. That's a finding about your funnel, not about the delay.