Three tools under one name
Search for an OnlyFans chatbot and you get three different things. An auto-reply sends lines it was given when something happens. A drafting tool writes a message and waits for a person to approve it. An autonomous AI chatter reads the chat, decides what to do, and does it.
The difference that matters is who decides each message. With the first, a script does. With the second, a person does. With the third, the software does, so its limits have to be built in rather than left to whoever is on shift.
Auto-replies and scripted chatbots
A scripted bot fires a set line on a trigger: a new subscriber, a keyword, a time of day. Its strength is that you know exactly what it will say. That suits a welcome message, a menu of what the page sells, or a mass message at a set hour.
Its limits show in a real conversation. A typical one reads the last line, not the chat, and cannot see what he bought last week, so it offers it again. Every fan gets the same opener. And it cannot decide to say nothing, so a fan who just said he is broke still gets the next push in the script.
Drafting tools a person approves
A drafting tool writes the next message, and a chatter reads it, edits it and presses send. Every word has a person behind it. That suits a creator who wants to see everything before it goes out, or a team teaching new chatters what a good reply looks like.
The cost is time. The fan waits until someone gets to the draft, nothing goes out when nobody is on shift, and the page answers only as many fans as there are people approving.
Autonomous AI chatters
An autonomous AI chatter makes the call and carries it out, on the pages that were switched on, with no approval queue. Fans get answered at any hour, and each chat runs on its own history and timing, so a busy page does not turn into one long line.
Because nobody approves each message, the limits live in the software: what it may sell, at what price, how often it may follow up, and how a person takes over. It also has to read when to back off: a fan who said no, one who is out of money, one who wants something only a person can give.
Fan Auto is this third kind, an independent product not affiliated with OnlyFans. Its job is to decide and send, not to draft for someone else.
How Fan Auto turns a decision into an action
Every decision ends as one of three actions: send a message, wait, or stop and hand the chat to a person. A request only a person can fill is a message plus a ticket for your team, so the chat keeps going while someone picks it up. Whatever the model writes is only a proposal. Before anything leaves, the proposal is checked: the item must be in her inventory, the price inside its range, and the chat must not be one a person has taken over.
A proposal that breaks a rule is not sent and not quietly fixed. It goes back once with the reason. If the second try breaks a rule too, Fan Auto waits for the fan’s next message instead, and both tries stay on the record. A wait is an action too: when his message or the set time arrives, it reads the chat again and decides again. It never sends a line saved from earlier.
Every decision is logged with the conversation as Fan Auto saw it at the time, and each one comes from a published, versioned release of the Decision Brain, so you can always tell which version ran on a page.
What to ask any vendor
Whatever you are looking at, these questions sort the three kinds quickly:
- Does it send on its own, or does a person approve each message?
- What does it read before it writes: the last line, or the chat, what he bought and what the creator approved?
- Can it choose to send nothing, and what brings it back?
- What stops it from selling content that does not exist, or at a price the page does not allow?
- Does it check what a fan already received before offering him something?
- How are follow-ups spaced and capped?
- When a fan asks for something only a person can do, where does it go, and does the bot keep talking?
- How do you stop it for one fan or one page, and how fast does that take effect?
- Is every decision logged, and can you tell which version made it?