Time, context, consistency
Start automating when DMs crowd out content creation, leave interested fans waiting and make previous offers hard to track. Those are the same three problems whether you run one account or manage creators for an agency.
Unly lets you set clear rules for repeat conversations: choose the fans the AI handles, set its tone and availability, and prepare media and prices. Follow the account statistics in Unly and reread the messages on your creator platform. You keep the decisions about your content, boundaries and sensitive conversations.
Look for three signals in your daily work
Count the work around each reply: reopening threads, checking a purchase, finding the right media and remembering what you promised. A busy inbox becomes difficult when you have to rebuild that context every time.
| Signal | What to check | What it tells you |
|---|---|---|
| DMs take over your schedule | Time replying, looking up context and finding content across the whole day. | If this displaces filming, posting or reviewing your account, the workload needs a limit. |
| Interested fans wait | Threads where someone asks a clear question about content, then receives no answer within your intended reply window. | Your reply routine no longer matches the conversations coming in. |
| Offers lose their context | Can you find what was offered, what was bought and what still needs a reply? | If you rely on memory, each new conversation adds more work to recover later. |
For this guide, use more than 45 minutes a day as a prompt to review your workflow, especially when the other two signals also appear. Your available time still matters: a dedicated chatter and a part-time creator have different schedules.
Few messages, clear records and reliable reply windows? Keep answering manually. Repeated context loss, late replies and squeezed content time? Start a limited automation test.
Audit one week before changing the workflow
Record each DM session for a week. Split the time into replying, finding context and finding media. Include short phone checks between other tasks; they still interrupt your work.
A simple workload calculation: 20 minutes replying + 15 minutes recovering context + 10 minutes finding media = 45 minutes of inbox work. If the biggest part is searching, organize your records and media before expanding automated replies.
- Separate requests: greetings, questions about available content, purchase questions, custom requests and conversations to stop.
- Record pending commitments: fan, request, promised action and next step. Use a note or worksheet you can actually maintain.
- Identify repeat work: mark questions you can answer from a prepared rule or an existing media description. Record the time spent on the fans you plan to include in the first test, so you can compare the same group later.
- Check your reply windows: find where the backlog starts and which fans are waiting for a useful answer.
Match the automation to the work you found
Keep manual replies
Use this when the volume fits your available time. Set reply windows and keep a record of custom orders and promises. A saved answer can help with repeat questions, provided you read the thread before sending it.
Automate a fixed event message
Use this when the repeated task is a welcome or renewal message. MYM documents subscription-related scenarios; Fansly documents triggers such as subscriptions and tips, with delay and cooldown settings.
Handle repeat conversations in Unly
Use this when fans reply with different questions about your existing content. Configure the agent's voice, fan selection and response timing, then prepare the media it can offer and their catalogue prices.
The event-message options are described in MYM's automatic-message guide and Fansly's automated-message guide. Check any messages already active on your platform so your new workflow does not repeat the same welcome or offer.
For Unly's account workflows, see the MYM AI chatbot or OnlyFans AI chatbot guide.
Start with a small, reviewable setup in Unly
Open Configure for your connected account. Give the first test one job: handle repeat questions about prepared content for a group you can review. Leave fans with unusual requests or unresolved commitments outside that group. A selected fan can still ask for a custom later, so include this rule in your instructions: “Do not confirm a custom order, price or delivery date.”
Prepare the content and prices
In Media, choose content you are ready to sell and check its Internal description and Price. A fan asking for a short video should lead to content that actually matches the request.
Write usable tone instructions
Fill in Personality, then use Advanced options → Instructions from PDF to import prepared instructions. Specify greeting style, message length, vocabulary and boundaries, with examples of replies you would send. Replace “sound natural” with a rule you can check, such as “answer the question in two short sentences before offering content.”
Select the fans
In Fan selection → Monitoring type, choose Talk only to fans in the list (whitelist) and add the fans for your test. Keep custom orders, disputes and conversations requiring personal judgment outside it. The blacklist is available when you want to exclude particular fans from a wider scope.
Set availability and pacing
In Behavior → AI availability, choose continuous operation or specific hours, then set the response delay. Leave individual follow-ups off for the first test if you want to review replies on their own. Add them later with a clear purpose.
Review and adjust
Read the conversations on your creator platform early in the test. Check tone, context, media and prices. If you see repeated mistakes, pause the account in Unly, correct the relevant instruction or media setup and review again before expanding.
Use the guide to AI replies and PPV pricing to prepare the tone and content rules. For this first test, change one part of the setup at a time so you can understand the effect.
Handle custom requests and exceptions yourself
A question about available media is a good repeat task. A custom request with a deadline needs a decision about what you can create and deliver. That distinction should be written into your operating rules.
Fan: “Do you have a short video from that outfit set?”
Reply pattern: “Yes, there is a short video from that set. Would you like the details?”
Repeat task: answer from the prepared catalogue. Use this wording only when the matching video exists and its description and price are ready.
Fan: “Can you make a custom video and have it ready tomorrow?”
Human reply pattern: “I'll check the request and my schedule before confirming a price or delivery date.”
Human decision: review the request, boundaries and workload. Keep this conversation outside the automated scope while deciding; do not let a reply turn an unconfirmed request into a promise.
Give a named person responsibility for custom requests, complaints and sensitive negotiations. For important buyers, review the context personally before changing the offer or timing. If a selected fan asks for a custom during the test, remove them from the whitelist or pause the account's agent while you handle it. The fan list defines who is included; you still need to spot and act on a change in the conversation.
The guide to keeping your voice when automating helps you turn those boundaries into concrete instructions.
Check whether the workflow removes more work than it adds
Compare the same fans and types of request over equivalent periods. Use the time recorded for the test group during your audit, then include time configuring the agent, reviewing replies and correcting them. Check the rest of the inbox separately to see whether work has shifted to other fans.
- Time: compare manual replying and searching with the time now spent reviewing and correcting.
- Context: check whether you can find offers, purchases and pending commitments without rebuilding the thread.
- Quality: record replies that miss the question, use the wrong tone or require a human correction.
- Sales: review the account's sales statistics alongside the actual conversations. Keep the period, prices and fan group comparable when assessing a change.
A higher sales total during a busier week does not show that automation caused the increase. First confirm that interested fans get useful answers and the review workload stays manageable. Then expand the fan group or add a new repeat task.
Make the switch when the cost of lost context and delayed replies is visible. Start in Unly with prepared media, clear instructions and chosen fans. Use the creator dashboard guide to keep the next review focused.