Reddit can spot a template from across the room. Here is how to use them anyway.
Saved replies are essential for any brand support operation that handles more than 20 messages a week. They are also the thing that gets brand accounts publicly mocked on Reddit when used poorly.
Both can be true. The trick is using saved replies as a starting point for a real reply, not as the reply itself. The templates below are designed to be quickly customized in 15 to 30 seconds before sending. None should ever be sent verbatim. All should be modified to mention the specific user, the specific issue, and one specific detail that proves a human read the thread.
The 12 templates that work
1. Acknowledged bug, no fix yet
Thanks for the detailed report. We can reproduce this on our side. There is an open ticket tracking it: [ticket reference if you have one]. We will reply on this thread once it ships.
Why it works: confirms the bug is real, gives the user something to follow, sets a clear callback expectation.
2. Acknowledged bug, fix shipping soon
This is a known issue we are fixing in [version or rough timeline]. Sorry for the friction in the meantime. If you want to be notified when it ships, [link to changelog or signup].
3. Acknowledged bug, fix already shipped
This was fixed in [version], you should be on the newest version now. If you are still seeing it, can you reply with [specific debug info] and we will dig in.
4. User error, gently
The behavior you are seeing is actually how [feature] is intended to work, here is why: [one-sentence reason]. That said, the docs do not explain this well, we are going to fix that. Sorry for the confusion.
The “we are going to fix the docs” part is non-optional. If the user got confused, the docs failed.
5. Billing question, public
Happy to look at this. Could you DM us your account email and we will pull up the invoice. Posting payment details in a public thread is not a great idea.
6. Account-specific, redirect to DM
This needs us to look at your specific account. Could you message us directly so we are not asking you to share account info in public.
7. Outage acknowledgment
Yes, we are seeing this too. The team is on it. Status updates here: [status page]. We will reply on this thread once it is resolved.
The status page link is the difference between “we hear you” and “we have a plan.”
8. Feature request, no plans
Thanks for the suggestion. This one isn’t on our near-term roadmap, but the request is logged. The case for it would be stronger with [specific data or use case], if you have any.
9. Feature request, on the roadmap
Good news, this is something we are actively working on. The current target is [rough timeline]. We will post here when it ships.
10. Apology for late reply
Sorry for the slow reply on this. We are working through a backlog of unread messages. Is this still relevant, or has it resolved on your end?
The “still relevant” question is genuine. About 40% of late-reply threads are now stale. Closing them politely is fine.
11. Disagreeing with a user, respectfully
We see it differently. [Specific reason]. Happy to be wrong here. If you have data showing otherwise, share it and we will look.
12. Modmail to a moderator, partnership
Thanks for reaching out. We would love to coordinate on this. The right person on our side is [name and role]. Do you want to take this to email, or keep it in modmail?
Modmail is fine for ongoing coordination. Many mods prefer it because it stays visible to the whole mod team.
The three templates that look like they should work but don’t
Don’t: “Thanks for reaching out.”
Reddit tone hates this opener. It reads as corporate, dismissive, and templated even when it’s not. Cut it. Start with the response itself.
Don’t: “We appreciate your feedback and will pass this along to our team.”
Translation: nothing will happen. Reddit reads this as a brushoff because, almost always, it is one. If you actually mean it, say what specifically will be passed along, to whom, and when you will reply with an update.
Don’t: “We are sorry you are experiencing this issue.”
Two problems. First, it is the corporate-passive-voice cliche that every customer-service training course teaches and every Reddit user has learned to hate. Second, “experiencing this issue” is fancy talk for “it broke.” Just say “Sorry, that is broken on our end.”
How to use these without sounding like a robot
Five rules.
1. Add the user’s specific issue, by name, in your first sentence. “Thanks for the detailed report” becomes “Thanks for the detailed report on the dropdown bug in v3.1.” That single change is the difference between a templated reply and a real one.
2. Include one detail nobody could have written without reading the thread. “I see you mentioned this only happens after you toggle dark mode, that is a great clue.” This proves a human read.
3. Sign off as a brand, not a person. “Subportly Support” is fine. “Best, Sasha from Subportly Support” is also fine. What’s not fine is signing off as a person on a brand account, because the account is shared. People reading the thread will figure out it’s not Sasha replying every time. Stick to the brand voice.
4. Keep replies short. A 60-word reply that nails the issue beats a 300-word reply that buries the answer in apology language. Reddit rewards directness.
5. Reply to the actual question, not the question you wish they asked. This sounds obvious. It is the most violated rule on Reddit by brand accounts. If the user asked “why does this break,” answer why. Don’t pivot to a feature pitch.
Where to keep these
A shared doc, or a saved-replies feature in your inbox tool. The doc is fine if you are small. By the time you have three people on the team, you want a tool that lets you insert templates with two keystrokes, customize, and send. The friction of copy-pasting from a doc kills the discipline.
Subportly does this, but so do most modern support tools. The point is that the templates exist somewhere fast.
Subportly has saved replies built in, scoped per account and per brand, with autocomplete from your two-letter shortcut. So your team can use these templates the right way: as 15-second drafts, not as 300-word ghosts. See how it works.