How to reply to 200 "dam koto?" comments on one post

Updated 2026-07-26 · 6 min read

The post did well. 200 comments. About 190 of them are the same two words.

"dam koto?"

You start at the top. By comment forty your thumb hurts and you are copy-pasting. By comment ninety you are replying "inbox koren" because it is shorter. The last sixty never get answered at all, and the post is already off everyone's feed.

That is a full working day, and at the end of it the thread looks exactly like it did at the start: a wall of unanswered questions.

"Inbox koren" answers one person and hides the answer

The theory behind hiding the price is that a comment becomes a conversation, and a conversation becomes a sale.

What actually happens is that you convert one public question into one private question. The person who was already interested now has to do more work. The forty people reading the post behind them learn nothing — so they ask the same question, and you answer it again.

A public price is written once and read a hundred times. A private one is typed a hundred times and read once.

Put the number in the reply and the arithmetic inverts. "1,450 taka. Dhaka'r vitore delivery 60 tk, baire 120 tk." Everyone who scrolls past that comment is answered without you touching the keyboard. The comment count drops, because the question has been answered where the question was asked.

And the people who do message you after seeing it have already accepted the price. Your inbox stops being a queue of price checks and becomes a queue of orders — a different job, and a much shorter one. This is also why reply speed decides the sale: fewer messages means the ones you get are answered inside ten minutes instead of two hours.

Write the comment for the next reader, not the commenter

The person who asked is not your only audience. They may not even be your best one — plenty of the people who buy never comment at all. So the reply should be a small, complete answer that a stranger can act on:

1. The price, as a number.
2. The delivery charge, both inside and outside Dhaka, because the reader does not know which applies to them.
3. One line of next step — "order korte inbox e message diben" or a size question.

Three lines. Under one comment. Pin it, so it sits at the top of the thread instead of sinking under the next hundred.

The reader who was going to ask "dam koto?" now has no reason to. The reader who was going to ask "delivery koto?" also has no reason to. What is left in your comment section are the real questions — "size 40 ache?", "washing e color jabe?" — which are worth your time because they are close to an order.

What Meta actually lets a page do with a comment

The private reply is more limited than people assume. You get one message. If the customer does not answer it, that thread is over — Messenger only lets you keep talking to someone who has replied to you. So that single message has to carry everything: price, delivery, and a question that makes replying the easy option.

Which is the strongest argument for the public price. A customer who reads it and opens the inbox themselves starts a normal conversation, with no one-message limit on it.

Does a wall of identical comments hurt your reach?

Honest answer: nobody outside Meta can tell you the weight a comment carries, and anyone who quotes you a number is guessing.

What is safe to say is that comments count as engagement, so a post with 200 of them is not being punished for having them. The cost is not algorithmic. The cost is that you spent a day typing, and the thread you produced does not answer anything for the next person who finds the post.

Which makes "hide the price to farm comments" a bad trade even in its own terms. You are buying distribution you cannot measure with hours you definitely spent.

Tanet Chat does not answer comments

Worth stating plainly, because the tooling in this category often implies otherwise.

Tanet Chat reads only inbox events. When you connect a page it subscribes to Meta's message webhooks — new messages, read receipts, delivery receipts — and not to the feed one that carries comments. Comment activity is never delivered to it at all. There is no comment reply, public or private, and no auto-DM to commenters.

It starts at the message. The customer reads your public price, taps through to the inbox, types "eta ki stock e ache?" at 11:40pm — and gets a real answer with the price, the delivery charge and a question back, in Banglish, in seconds. It handles a photo instead of a product name, and it captures the order as fields you define — name, phone, address, plus any row you add — instead of leaving it scattered across a thread. What it cannot do is stand in the comment section for you. See what the agent handles for the current list.

What to do with this week's post

• Put the price in the post itself. Caption, first line. Not "inbox koren".
• Write one three-line comment reply — price, delivery inside and outside Dhaka, next step — and pin it under the post before the comments start.
• Answer the first ten comments individually with that same text, so the thread reads as answered rather than ignored. After that, most people have stopped asking.
• Use your one private reply only on the comments that show real intent — a size, a colour, "kivabe order korbo". Spending it on a generic "dam koto?" burns your single shot on someone the pinned comment already answered.
• Leave the specific questions public. "Size 40 ache" answered in the open is a sales page for the next reader.

None of this needs a tool. It needs the price to be visible before somebody has to ask for it. If you want the inbox side covered too, access is invite-only right now — there is no self-serve signup, and the application form requires three things: your business name, your name, and an email.