Autopilot

Autopilot is how automation actually runs. Reply modes decide what is permitted; Autopilot decides what is happening.

With Autopilot off, nothing automatic happens — no message is sent, and no draft is written by itself. The Generate button always works, whatever Autopilot is doing.

---

Before you engage

Autopilot writes to real people. Three things should be true first:

1. Your creator’s persona has been tuned against real conversations.
2. Your team has worked on Draft only long enough that drafts rarely need editing.
3. You have decided which fans are eligible, and set their reply mode accordingly.

See Reply Modes and Autonomy.

---

Engaging it

Autopilot is engaged in one place: the Autopilot tab of the side panel.

1. Open the platform tab you want it to work in.
2. Open the side panel → Autopilot.
3. Under The autopilot works on, switch on the groups of fan it should handle. Each switch carries the number of fans in that group; one showing 0 fans, or greyed out, has nothing to work on.
4. Under Where it works, choose Lock on one fan — the open fan’s name is in the option itself, after a dash — or All fans in the list. Opening the first gives you that fan’s reply mode.
5. Only answer messages from — the freshness window, in its own band. It governs the sweep only; a lock ignores it, and the panel says so when a lock is chosen.
6. Click Start, in the top row beside the state.

If no fan is set up yet, both switches read 0 fans. Set a fan’s reply mode on the Fan tab, or the creator’s default from their name at the top of the panel — it opens their dashboard page.

It begins immediately, and only from that moment. Nothing is retroactive.

While engaged, the toolbar icon shows AP, so it is visible at a glance from anywhere in the browser.

---

Which fans it works on

Two large switches decide which fans this session handles. They do not change anybody’s reply mode — they say which groups the autopilot takes on right now.

Switch	Effect
Draft only	It writes the reply and leaves it for you to send
Draft and send	It writes the reply and sends it without waiting for you

Each row leads with how many of this creator’s fans are in that group, counted from the CRM — that is the “who am I about to affect” answer, so it is the biggest thing in the row. Below the two switches, one sentence says what the combination will do, and one more says how many fans are on Manual and will never be touched.

Switching on only the second one is a real and useful choice: leave my hand-written fans alone, and handle the automatic ones.

A switch is greyed out with one line of explanation when your manager has turned that group off for this creator, or when no fan is in that group yet.

---

Where it works

Lock on one fan

Open the fan, set the reply mode you want on them — the control sits inside this option, so you do not have to go looking for it — and engage. Autopilot works with that fan and nobody else.

The lock is on the person, not on the window. You can read any other conversation meanwhile and nothing will happen in it. When you come back, the panel is where you left it.

The fan’s chat has to be open for a reply to actually go out — a message can only be typed into an open conversation. So if you move away, Autopilot waits and says so; when their chat is on screen again, it carries on. It does not switch itself off, and moving around costs nothing.

This is where every agency should start. Your chatter sees every message go out, in real time, and can stop instantly.

All fans in the list

Autopilot works through the conversation list, serving everyone who is waiting: open a conversation, review it, reply, move on. Each fan is handled according to their own reply mode, and fans in a group you did not switch on are passed over.

This takes over the browser tab. Conversations are opened by clicking them, so your team cannot work in that tab while it runs. Use a separate window or a dedicated browser profile.

Before engaging, this option tells you how many conversations are in reach, how many are unread, and how long a full pass will take at the sending pace — so you can plan the session rather than wonder whether it has stalled. It also says plainly that these lists load as you scroll: the sweep reaches the conversations the platform has actually drawn, so on a very long list, scroll it in first.

Availability. The sweep works on OnlyFans and Fanvue. On Fansly, lock on a fan.

---

The freshness window

The most important setting for the sweep.

It has its own band — Only answer messages from — under Where it works. It governs the sweep and nothing else: a lock ignores it entirely, and the panel says so under the choices while a lock is selected. For the sweep, it limits how far back Autopilot will reach:

Window	Behaviour
6 hours	Only today’s active conversations. The most conservative choice
24 hours	The default, and the right answer for most agencies
3 days	Weekend catch-up
No limit	Every unanswered conversation, however old

Choose deliberately. On an established account with history, No limit means every conversation ever left unanswered receives a reply — potentially hundreds at once. The panel warns you before you select it.

The window applies to All fans only. A fan you locked onto is always served: you chose them by hand, which is a stronger signal than any timestamp.

---

The one trigger rule

Autopilot acts on exactly one condition:

The last message in the conversation is from the fan.

That is all. It is the same thing as “a new message arrived” and “your creator has not replied yet”, and having one rule rather than three is what makes its behaviour predictable.

---

What you see while it runs

The Autopilot tab is a live console. The top of it turns green and stays that way for as long as it is working, so the answer to “is this sending on my behalf right now” is the first thing on the screen:

• Who it is serving now, and what it is doing — opening the conversation, reviewing, writing, waiting. When it is locked on a fan whose chat is not on screen, it says whose chat it is waiting for.
• Progress through the current pass.
• Counters for this session: sent, drafted, skipped, failed. They reset each time you engage, so the numbers always describe the current session.
• The activity log opens by itself when it engages — while it runs, what has gone out is the thing worth watching.
• What it is running with, in a line under the top row.
• Stop — in the top row, where Start was.

