← Back to blog

Should You Answer a Customer's Question in a Public Comment or Move It to DMs?

28 September 2026·6 min read
Quick answer: If the answer helps other people who'll read the same comment — pricing ranges, how something works, whether you service an area — answer it publicly, because that reply is doing marketing work for free. If the question involves personal details, a specific complaint, or anything that needs a longer back-and-forth, reply publicly with a warm one-liner and move the detail to DMs. The mistake most businesses make is picking one habit and applying it to everything, instead of routing each question on purpose. 📱

Every comment section is being watched by more people than the one who wrote the comment — which means every reply is actually two decisions at once: what you say to that person, and what everyone silently reading decides about your business because of how you said it. Answer everything publicly and you'll eventually overshare something better kept private. Move everything to DMs and you'll strip your comment section of exactly the social proof that makes people trust you enough to buy. The fix isn't a mood call each time — it's a simple rule for routing. 💖

What most businesses get wrong

  • Defaulting to "DM us" for everything — it feels safe, but it kills the free social proof of a good public answer, and research keeps showing "DM for pricing" quietly costs you leads who move on rather than message.
  • Answering personal or sensitive questions in public out of habit — replying to a specific complaint or personal detail in the comments can embarrass the customer and make onlookers nervous about what else gets aired publicly.
  • Leaving a public question unanswered while you sort out a private reply — a comment sitting unanswered for hours looks like you're ignoring it, even if you're quietly sorting it out behind the scenes.
  • Forgetting to close the loop publicly — moving to DMs without a visible public acknowledgment leaves everyone else wondering if you even saw the comment.
  • Treating every question as equally private or equally safe to answer publicly — a routing decision should take ten seconds, not become a debate every time.
The 10-second routing check — ask these in order, stop at the first "yes":

1. Does this involve personal details (order number, health info, a specific complaint, payment issue)? → Move to DMs.
2. Would the honest answer need more than 2-3 sentences to actually help? → Reply publicly with a one-liner + "sent you a DM with the details 🤍", then move it.
3. Would other people reading this comment want the same answer? (pricing, availability, how something works, whether you do X) → Answer publicly, in full.
4. None of the above? → Default to public — it's free proof that you respond.

The public hand-off line to keep on hand: "Great question! [One honest line of the answer, if you can give one.] Sending you a DM now with the specifics 🤍"

Worked examples

A local service business asked "do you come out to [suburb]?": Answered fully, publicly, in one line — "Yes, we service [suburb] and surrounds!" — because every other local scrolling the comments has the exact same question, and a clear public yes quietly does marketing work for the next six people who never even ask.
A customer commented about a delayed order with specific order details attached: Replied publicly first — "So sorry about this, sending you a DM right now to sort it out 🤍" — then handled the actual details privately. The public reply matters here just as much as the private fix, because everyone watching sees a business that responds, without a single private detail on display.
A B2B firm got a comment asking a genuinely complex pricing question (multiple variables, custom scope): A three-sentence public answer would have been either wrong or misleadingly oversimplified, so the reply was "Depends a bit on scope — sending you a DM so we can get you an accurate answer 🤍", followed by a proper conversation in DMs. Trying to force a nuanced answer into a public comment would have undersold the offer or set the wrong expectation for other readers.

Why the public reply still matters even when you're moving to DMs

The habit worth building isn't "public or private" — it's "always acknowledge publicly, then decide where the substance goes." A comment that gets zero visible response, even one that's later handled perfectly in DMs, still reads to everyone else as a business that doesn't reply. A quick public acknowledgment costs nothing and does two jobs at once: it tells the person asking that you've seen them, and it tells everyone silently reading that questions here get answered. Speed matters more than most businesses assume — a reply within an hour or two reads as attentive, while the same reply three days later reads as an afterthought, even if the content is identical.

💡 Screenshot your best public Q&A exchanges. A genuinely helpful public reply to a common question is reusable — turn your three or four best ones into an FAQ highlight, a Stories save, or a pinned comment, so the next person with the same question never has to ask at all.

Mistakes to avoid when you're routing questions

  • Sending a generic "check your DMs" with no public substance at all — it looks evasive, especially for a simple question everyone could see the answer to.
  • Forgetting to actually follow up in DMs after saying you would — a promised DM that never arrives is worse than answering publicly in the first place.
  • Copy-pasting the same canned line regardless of the question — it reads as a bot, not a business, if every single reply is identical.
  • Letting a public complaint sit while you privately negotiate a resolution — a short public "we're on it" holds the space until the private resolution is done.
  • Being inconsistent across team members — if one staff member answers pricing publicly and another always moves it to DMs, customers get mixed signals about what's normal.

Frequently asked questions

Isn't it safer to just move everything to DMs?

It feels safer, but it isn't free — every "DM us" reply to a simple question is a small piece of trust and momentum you're handing away, and some people simply won't bother messaging and will move on to a competitor who answered in the open. It depends on the question: genuinely safer for anything personal, but often a quiet cost for anything that was fine to answer in public.

What if I don't know the answer well enough to reply confidently in public?

Buy time publicly rather than guessing — "Great question, let me confirm the details and get back to you 🤍" — then follow up once you actually know. A confident wrong answer in public is far worse than an honest short delay.

Should pricing always be public or always private?

Neither, universally — a simple, standard price is worth stating publicly because it removes friction for everyone reading. A genuinely variable, quote-dependent price is better handled with a public range or "it depends on X, Y, Z — DM us for an exact quote" so you're not misleading anyone with a number that won't hold.

How fast do I actually need to reply?

Within a few hours on a good day, ideally under 24. Speed compounds — a fast public acknowledgment buys you room to take your time on the private detail without looking slow overall. 🌴


Keep reading 🤍

Share
Written by
Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