OnlyFans agency SOP: the processes you should document

What a usable SOP looks like

A standard operating procedure is only useful if someone opens it in the middle of a shift and finds the answer in under a minute. Long documents written once and never read again are the most common failure. Before you write the library, agree on a format that every SOP follows, so people know where to look and what each part means.

Write for the person doing the task, not for an auditor. Use the words your team already uses, number the steps and put the rule first and the reason after. When a step depends on judgment, say who decides and how to escalate instead of trying to describe every possible case.

• Purpose in one sentence: what this SOP protects and when it applies.
• Owner: the one person who keeps it accurate and answers questions about it.
• Checklist of steps in the order they happen, each starting with a verb.
• Limits and escalation: what nobody may do, and who to call when unsure.
• Version and review date, so outdated rules are easy to spot.
• Length: one page where possible; link to detail instead of pasting it in.

Creator onboarding and the creator guide

Two documents sit at the start of every creator relationship. The onboarding SOP is what the agency does in the first days, and the creator guide is what chatters read before they ever write as that creator. Both depend on information only the creator can give, so collect it in one structured interview rather than in scattered messages.

The creator guide is usually the most used document in an agency. Keep one per creator, update it whenever the creator changes a preference, and treat their limits as fixed rules that a chatter can never negotiate away with a fan, however much money is on the table.

• Onboarding: signed contract, confirmed account holder, how the account is linked without sharing the password, and who gets which access.
• Onboarding: content inventory, posting plan, current prices, size of the fan base and any known problem fans.
• Onboarding: first review date and what the creator will receive in reports.
• Creator guide: voice and tone with three or four real example messages, emoji habits and words the creator never uses.
• Creator guide: hard limits (topics, content types and requests that are always refused) and soft limits that need approval.
• Creator guide: price bands per content type, what each includes, and who may approve exceptions.
• Creator guide: facts chatters may mention (time zone, availability for customs) and what must always stay private.

Daily inbox, handover and PPV pricing

These SOPs run every day, so they should be the shortest. The daily inbox routine and the shift handover each have their own guide on this site, so here we only list what the SOP must contain. The goal is that any chatter on any shift works the inbox in the same order and leaves it in a state the next person can pick up without guessing.

PPV pricing deserves its own SOP because it is where money, fan trust and the creator's rules meet. Write down who sets prices, how far a chatter can go without asking, and what never happens, such as pressuring a fan who has said no or describing content that does not exist.

• Inbox routine: order of work (unread, open conversations, paying fans, new subscribers), response time targets, and when to use a template versus a fresh reply.
• Inbox routine: read the fan note before replying and update it whenever something new is learned.
• Handover: open conversations, promises made, pending PPVs and anything to escalate, written in a fixed format in a fixed place.
• PPV: price bands per content type, the maximum discount a chatter may give, and who approves anything outside the bands.
• PPV: describe content accurately, never send content the creator has not approved, and respect a fan's no.
• PPV: how to record what was sent and bought so the same content is not sold twice to the same fan.

Difficult fans, refunds and chargebacks

Every agency meets rude fans, fans who push past limits and fans who say they paid for something they never received. Without an SOP, each chatter improvises, and improvising under pressure is where rule breaks and unhappy creators come from. Decide in advance what a chatter handles alone and what goes straight to a lead.

Refunds are a special case because payments run through OnlyFans, not through the agency or the creator. Chatters should never promise a refund, compensation outside the platform or payment by another route. Their job is to stay calm, record what happened and pass it on. OnlyFans' terms and acceptable use policy are the reference for what is allowed.

• Difficult fans: a short ladder from polite redirect to firm boundary to restricting or blocking, with who may take each step.
• Abusive fans: no arguing, note or screenshot the messages, escalate to a lead, and block or report when the creator's rules say so.
• Stop and escalate at once: any sign a fan may be a minor, threats, requests to meet, or requests to pay outside the platform.
• Refund requests: a neutral reply template, how to check what was actually sent, where the case is logged and who decides on any goodwill gesture inside the platform.
• Chargebacks: how they are noticed, how the creator is told, and how the fan note is updated so future sales to that fan are handled carefully.