If you lock onto a fan the session will never touch — because they are manual, or because their group is switched off — the panel says so instead of sitting there looking busy.

During a full sweep, the Draft tab clears its working surface and shows “Autopilot is driving this tab”. This is deliberate: conversations are opening every few seconds, and manual buttons would act on whichever one opens next.

---

The emergency stop and the stop-gates

• The emergency stop — it stops all automatic sending for that creator, whatever else is switched on and whoever is working. It is in Creator Studio, and in the extension popup — deliberately not on this tab, where it would read as stopping the tab. A chatter who needs their own browser stopped presses Stop in the top row, which ends it there immediately.
• A reply is held back when… — the four situations that hold a message for a person: the fan may be in crisis, the fan is complaining, the fan pushes a banned topic, and it is the middle of the creator’s night. They are folded away with a count (“4 of 4 on”) and open on a click. Managers change them here; everybody can see them, because they decide whether a reply goes out.
• The pace — at most 20 messages an hour, fixed. Stated with the stop-gates.

---

The activity log

Every message is recorded: who it went to, what was sent, when — and the reason for every conversation that was opened and then passed over.

Fans the sweep skips without opening them at all, because their reply mode is not one of the groups you switched on, are counted rather than listed. On a roster where most fans are manual, a line each would fill the log and push the actual sends off the end of it. The numbers are in the counters, and the breakdown of who is on which mode is on the two group switches above.

The log is folded away with its count while Autopilot is off, and opens by itself when you engage.

Read it daily for the first two weeks. A sweep is not something anyone watches in real time; the log is what makes it reviewable, and it is where you will learn which conversations should not have been eligible.

---

Pacing

Autopilot works at a human pace, by design:

• A short randomised pause before each message, shown as a live countdown with a Cancel button.
• A minimum gap between messages.
• A strict hourly ceiling — 20 messages per hour.

This is not a technical constraint; it is how the feature is meant to work. An account that answers forty conversations in ninety seconds does not look like a person, and looking like a person is the point.

---

When Autopilot stops

Autopilot ends cleanly and tells you why. It stops when:

Event	Reason shown
You click Stop	Switched off
The tab it was working in is closed	The tab it was working in was closed
The page is reloaded	The page was reloaded — engage again when ready
You change the creator you are acting as	You changed the acting creator
The browser restarts	Nothing runs through a restart
Several attempts fail in a row	It switched itself off — check the log
Your monthly draft allowance runs low	Drafts are nearly used up

Moving to another conversation does not stop it. A session is locked to a person, so where you browse is not its concern.

Autopilot never survives a restart, a reload or a closed tab. This is a deliberate design decision: automation that appears to be running when nobody is executing it is the most dangerous state this feature could present. It is always re-engaged consciously.

Your switches, scope and freshness settings are remembered, so re-engaging is one click. The fan lock is not — that belongs to one session.

---

Safeguards

Beyond the per-message checks described in Reply Modes and Autonomy, Autopilot adds its own:

• Both group switches start off, and a manager has to unlock automatic sending before it can be switched on at all. A fresh installation does nothing.
• Conversations with no reply from your creator anywhere are skipped. Either it is a brand-new fan who deserves a person, or something is not being read correctly. Skipping costs one manual reply; not skipping costs an incident.
• The same messages are never answered twice. Engaging over a conversation a draft was already made for does not produce a second reply.
• Every message re-confirms the fan immediately before sending. If the conversation on screen has changed, the send stops.
• Repeated failures disengage it automatically, rather than continuing at volume.
• Your draft quota is protected. Autopilot stands down before the monthly allowance is exhausted, leaving drafts available for the ones your team asks for by hand. The Generate button is never blocked.

---

Recommended operating procedure

Phase 1 — supervised, drafts only, one fan. Lock onto one fan with only Draft only switched on. Nothing is sent; your chatter reads what the model writes.

Phase 2 — supervised sending, one fan. Same lock, with Draft and send switched on. Your chatter watches every message go out. Several shifts of this.

Phase 3 — review. Read the log end to end. Every skip reason should make sense to you. Every sent message should be one you would have approved.

Phase 4 — sweep, in a dedicated window. Engage All fans in the list with a 6- or 24-hour window, in a separate window so your team keeps working. Check the log at the end of each pass.

Do not run phase 2 and phase 4 together at first. If something is not right, you want to know whether it is Autopilot or the persona — and running both at once makes that impossible to tell.

---

Governance for agency owners

• Autopilot is engaged per chatter, per tab. It is not an account-wide setting someone can leave on by accident.
• What a chatter is allowed to engage is a manager’s setting, per creator, in Creator Studio.
• Every automatic send is logged with fan, text, time and outcome.
• Conversations where automation stopped and a human is needed appear in the dashboard’s Needs attention panel.
• The creator-level pause switch overrides everything, instantly.