Playbooks · 5 min read

Community Building Is Mostly Answering the First Comment

The PostEngage teamEngineering and support ·
Building an automation: the trigger, the condition and the reply.

Somebody comments on your reel for the first time. It is not a clever comment. "Kitne ka hai?" or "where is this from" or just a fire emoji and a question mark.

Whether that person ever comments again is decided in the next few hours, and it is decided by one thing: did anybody answer.

That is not a growth theory. It is what it feels like to be them. Everybody knows the experience of writing something under a big account and watching it disappear into three hundred other comments, and everybody knows the small surprise of getting a reply from somewhere you did not expect one. The second one changes your relationship to the account. The first one teaches you not to bother.

Running the community you already have — triage, moderation, the upset person, and which of those jobs software can honestly take — is a different post. This one is about building: what makes a stranger become a regular, and where automation sits on that path.

The ladder, and which rung software touches

Rung one: they comment once. This is content work. Nothing in any tool produces this.

Rung two: they comment again. The rung this whole post is about. What produces it is an answer to the first one.

Rung three: they are recognisable. You know the handle. They turn up under most posts. They have opinions about your packaging.

Rung four: they answer other people. Somebody asks about sizing in your comments and a customer replies before you do. This is the actual thing people mean by community, and it is rare enough that you will remember the first time.

Automation touches rung two. Only rung two. It gets people answered who would otherwise have been ignored, which is the bottleneck on almost every account under a certain size, and then its usefulness drops off sharply.

The comment-to-DM flow, from a keyword typed under a post through to a private reply arriving in the inbox.
A public reply under the comment and a private one in the inbox. The public half is the part that does community work, because other people read it.

The public reply is doing more work than the DM

Most writing about comment automation treats the public reply as a receipt — "check your DMs" — and puts all the effort into the private one.

For community building it is the other way round. The DM is read by one person. The public reply is read by everybody who scrolls the comments, and what it tells them is whether this is an account that answers. Somebody who was never going to comment sees eleven questions with eleven replies underneath and files that away.

Which is also why forty identical public replies are worse than none. A column of "DM sent! 💌" repeating down the page looks like exactly what it is. Vary the templates, keep them short, and read your own comment section top to bottom occasionally as a stranger would.

The private reply answers a person. The public reply tells the room what kind of account this is. They are not the same job and they should not be the same sentence.

Where automation makes a community worse

Three ways, and all three are quiet.

Greeting a regular like a stranger. Somebody on rung three gets "Hi! Thanks for your interest 😊" for the ninth time. Nothing broke, nobody complained, and a person who was becoming a regular now knows they are talking to a machine. The Advanced setting for first-time senders only exists partly for this, and on a frequently posting account it is worth turning on before you think you need it.

Answering the comment that deserved you. The negative keyword list is usually built from words that mean do not sell to this person — not interested, complaint, refund. The category people miss is the opposite one: the messages that say your work mattered. Those look identical to a keyword matcher, and automating them is a quiet way to delete the best part of the week. Put them on the negative list and answer them yourself, late, whenever you get to them.

Sounding like a different person every time. A community forms around a voice. If half your replies are yours and half are generated in a register you did not choose, the account reads as inconsistent long before anybody consciously notices why.

The voice profile screen, built from replies the account owner previously wrote by hand.
The profile is grounded in messages you actually sent, which is the only reason a generated reply can sound like the account rather than like a tone setting.

What "AI-powered" honestly means on this

It means one thing: when somebody writes something no template anticipated, a reply can be composed in your register instead of being ignored or answered with the wrong template. One credit, one reply. Templated replies are free and unlimited, so on most accounts the model is a minority of the volume and should be.

It does not mean the software knows who anybody is. There is no member profile, no relationship history, no sentiment tracking, no social listening, no follower analytics, no growth feature. It replies to what somebody typed. That is the entire mechanism, and stretching the description of it is how tools end up promising community and delivering an autoresponder.

What to actually do this month

Answer every comment on your next three posts. All of them, including the emoji ones, including the ones with nothing to say. Automate the repetitive question so you have the time to do the rest by hand.

Then look at who came back. It will be a handful of people and it will be more than came back last month. Learn those handles, and reply to them as a person for as long as it is possible to.

Nothing in this scales, which is the honest ending. The scaling part is answering the repetitive question, and the community part is what you do with the hours that frees up. If the underlying question is whether software changes what the job is, that is a different argument, and if you were sent here by a promise about engagement numbers going up, read this first — the effect is real, it is human, and it is slower than the headline suggests.

One email when we publish.

No drip sequence, no “quick question” follow-up. Unsubscribe is one click and we honour it immediately.

Try it on your own posts

Free forever. Three minutes to set up.

Start free