Community in DMs: what to automate and what to answer yourself

Three queues that look like one

What arrives from social is not "the inbox". It is three different things sharing a screen, they are not answered the same way, and treating them as one is where most of the trouble starts.

A direct message is a conversation with one person, with no audience watching. You can ask a question, request a detail, correct yourself without leaving a public record. A comment is a public reply under a piece, and what you write there is read mostly by the people who did not comment. A review is the hardest of the three: public, permanent, attached to a score, and the first thing somebody sees when they find you on a map.

Three different standards come out of that. In a direct message you resolve. In a comment you answer briefly and take the detail to private, because a long public thread reads like an argument even when it is an explanation. And every review gets a reply, the good ones included, because the reply is written for whoever reads it next rather than for the person who left it.

What each network actually delivers

Before promising a response time, it helps to know what is going to arrive. Not every connected network produces all three things, and four of the fourteen produce none of them: there you publish and nothing comes back.

Two readings of that table change how you staff the week. The first: reviews only arrive from Google Business and from Facebook Pages, so if you have a physical location, the queue most likely to cost you money is the one you look at least. The second: outbound attachments exist on four networks, and on Instagram they do not include documents, so a rate card PDF cannot go out that way and is better kept on a page you can link to. How all of it is grouped into one thread per person is on the inbox page.

The clock belongs to Meta, not to your internal policy

There is a widespread idea that replying within 24 hours is a best practice. On Instagram and Facebook it is not a practice, it is the limit of the system: 24 hours after the person's last message, the conversation stops accepting a freely written reply and only takes what the platform counts as a template. That is why a message is marked overdue at 24 hours rather than at 48.

Three operational consequences follow. A message arriving on Friday afternoon expires on Saturday, so either somebody works the weekend or the public promise cannot include the weekend. Night time notifications do not need answering, but they do need counting, because a spike of messages at eleven at night tells you when your audience is awake. And a fast short reply beats a perfect late one, because the late one sometimes no longer fits.

What can be automated without it showing

Useful automation in messaging is narrower than it is usually sold. What exists here is a rule: somebody writes a specific word and a direct message goes out with whatever that word promised. It works on Instagram and Facebook, the two networks where the platform opens that door, and it fires from a comment, from a story reply (Instagram only) or from a direct message.

Three details separate a rule that helps from a rule that annoys.

• The keyword has to be unusual. "Info" turns up in the middle of sentences and fires the rule at people who never asked. A word invented for that one piece, said in the video and written in the caption, does not trigger by accident.
• The first message says what it is. One short line, the link, and a way through to a person. The recipient already knows they asked for something, so pretending to hold a conversation fools nobody and only lengthens the thread.
• A follow requirement is asked, not checked. There is no platform lookup that says who follows you: the rule asks the person and reads their reply. Worth knowing before you build a promotion on top of that condition.

The links that go out this way are short, /r/ plus a code, and they can be counted. That is what turns a rule into something measurable: how many triggered it, how many opened the link, and which piece they came from. The full detail is in the Instagram Auto DM guide.

On cost there is one thing worth understanding before you scale. The contacts reached by that automation are the only soft ceiling in the product: nothing is blocked when you reach it, the message still goes out, and the excess is billed per contact. The entry tier of each profile carries that ceiling and the tiers above it do not, so an account using this seriously stops having the problem by moving up. The current terms are on the pricing page.

What never gets automated

Four things should never come out of a rule, however repetitive they look.

The first is a complaint. An angry person who gets an automatic reply gets twice as angry and usually says so in public. The second is a price with conditions: if the right answer depends on three facts you do not have, the rule will confidently give the wrong one. The third is anything containing a personal name, because the moment an automation calls somebody by the wrong name is the moment it becomes obvious. And the fourth is a review, with no exceptions: an automatically answered review is worse than an unanswered one.

Splitting the queue without stepping on each other

With two people watching the same inbox, the problem stops being volume and becomes duplication. Two different replies to the same person within ten minutes do more damage than one late reply.

What works is splitting by queue rather than by shift. One person takes direct messages, another takes public comments, and reviews go to whoever can actually commit to something, which is often not the social media person. Inside each queue the order is by age and not by ease, because if everybody picks what they know how to answer, the hard ones get old enough to expire.

Agree what a finished thread looks like as well, because that is where two people most often disagree. A message is done when the person has what they asked for, not when a reply has been sent, and a thread closed on the second definition comes back a day later with the same question rephrased.

Write down the four or five answers you have already given a hundred times and keep them somewhere shared. That is not automation, it is not drafting the summer opening hours from scratch every July. How the inbox is organised when it arrives from several networks at once is covered in more depth in the unified inbox guide.

What the inbox tells you about the account

Messages are the qualitative signal the metrics never give you. If the same question turns up fifteen times in a month, that is not a support incident: it is a hole in your content, and the piece that fills it will work, because you already know the demand is there.

Watch the direction of travel too. An account that holds its reach and suddenly gets half the messages has a different problem from an account that loses reach and holds the messages: in the first one, the content is arriving and no longer inviting anybody to write. That reading, along with the other six worth making in order, is in the guide on what to do when an account stops growing.

One last rule, and it is the cheapest of them all: answer everything before publishing more. The person who wrote has already given you their attention, and an inbox three days behind costs more than a week without posting.