Features › Chatting

Chat with the whole roster behind you

Your team gets the tools it expects from a chat CRM, from a merged inbox to a content vault. Segments build themselves. You also get campaigns and a scheduler for planned drops.

For your team, the difference is the panel to the right of each thread. Every line in it shows where it came from. A send that shouldn’t go out gets caught before it does.

Book a demoSee the Shift Console

The inbox across every creator, with the open chat on the right and each fan’s spend beside their name.
One merged inbox covers every creator a chatter is assigned. Each thread is locked to its own account, and a reply can’t land in the wrong creator’s chat.

The panel beside each thread

When a chatter opens a conversation, this panel opens with it. Each computed field says which records it came from. Team notes and tags sit next to them, labeled as notes.

f–8821Top 2% of the roster
Spent with this creator$310.00
Spent across your roster$547.00
Last purchase9 days ago
Median reply time4m 20s
This vault itembought, $22
Suggested price$30.00
Top 2% of the rosterGraded on what he has spent across every creator you run. On this creator alone, he’s her 41st biggest spender. He wouldn’t make a follow-up list there. Across the roster, he’s in the top 2%.reconciled transactions
Last purchase, 9 days agoTaken from the transaction record. It tells you he has stopped buying, even if he still chats. A fan who stops buying needs a different reply from one who stops typing.ledger
Median reply time, 4m 20sWorked out from message timestamps. The sync records when messages happened and how many there were. What fans write is never stored. What your team sends is kept for 30 days for audit and then deleted. This panel reads neither of them when it works out reply time.timestamps only
This vault item: bought, $22Each item keeps a send history for every fan. He was sent this exact set in March at $22, and he bought it. Before it goes to him again, the composer warns the chatter. Resending a set a fan already owns is a common mistake in this job.vault history
Suggested price, $30.00This comes from the creator’s own price ladder, and 571 sends sit behind it. The composer shows that sample size too. If a suggestion rests on only four purchases, the chatter sees that before acting on it.derived · n=571

Illustrative figures from a demo workspace with made-up creators and fans. The IDs here are placeholders. In the product, staff see each fan by their OnlyFans @handle. That handle is also what lets us honor a request to erase a fan’s data. Your team writes the notes and tags on a fan, and only your agency can see them. They’re deleted when the fan asks to be erased.

Six tools your team uses all day

One inbox, every assigned creatorThreads from all of a chatter’s creators, newest first. In the inbox, each thread is locked to its account. A badge at the top shows which creator you’re replying as at all times.inbox
A composer that already knows the fanThe fan panel sits beside the thread. Next to it, a vault picker shows what this fan has already been sent and if they bought it.composer
Segments that build themselvesLists build from the ledger, for example big spenders who stopped buying or trials ending within 48 hours. Other lists cover first-time buyers and renewals at risk. One more shows the fans waiting longest for a reply. Someone on your team can open each list and work through it.segments
Campaigns with limits built inSet a different price per segment and exclude fans you want left out. Mass messages go out one at a time, at least 10 minutes apart. Each creator can send up to 24 a day.campaigns
Triggers that don’t watch anyoneWin-backs, spend milestones, lapsed VIPs and trial-day nudges run from synced data on your schedule. When a trigger fires, it sends from a template a person on your team wrote. Nothing waits for a fan to come online, because the product has no presence detection.triggers
Every send on the recordSchedule drops your team wrote, and watch what’s going out in the outbox. The audit log ties every send to a named person and their shift, and no send goes out unnamed.outbox

What this fan has already been sent

Each vault item keeps its own send history for every fan. It shows the price of each send and if the fan bought it. That stops a chatter from selling a fan a set they already own.

Vault item Sent Bought Converts Best price To this fan
Set 214 604 96 15.9% $22 already bought
Set 188 571 71 12.4% $30 never sent
Set 233 233 19 8.2% $45 never sent
Set 241 41 3 thin thin never sent

The fourth row is marked thin and gets no best price. At three purchases, the sample is too small to set a price. The same cutoff applies here as on the price ladder. Each item is indexed by folder and tag along with its history and price evidence. The vault stores links to your content. We don’t store your media. Pictures pass through our server on the way to your screen, and small ones are kept in memory for up to 30 minutes so chats load fast. Nothing is saved to disk.

Team sales and automation sales

Sales from automated sends are credited to Automation as their own actor. That splits the month in two. One part is what your team earned, and the other came from automation.

Credited to people$41,365These sales followed a message a named person wrote and sent on a shift covering that creator. Your team’s commission comes from this figure each month.
Credited to Automation$4,818Sales that followed a triggered send. They’re credited to Automation, and nobody earns commission on them. That’s 10.4% of the month.

The rule leans one way by design. Fans often open a triggered offer the next time they pick up their phone. So the rule looks back two days before it decides a person closed the sale. It can only move a sale away from a person and never toward one.

If you switch automation crediting off, triggered sales go to whoever was on shift. Leave it on to keep those sales out of your team’s commission.

AI never sends to your fans, and no setting changes that.

AI reply help is off by default. When the owner switches it on, it can suggest a draft. Fan identifiers are stripped before anything is processed, and each draft is marked with how it was made. A person writes every message that leaves an account, and AI never sends.

The rule is built into the product. No toggle can switch it off at 2am, and no plan lets you pay to skip it. Automated triggers only send from templates that a person on your team wrote first.

How the panel is made

Segments and the fan panel are built from matched transactions. What fans write is never stored, and nothing here is worked out from it. Reply time comes from timestamps alone.

Price evidence shows its sample size everywhere it appears. That includes the composer at the moment of sending.

Each sale is credited to the shift covering that creator when the money lands. The rule is published on the Shift Console page. Full rules on the methodology page.

Limits of the chat tools

  • AI never sends. It can suggest a draft when switched on, and a person still writes every message.
  • It won’t make a slow team fast. A merged inbox ends tab-switching and wrong-account sends. How well someone writes still depends on that person and their practice.
  • It doesn’t host your content. It keeps links to your files along with tags and send history, and we don’t store your media.
  • It won’t outrun your sending limits. If the limits mean a campaign takes three days to clear, it takes three days. Nobody can override the limits, and that includes our own team at FanOptik.
  • Segments describe what fans have done. They never guess at who a fan is. Notes and tags stay inside your agency and are deleted if the fan asks to be erased.
  • It can’t tell you why a fan stopped buying. It can tell you he stopped nine days ago and what he bought before that. Your chatter decides what to say from there.

What chatting connects to

The Shift ConsoleWhere each sale from a send gets credited to a named person under a rule set in advance.Open
Roster analyticsWhere the suggested price and spend tiers in the fan panel are worked out.Open
SecurityHow sending limits and screening are enforced. Quiet hours use the agency’s time zone.Read
How fan data is handledWhat we store and how reply time works without storing what fans write.Read

See it on your own roster

Book a 20-minute demo or start free on your own accounts. No card needed. See how your month splits between team sales and automation, and move to a paid plan when you are ready.

Book a demoAll features

FanOptik

Chat, analytics and payroll for OnlyFans agencies and creators. Every number shows where it came from.

© 2026 FanOptik. All rights reserved. · Free to start. No card needed.