Lesson 7 of 87 min read
Inbox and community: reply fast, reply well
Treat comments, mentions and DMs as sales and support. Set response times, write saved replies, and turn good answers into posts.
In this lesson you will
- Set response-time targets and an owner for every network
- Write a small set of saved replies that still sound human
- Turn repeated questions into public posts and docs
- Know when to move a conversation out of public and into the product
For a SaaS company, the replies under your posts are often worth more than the posts. A prospect who asks "does this work with our setup?" under a LinkedIn post is closer to a trial than anyone who just liked it. A customer who complains in a public thread is telling everyone reading how you handle problems. And every answered question is a small, public piece of documentation.
Yet replies are where small teams fall behind first. Comments sit for three days, a DM gets lost between two people who each thought the other would answer, and a frustrated customer's mention never gets seen. This lesson gives the inbox an owner, a response time, a short set of saved replies and a habit of turning answers into posts.
Give the inbox an owner and a clock
An inbox that everyone checks is an inbox nobody owns. Name one owner per week, rotating if you have more than one person. The owner does not have to answer everything; they make sure everything gets answered.
Then set response-time targets. These are starting points for a small team, during working hours:
| Type | Target | Why |
|---|---|---|
| Complaint or bug report in public | Within 2 hours | Everyone reading is watching how you respond |
| Question from a prospect | Same day | They are choosing right now, possibly between you and someone else |
| DM from a customer | Same day | It is support, wherever it arrived |
| Question from a customer in public | Same day | Others have the same question |
| Praise or general comment | Within 2 days | A thank-you is enough |
| Spam, trolling | Never | Hide, report or ignore |
Write your targets down where the team can see them, including what happens outside working hours. "We reply within one working day" on your profile sets an expectation you can keep.
How to reply well
Speed is half of it. The other half is the reply itself. Rules we follow:
- Answer the actual question. Read the whole comment first. Many bad replies answer a question that was not asked.
- Lead with the answer, then the detail. "Yes, it does. Here's how:" beats three sentences of thanks before the answer.
- Thank people for bug reports and complaints, specifically. "Thanks for the screenshot, that made it easy to find" is better than "Thanks for your feedback".
- Never argue in public. If someone is wrong about your product, correct the fact once, politely, with a link. If they are angry, acknowledge it and offer to fix it.
- Move private details out of public. Account specifics, billing, anything with personal data: offer to continue in DMs or through your support form.
- Close the loop. When a reported bug is fixed, reply in the original thread. It is one of the most convincing posts you will ever write, and it costs one sentence.
Saved replies that still sound human
Saved replies save time, but replies that read like templates do damage. Write a small set, five to eight, as starting points the owner edits every time.
Bug report, first reply:
"Thanks for flagging this, and for the detail. We're looking into it now
and will reply here when we know more."
Bug fixed:
"This is fixed now. Thanks again for reporting it; it made the fix much
quicker."
Feature request:
"Thanks, that's a good one. It's not on the product today. We've added it
to our list; if you want to follow it, [where you track requests]."
Question we've answered in the docs:
"Yes. Here's the short version: [one or two sentences]. Full steps here:
[docs link]."
Moving to private:
"Happy to look at this with you. It involves account details, so could
you send us a message through [support form or DM]? We'll pick it up there."
Rule: if the owner sends a saved reply without changing at least one word to fit the person, it is probably the wrong reply.
Turn answers into posts
Every question you answer more than twice is a post waiting to be written. Keep a "repeated questions" list in the inbox owner's notes. Once a week, take the top question and turn it into:
- a public post in your how-to pillar (lesson 3)
- a docs page or FAQ entry, if there is not one already
- a saved reply that links to both
This loop is what makes support into marketing. The questions your customers ask are the questions your prospects have, too.
When to move a conversation into the product
Some conversations should not stay on social at all:
- A customer with an account problem belongs in your support channel, where you can see their account. Offer the move publicly so others see it was handled.
- A prospect who wants to try something specific belongs in a trial or a docs page that shows it. Give them the shortest path: one link, tagged.
- A conversation that turns into a long technical thread belongs in your community space (Discord, Slack or a forum), where it can be found later.
Do not try to close sales in DMs that nobody asked for. Offering help is fine; a cold pitch after someone liked a post is not.
Your own community space
Many SaaS teams run a Discord server or a Slack community next to their public accounts. It can be the best place to learn what customers actually do with your product, or a quiet room with a welcome message and nothing else. The difference is mostly how you run it.
What works for a small team:
- Few channels. Start with three: announcements, help, and general. Add a channel only when a topic keeps crowding another one out.
- The team shows up. A community where only members talk to each other is rare at small scale. Someone from the team should answer in help every working day, inside the same response-time targets as everywhere else.
- Announcements are short and invite replies. Your community has already chosen you; it does not need the marketing version. Say what changed, link the changelog, ask one question.
- Good answers leave the room. A great answer in help is invisible to everyone outside the server. Turn it into a public post or a docs entry using the loop above.
- Clear rules, enforced kindly. Post the rules once, pin them, and apply them the same way to everyone.
If you cannot staff a community space every working day, do not open one yet. An empty server with unanswered questions is worse than no server, because it tells the people who joined that nobody is listening.
Worked example: one repeated question, three outputs
Here is how we run the loop on one question about our own product: whether a coding agent can draft and schedule posts for you. The answer is in our AI agents page, so it qualifies for the loop.
The reply in the thread, on X:
Yes. Connect your coding agent to our MCP server and ask it to draft a
week of posts. It works through your workspace, and nothing publishes until
you approve it. Setup steps: [link]
The public post it became, for LinkedIn, in our how-to pillar:
"Can my coding agent post to social for me?"
It can draft and schedule. Publishing is a different question.
Our rule is that nothing goes out without a human approving it, whether
the draft came from you, a teammate or an agent. Agents are good at
first drafts and at filling a calendar. They are not the ones who should
decide what your company says in public.
How to connect one: [link]
And the saved reply that links both, for the next time someone asks. In our Discord, the same question gets a short answer and a pointer to the setup page, plus an invitation to post their setup if they get stuck.
Notice the LinkedIn post adds an opinion (humans approve, agents draft), which is what makes it worth reading for people who never asked the question.
A 15-minute daily inbox routine
- 5 minutes: complaints and bug reports first, then prospect questions.
- 7 minutes: customer questions and DMs; move private ones to support.
- 3 minutes: praise and general comments; add any repeated question to the list.
Once a week: turn the top repeated question into a post, a docs entry and a saved reply.
Recap
- Name one inbox owner per week and write down response-time targets the team can keep.
- Lead with the answer, thank specifically, never argue in public, and close the loop when something is fixed.
- Keep five to eight saved replies, and edit every one before sending.
- Turn any question answered twice into a post, a docs entry and a saved reply.
- Move account problems to support, specific trials to a tagged link, and long technical threads to your community.
Exercise
Write your reply kit
- Go through your notifications on each network for the last two weeks and list every unanswered comment, mention and DM. Answer the urgent ones first.
- Write your response-time table using the one above, adjusted to your team's hours.
- Write five saved replies: bug report, bug fixed, feature request, docs question and moving to private.
- Pick the question you were asked most often and answer it as a public post. Turn it into a short X thread with the X thread maker, or format a longer version with the LinkedIn post formatter.
- Write the name of this week's inbox owner at the top of the table.
Done looks like: no unanswered urgent items, a response-time table with an owner, five saved replies, and one post drafted from a repeated question.
Go further
Unified inbox
In FoPost, comments, replies and mentions from your connected accounts land in one inbox, where you can reply with an AI draft in your brand voice, snooze what can wait and resolve what is done. Add your docs and saved answers in knowledge so reply drafts quote them instead of guessing. See the unified inbox for which networks it covers.
Check yourself
1Why should a public complaint get the fastest response of all?Show answer
Everyone reading the thread is watching how you handle it, so it affects every prospect who sees it, not only the person complaining.
2What should you do with a question you have answered more than twice?Show answer
Turn it into a public post, a docs or FAQ entry, and a saved reply that links to both.
3When should a conversation move out of public replies?Show answer
When it involves account details or personal data, when it is a specific trial request better served by a link, or when it becomes a long technical thread that belongs in your community.
Keep reading, free
Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.