“How much?” is the start of a conversation
A customer sees a product in a post and asks for the price. The reply they receive may be read by everyone else considering the same product. That makes a comment more than a smaller version of a direct message: it helps one person while shaping what other visitors understand about your business.
Instagram comment automation works best when you decide what the public reply should accomplish and what belongs in a private conversation. Sometimes the customer only needs a price or a product detail. Sometimes they need help choosing. The useful next step depends on the question, not on a rule that every comment must become a sales pitch.
Answer the question where it was asked
If the answer is useful to other readers, consider keeping it public. Opening hours, available colours and what a service includes are often good examples. A clear answer saves the next visitor from asking exactly the same thing.
Here is an illustrative reply for a fixed-price product: “This one is [price] and comes in black or sand. Which colour are you considering?” Replace the placeholders with your actual information. If the price depends on options, explain what changes it: “The price depends on the size and finish. Which size are you looking at?” That gives the customer a reason to continue instead of leaving them with a bare “DM us.”
Give the customer a reason to move into DMs
A private conversation becomes useful when the answer depends on that person's order, preferences or circumstances. Explain what you will help them work out. “Message us with the desk size and your delivery area so we can confirm the options” is a more concrete invitation than “Check your inbox.”
Keep the first private question relevant to the original comment. If someone asked about a sofa, restarting with a long menu makes them do the work again. In your reply instructions, define the information needed for that type of enquiry and ask for the next missing detail. You can design that journey without assuming every public commenter is ready to buy or receive a stream of messages.
Handle buying questions, recommendations and complaints differently
Consider three fictional comments on a skincare shop's post. “What is the bottle size?” needs a factual answer from the product information. “Which cleanser should I choose?” needs a relevant question about the customer's preferences and the options you actually offer. “My order hasn't arrived” needs an order-support route, not a recommendation for another product.
Write examples for these different intentions before automating replies. Keep the complaint response calm and give a clear way to contact the right team privately. For recommendation requests, avoid asking for every possible detail at once. The first useful question is usually enough to keep the conversation moving. Treat a simple compliment as a compliment; it doesn't need a qualification form.
Give comment and message agents different jobs
In AnswerAct, you build separate agents for your customer messages and public comments, then assign them to your connected business pages. Add your product and service facts to each relevant agent, and tailor its instructions to the setting. A comment agent usually needs a concise public answer and an appropriate invitation to continue. A message agent can work through the details of a customer's enquiry over several turns.
Keep prices, delivery terms and available options consistent across both. A customer who hears one price under the post and a different price in a message has a new problem to solve. When you change a business rule, review the knowledge used by both roles rather than fixing only the reply you happened to notice first.
Test the handover as one customer journey
Read the post, write the comment and follow the next step using the same question. Does the public answer make sense next to the post? Is the invitation specific? When the customer continues privately, do they know what to send and what answer to expect?
Use an example for each common type of enquiry and one that doesn't fit neatly. Look for promises such as “We've sent you a message” when no message has actually been sent. Depending on the channel and configuration, a public reply and a private reply are different actions. Only describe an action as completed when it has happened. If the next step is for the customer to message you, say so plainly.
Review the questions that lead somewhere
A large number of replies tells you that replies were sent. It doesn't tell you whether customers found what they needed. Review whether people received a useful answer, continued with a relevant question, reached an appropriate order or booking step, or got their support issue to the right person.
Read comments that received no further response as well. Some were fully answered; others may have been discouraged by an unclear next step. You need the context to tell the difference. Keep a short list of recurring friction, such as unexplained price differences or repeated requests for the same detail, and improve those replies first.
Choose a plan and create your agent
Choose a product or service you plan to post about. List the questions it is likely to attract, write the public answers and decide which questions need a private conversation. Then build those roles in Answer Act. A useful comment reply should leave the customer better informed and make the next step easy to understand.