Auto Responses: What to Automate and What to Never Automate
A clear line between the messages worth automating on InnerText and the ones that must always come from you.
Every creator hits the same wall eventually. The inbox that felt manageable at forty fans feels impossible at four hundred, and the obvious fix is to automate your way out of it. That instinct is right, but only halfway. Automation is genuinely good at some things and genuinely destructive at others, and the difference is not about how busy you are. It is about what the fan is paying for in that specific message. Get the line right and you buy back hours a week without anyone noticing. Get it wrong and fans quietly work out they are talking to a machine, which is the one thing a text-first platform cannot survive. This guide gives you a decision rule you can apply to any message, then shows what that rule says about the tools you actually have.
1. The one question that decides everything
Before you automate anything, ask a single question about the message: is the fan paying for the information, or for the attention?
If the value is in the information, automate it. A link, a price, a time, a confirmation, a set of instructions. The fan wants that content fast and correct. They do not care whether a person typed it, and they would rather have it in five seconds than in five hours.
If the value is in the attention, never automate it. A reaction to something they told you. A reply to a question about you. A thank you after they spent money. In those messages the content is almost irrelevant; the point is that you noticed them specifically. An automated version is worse than no message at all, because it takes something that felt personal and proves it was not.
Almost every message sorts cleanly into one bucket or the other. When it does not, default to sending it yourself.
2. Automate the front door
The single highest-value thing to automate on InnerText is the very first exchange, before a fan is a fan.
When someone texts your number and they are not subscribed yet, your Text Me auto response fires and sends them a pre-written reply with your subscribe link. You set this up once at Dashboard → Settings → Text Me, and it runs from then on. You can turn it on or off, edit the message, and attach a piece of teaser media that goes out with it.
This is the purest case of information over attention. Someone just discovered you and needs a link. Nothing about that moment is improved by making them wait for you to be awake. It also keeps an unsubscribed number out of your inbox while it is still just a stranger with a phone.
Two things worth doing here:
- Write the message in your own voice rather than leaving the default. It is the first thing anyone hears from you.
- Attach the teaser media. It costs you nothing after the first setup and it turns a plain link into a preview of what they are subscribing to.
3. Automate the logistics you would otherwise forget
The second category is scheduling and admin, and InnerText handles much of it for you already.
When a fan books a call, reminder texts are queued automatically: one about twelve hours out if the booking is far enough ahead, and one fifteen minutes before the call starts. You do not configure these and you do not have to remember them. If the call is cancelled, the reminder is skipped rather than sent into the void.
The platform also handles the standard keyword replies on your number. If a fan texts STOP or HELP, the correct response goes out automatically and their status updates. That is not a feature you have to think about, and it is one of the quiet things that keeps your line in good standing with carriers.
The rule holds: nobody has ever felt less special because a call reminder was automatic.
4. What to never automate, and why
Here is the same rule applied to the messages creators are most tempted to hand off.
| Message type | Automate? | Why |
|---|---|---|
| First reply to a brand new number | Yes | Pure information: they need the link |
| Call reminders | Yes | Logistics, and it is already handled for you |
| STOP and HELP replies | Yes | Handled by the platform, do not touch |
| A reply to a personal question | Never | The whole value is that you answered |
| A thank you after a tip or unlock | Never | Automating gratitude cancels the gratitude |
| A reaction to something they shared | Never | This is the relationship, not the overhead |
| Re-engaging a fan who went quiet | Never | If it reads as a template, it confirms why they left |
The bottom half of that table is a practical position, not a moral one. Fans on a text platform are paying for access to a person. The moment a message reads like it could have been sent to anyone, the thing they are paying for stops being visible, and that shows up later as a cancelled subscription rather than a complaint.
5. The middle ground: saved replies
Most of the time savings creators want do not come from automation at all. They come from not retyping the same four sentences twenty times a day.
InnerText has saved replies for exactly this. You build a small library of messages you send often, then pull one into the composer from the toolbar or by typing / in an empty message box and filtering by name. The reply drops into your draft. It is never sent on its own: you always see it, you always edit it, you always press send.
That last part is what makes it safe. A saved reply is a starting point, not an answer. Insert, change two words so it fits this fan, send.
Good candidates for your library:
- Your standard explanation of how a call booking works
- Your usual answer to "what do you charge for X"
- A short re-engagement opener you always personalise before sending
- The line you use to explain that a link expires
"Hey , that link is just for you so it won't work if it gets shared. Want me to send a fresh one?"
Notice the shape: a saved skeleton with a fan-specific detail dropped in. It saves ninety percent of the typing and keeps a hundred percent of the personal touch.
6. Broadcast is not automation
Mass messages sit in their own category and it is worth being precise about it, because creators often lump the two together.
A mass message is something you write today and send today, to a group you chose. You can target a tag, exclude a tag, and use {{first_name}} so each fan sees their own nickname instead of a generic greeting. It is one deliberate act of writing that reaches many people, which is a different thing from a rule that fires without you.
That matters because it changes how you should think about frequency. An auto response can run for months without going stale. A broadcast goes stale immediately, because it was written for a moment. If you find yourself sending the same broadcast every month, that message belongs in your saved replies instead, sent one to one when it is actually relevant.
7. A one-hour setup that lasts
If you want to do this properly in a single sitting:
- Write and enable your Text Me auto response, in your voice, with teaser media attached.
- Build four or five saved replies from the questions you answered most often last week.
- Tag your fans so your broadcasts can be targeted instead of blanket.
- Write down, for yourself, one line: automate the link, never the feeling.
That is the whole system. It is not sophisticated, and it does not need to be.
The point
Automation on a messaging platform should be invisible, not impressive. Every automated message you send should be one that a fan would be mildly surprised to learn you had typed by hand, because it was only ever logistics. Everything else, the parts they will remember and the parts they are actually paying for, stays yours.
Ready to get started?
Start monetizing