Chatter onboarding and offboarding

People join and leave agencies often, and both moments carry risk. A new chatter who starts without training writes in the wrong voice and breaks limits; a chatter who leaves with access still active is a security problem. A checklist for each moment turns them into routine tasks instead of emergencies. Our guide on hiring chatters covers the selection side.

Offboarding should happen the same day, every time, whatever the reason for leaving. Removing access is simple when each person has their own login and no password was ever shared, which is one more reason to set up account access properly from the very first creator.

• Onboarding: signed confidentiality and conduct agreement, a personal login, and access to one account only at first.
• Onboarding: read the SOP library and the creator guide, then shadow a shift before replying alone.
• Onboarding: a first week with a lead reviewing conversations and a clear point at which access widens.
• Offboarding: remove access to every account and shared tool, and reassign open conversations.
• Offboarding: check the last handover notes they left and record the date in the team file.

Weekly reporting and incident response

The weekly report is how the creator sees the agency's work, and the incident SOP is how the agency behaves on its worst day. Both are better decided in calm conditions. Keep the report format stable so trends are visible from week to week, and keep the incident SOP short enough to follow under stress.

Incidents are rare, which is exactly why people forget what to do. Name one incident owner, write the first five actions and rehearse them once. Never try to work around a restriction or a review by OnlyFans: follow the platform's process and contact its support through the account holder.

• Weekly report: subscribers and active fans, messages and response times by shift, earnings by source from the creator's statements, what worked and what changes next week.
• Weekly report: who prepares it, when it is sent, and who checks it before it reaches the creator.
• Account flagged or restricted: pause risky activity, read the notice carefully, inform the creator, review recent messages and posts against the rules, and let the account holder contact OnlyFans support.
• Content leak: collect links and evidence, inform the creator, file takedown requests through the proper channels, and check whether anyone's access needs review.
• After any incident: a short written review and an update to the SOP that should have prevented it.

Where to keep SOPs and how FansTracker fits

Keep the library in one shared place that everyone can reach in two clicks: a shared drive folder, a wiki or one pinned document per creator. Avoid copies spread across chat groups, because people follow whichever version they saw last. Store sensitive material, such as contracts and personal data, separately with restricted access.

Part of the knowledge works better inside the tool where chatters actually reply. In FansTracker, a desktop app for OnlyFans agencies that is not affiliated with OnlyFans, internal fan notes are shared by the team and never sent to OnlyFans, and saved templates hold approved replies, so the creator guide shows up in daily work. Team roles with per-account assignment and separate read and reply permissions enforce who does what. A banned words filter and an activity log are in development, so for now limits are enforced through training and lead review.

How to train on SOPs so they stick

Reading a document once does not change behavior. Train inside real work: a new chatter shadows a shift with the inbox SOP open, then works a shift with a lead reviewing. Short quizzes built on real situations, such as a fan asking for a discount or a refund, show quickly whether the rules have landed.

Make updates easy and visible. When a mistake happens, ask which SOP should have prevented it and fix that page the same week. Announce changes in one place, note the new version and review date, and hold a recurring review, for example every quarter, where each owner confirms their pages are still true.

Step by step

1. List your processes. Write down every recurring task and every risky moment, from creator onboarding to incidents, and group them into one library.
2. Prioritize by risk. Start with the creator guide, PPV approval, difficult fans and offboarding, where mistakes cost the most.
3. Write one page each. Use a fixed format: purpose, owner, checklist, limits and escalation, version and review date.
4. Test on a real shift. Have a chatter follow the SOP during a shift and rewrite every step that was unclear.
5. Store and train. Keep the library in one shared place and train new staff through shadowing and reviewed shifts.
6. Review regularly. Owners confirm their pages every quarter and after every incident.