Installing the Extension

The extension is where your chatters spend their day. It puts the CRM, the fan’s history and the AI draft in a panel beside the conversation, so nothing requires a second screen.

Requirements

Google Chrome, or another Chrome-based browser (Edge, Brave, Arc).
A computer. The panel is a desktop browser extension — see below.
A Sufflera account with the Generate drafts permission — every role that works conversations has it by default.

Phones and tablets

Chatting is desktop work. The extension needs a Chrome-based browser on a computer — Windows, macOS or Linux. Chrome on Android and Safari on iOS do not support extensions at all, so there is no version of the panel that can run there, and no setting that will make one appear.

The dashboard is a different matter. app.sufflera.com works on a phone browser, and the layout is built for it: fan records, conversation history, analytics, billing, team settings and the reply mode of any fan can all be read and changed from a phone. A manager can run the account from a phone perfectly well.

So the split is:

On a phone	Only on a computer
Reading and editing fan records	Generating a draft
Conversation history and past drafts	Inserting or sending a reply
Analytics and billing	The autopilot
Team, roles and permissions	Importing conversation history
Changing a fan’s reply mode	Quick replies and the media vault in the panel

If you open a creator’s platform inbox on a phone, nothing breaks — the extension simply is not there, and you are working the way you would have before you installed it.

Supported platforms

The panel works on OnlyFans, Fanvue and Fansly. Everything a chatter does in a conversation is available on all three; the one difference is the sweep that works through every conversation at once.

	OnlyFans	Fanvue	Fansly
Fan recognition and CRM matching	✓	✓	✓
Live conversation sync	✓	✓	✓
AI draft generation	✓	✓	✓
Insert and send from the panel	✓	✓	✓
Conversation history import	✓	✓	✓
Autopilot — current conversation	✓	✓	✓
Autopilot — sweep all conversations	✓	✓	—

Installation

Sufflera is deployed to your agency as a managed package: your whole team runs one build, from one folder, and new versions go out on your schedule rather than Chrome’s. Installing it takes about two minutes per machine.

Unzip the package somewhere permanent on the machine — a folder such as C:\Sufflera or ~/Applications/Sufflera, not Downloads. Chrome loads the extension from this folder every time it starts, so keep it where it is.
Open chrome://extensions and turn on Developer mode (top right). This is the setting that lets Chrome run a package you control rather than one from a public catalogue.
Click Load unpacked and select the folder you unzipped.
Pin it to your toolbar. Click the puzzle-piece icon in Chrome’s toolbar and click the pin beside Sufflera. The icon carries live status, so keeping it visible matters.
Click the Sufflera icon and sign in with your email address and password — the same login you use for the dashboard.

chrome://extensions with Developer mode switched on, and the Load unpacked button it reveals

Agency tip. Use the same folder path on every machine in your team. It makes rolling out an update a single instruction everyone can follow.

Updates

New versions are distributed the same way, so you decide when a shift changes build. Rolling one out takes under a minute per machine.

Replace the contents of your Sufflera folder with the new files.
Open chrome://extensions and click the refresh arrow on the Sufflera card.
Reload any platform tabs you had open — a tab that was already open keeps running the previous version until you do.

Your login, your selected creator and your settings all survive an update.

Your permissions travel with you. If your role only allows you to work with three creators, only those three appear here.

Choosing the creator you are acting as

From the extension icon, select the creator you are currently working as.

This one setting determines whose voice every draft is written in, which fans you see, and which quick replies are available. Chatters who cover several creators should get into the habit of switching this first, before opening the inbox.

The current creator is always displayed at the top of the side panel, so it is never ambiguous whose account you are working in.

Opening the panel

Once installed, open your creator’s inbox on OnlyFans, Fansly or Fanvue and open any conversation.

Open the workspace with the Open the panel button in the extension popup.

The panel docks beside the page and stays open as you click through conversations. It follows whichever conversation is on screen, so you never have to re-select anything.

Clicking the toolbar icon gives you account-level controls:

The creator you are acting as, at the top. Their name is the switch — click it and pick from the list.
Their reply mode and your remaining draft quota, on the line under the name.
Pause auto-send — the emergency stop for this creator, beside the mode. It appears only when that creator is set to a mode that can send on its own; on Manual there is nothing to pause. The same switch is in Creator Studio.
Open the panel — the one action here, and the way into the workspace.
Active fan — the conversation open in this tab, if there is one, with a link to that fan in the CRM.
Sign out, the small icon in the top corner.

The extension popup: who you are acting as, drafts left, and the way into the panel

Everything you do inside a conversation happens in the side panel, not here.

The icon reports what is happening even when the panel is closed:

Icon state	Meaning
A number	Drafts ready that you have not looked at
A countdown	A message is about to be sent automatically — open the panel to cancel
AP	Autopilot is engaged in a tab

Team rollout checklist

For managers deploying to a team:

Confirm every chatter has an account and a role, and that their creators are assigned.
Have each chatter install, sign in, and pin the icon.
Walk one live conversation together, end to end: open, generate, edit, send.
Confirm the sent message appears in the fan’s history — this is the check that proves the loop is closed.
Agree your tagging conventions and purchase-logging rules before shift one.
Leave every creator on Manual for the first week, and leave Autopilot off. Automation is a decision to take with evidence, not on install day. See Reply Modes and Autonomy.

Next steps

Learn the workspace: The Side Panel
Start writing: Writing Replies