What the 24-hour window actually is

The rule is simpler than the way most documentation describes it. When a customer sends your Instagram Business account a DM, Meta starts a 24-hour timer. During those 24 hours, you can reply — with whatever you like, including marketing or promotional content. When the customer replies to you, the timer resets. When 24 hours pass with no further message from the customer, the window closes.

After the window closes, Meta’s Graph API refuses to send your reply. The HTTP response comes back with error code 10 and a message saying your message is outside the messaging window. The customer doesn’t see anything — they don’t get a failed-to-deliver notice, they don’t see a half-typed reply. From their side, it’s silence.

Here’s the timer in a typical exchange.

A typical 24-hour cycle

Mon 09:00Customer DMs: “Hi, do you ship to Australia?” Window opens. Closes Tue 09:00.
Mon 17:00You reply: “Yes, here are the shipping options.” No change to the window.
Mon 18:00Customer replies: “Great, ordering now.” Window resets. Closes Tue 18:00.
Tue 18:01Customer goes quiet. Window starts closing in.
Wed 18:01Window has now closed. Your next send to this conversation will fail with error 10 unless the customer messages again.

Why this is closer to a sharpener than a restriction

If you’d asked a customer service team in 2015 to define a good response time, they’d have said something like “under an hour during business hours, same day otherwise.” That’s a tighter bar than 24 hours. Meta’s window is actually generous compared to what most customers carry around as their internal stopwatch.

So when the window catches a team out, it isn’t telling you anything new. It’s surfacing a gap that already existed in the customer experience. The team that gets bitten by the 24-hour rule is the team that was already losing customers to delayed replies — they just weren’t measuring it.

In that sense the window is a useful diagnostic. A team that replies within a few hours never thinks about it; a team that hits it regularly has something to look at upstream — not in Meta’s rules, in their own coverage rhythm.

If you can’t reply to a customer within 24 hours, the right question isn’t “how do we extend the window?” The right question is “why aren’t we replying within 24 hours, and is that the customer experience we actually want?”

The 24-hour window is closer to a friendly nudge in the direction of behaviour your customers already expect — reply quickly, reply personally, reply roughly within the time it takes them to remember why they messaged you.

The one operational trick worth knowing

For the times when a real answer can’t happen inside the window, one tactic solves most of the practical problem.

The window resets when the customer messages. It doesn’t reset when you do. So if a conversation is approaching its limit and you don’t have a real answer yet, send a holding reply that invites a response.

Not “we’ll get back to you soon” — that’s a dead end. A small question that needs their input:

The customer feels attended to, and the window resets when they reply. It isn’t a workaround: a clarifying question is doing something for the customer rather than holding them up with a non-answer. The Meta timer just happens to reward it.

Five tactics for working with the window

1. Make the clock visible.

The single biggest cause of late replies is conversations that look like the others until they’re suddenly out of time. Whatever tool you use, you should be able to see at a glance which conversations are approaching their expiry — before they hit it. The morning briefing should highlight what’s closing today. The inbox sort should let you order by urgency. If your tool can’t do this, you’ll lose conversations to delays you didn’t see coming.

2. Plan your weekend coverage.

If most of your DM volume arrives Friday night and Saturday, you cannot wait until Monday. Even ten minutes of phone-based inbox time on Saturday afternoon — one person, sending the holding-reply pattern above — keeps every active conversation alive. The reply doesn’t need to solve anything. It just needs to invite the customer back into the thread.

3. Send holding replies that invite responses.

The pattern from the section above is the most useful single tactic in this whole article. Ask a small question whose answer extends the conversation naturally. Customer-friendly, window-friendly.

4. Treat the window as a diagnostic, not an obstacle.

If you’re hitting the window regularly, the answer isn’t to look for workarounds. The answer is to ask why your reply rhythm has drifted out past a day. Most customers expect an answer within a few hours during business hours; the fact that you have 24 doesn’t mean you should use them. Use the window as a quiet metric: how often did we hit the wall this month?

5. Be honest about closures.

For genuine PTO — Christmas, August closure, anything more than a few days — the right move is to tell people. Set an away message in the run-up to the closure. Reduce inbound volume by being public about it on the feed. Don’t try to game the window with clever automation. A small, honest “we’re back on the 7th — thanks for your patience” beats any workaround.

How Vidual Inbox helps

Conversations carry a status, and we know when the customer last messaged. The conversation list sorts to surface what’s closing soon. Our Up Ahead feature includes a “closing soon” section in the morning briefing — if a conversation is about to expire, it shows up alongside the day’s reminders and follow-ups so it doesn’t get lost behind everything else.

Assignment makes ownership visible. When a DM lands at 11pm, the team knows by 9am who’s on it. The mobile-first interface means a holding reply is two taps from your phone — weekend coverage doesn’t mean opening a laptop.

The combination — visibility plus mobile reach — usually means a small team rarely needs to think about the rule at all. Conversations naturally stay alive. The window does the quiet work of keeping replies prompt without anyone having to count down to it.

The healthier frame

Most teams that hit the 24-hour wall do so because something upstream broke down — a message that arrived out of hours, or a question nobody owned. The window flagged a coverage gap that was already there.

That’s worth knowing. If you’re hitting it more than occasionally, the answer isn’t to work around the rule — it’s to ask whether your customers are happy with the response time you’re actually delivering. The Meta limit is 24 hours; your customers’ patience is shorter than that anyway. If you build the rhythm that keeps your customers happy, the window takes care of itself.

If you’re running customer service across email and Instagram and you’ve thought about the timer more than you’d like, have a look at Vidual Inbox. The trial is fourteen days, no card required, every feature in from day one.

Vidual Inbox is available now at vidualinbox.com. 14-day free trial, no credit card required. £24.99/month after that, every feature, every team member.