Access · Data · Records · Boundaries · Human review
Before you automate an adult creator account, decide who can change it, which conversations stay manual and who handles a problem. A rushed reply, a misplaced screenshot or access you forgot to revoke can affect the creator long after the task is finished.
Unly gives you practical controls for this setup: team permissions by account, a manual account pause, fan inclusion and exclusion lists, and safety alerts to review. Configure these controls before enabling replies.
The five controls to set before automation
Use this grid with the creator and anyone helping on the account. Each row needs an owner and a clear answer before you start.
| Control | Decision to make | What to check |
|---|---|---|
| Access | Who can view, configure or manage each account? | Named team members, limited permissions and a way to remove access. |
| Data | Where can fan information go? | Approved tools and a clear reason for every copy or export. |
| Records | What will explain a disputed action? | The relevant message, alert, time and review decision. |
| Boundaries | What must never be sent, sold or promised? | Age concerns, consent, content rights, personal details and creator limits. |
| Human review | Who can pause the account and assess a problem? | A named reviewer who knows when to leave the conversation manual. |
Keep access under your control as the team grows
A person reviewing alerts does not automatically need to change the creator’s personality, media prices or automation settings. In Unly, assign team permissions by account and by area. Give each person the access their work requires, then review it when their role changes.
Keep the creator’s recovery email and account recovery methods under the creator’s control. Use unique passwords and enable two-step verification wherever the service offers it. The NCSC explains these account protections, including the use of a password manager.
When someone leaves, remove their team access and review any other access they held, including shared folders and connected tools. Follow the platform’s own instructions for ending sessions and changing credentials where needed. Review the account’s recovery and payout details yourself.
Set age, consent and content boundaries before sales rules
Read each platform’s current terms for account access, automation, content and fan interactions. Record the page and date you checked. Repeat this review when the platform changes its rules or you add a new workflow.
Ofcom’s UK guidance states that sites and apps allowing pornography need strong age checks from 25 July 2025. These are service-provider requirements; an AI reply is not an age verification process.
On 27 March 2025, Ofcom fined Fenix, the provider of OnlyFans, £1.05 million for inaccurate responses about its age assurance measures. On 27 May 2025, the European Commission announced investigations into four adult platforms over suspected DSA breaches involving the protection of minors. These dated actions show why age safeguards and accurate records belong in your operating process.
Write the creator’s boundaries as actions: do not share private contact details, promise a meeting or offer unapproved custom content. Stop sexual conversation when age is in doubt and use the platform’s official safety process. Keep identity checks in that process rather than collecting ID documents in DMs.
Consent also needs a clear response. If a fan asks you to stop sending offers, keep that conversation out of sales follow-ups. Before enabling a media item, confirm that you have permission to distribute everything shown in it and that its description matches the actual content.
Fan request
“Send me your personal number. I want to talk away from this platform.”
Approved reply
“I keep my personal contact details private. We can chat here.”
Review decision: keep the reply within the creator’s stated boundary. If the request becomes persistent or threatening, stop the automated exchange and have the named reviewer assess it.
Limit fan data sharing and keep decisions traceable
Map where account data goes: the platform, Unly, your team and any extra tool. For each destination, write what is shared, who can see it and why it is needed. Remove a destination if you cannot explain its purpose.
For a support question about one reply, use the relevant excerpt and time. Remove unrelated personal details from screenshots. Avoid copying entire conversations into personal chat groups, shared spreadsheets or another AI service just to discuss one issue.
Keep enough context to explain a decision without duplicating the whole inbox. Unly’s alert views show the fan, alert and timing information, with details of who requested a resume where available. Add a short decision note in your restricted team record: what happened, what you changed and who approved the next step.
Review the actual conversation in the platform’s native messaging. Compare the fan’s request with the reply and media that were sent. A sales total cannot explain whether a particular response respected the creator’s boundaries.
Configure the controls in Unly
Set the creator’s instructions
Fill in the personality settings accurately. Use Unly’s PDF instruction upload to document the creator’s voice, approved offers and conversation limits. Keep those instructions specific enough for a team member to apply too.
Choose the fans included in automation
In Security, use the whitelist to start with selected fans, or the exclusion list to keep particular conversations manual. Check the saved list before activating the account.
Prepare situations that need review
Use custom alerts to describe situations that require attention: “The fan keeps asking for the creator’s phone number after being told it is private.” Choose manual review rather than a timed expiry when the situation needs a human decision. Decide who watches those alerts.
Review safety alerts
Unly surfaces safety alerts including Suspected minor and Prohibited content. The account owner can request a resume after assessing the concern. Leave unresolved age or content concerns paused.
Check the media catalog
Review active media, descriptions, base prices and catalog price variation before allowing the agent to propose content. Remove anything the creator has not approved for sale.
For the setup behind these controls, see Unly’s OFM software. Use the reply and PPV pricing guide to make the approved offer clear.
Pause, review and decide whether to resume
Name a reviewer before the account runs unattended. The reviewer needs permission to manage account configuration to pause it, plus access to the context needed for review. The owner handles requests to resume safety alerts. Agree on who covers the review when someone is unavailable.
Pause
Use the account’s manual pause when the issue affects its automation. Check the conversation in native messaging to see what has already been sent.
Understand
Read the fan’s request, the reply and any media sent. Identify whether the issue concerns access, instructions, content or a safety boundary.
Decide
Correct the relevant setting, remove an unapproved item or keep the fan excluded. Record the decision and reviewer.
Check
For a paused alert, request a resume only after review. Check its status afterward and confirm what happens in the native conversation.
If you suspect an account compromise, follow the platform’s recovery process. Check the recovery email, change compromised passwords and end existing sessions using the service’s controls. The NCSC’s account recovery guide explains these steps. Restore access before considering whether automation should run again.
Check the setup before enabling it
Start with one account and selected fans so you can inspect the result. Keep a copy of the instructions used for that start and record any changes made during review.
- The creator controls recovery access; every team member has a defined role.
- You have reviewed the platform’s current rules for the intended workflow.
- The selected fan scope and active media match what you intend to automate.
- A reviewer knows where to find alerts and how to pause the account.
- You can explain an unexpected reply using the native conversation and relevant records.
- You have reviewed replies, media and boundary cases before expanding the scope.
Use the MYM account preparation guide for a platform-specific start, or the multi-account guide when assigning responsibilities across creators. Try Unly and apply this checklist to the first account you connect.