Context first. A short reminder. A clear stopping point.
Follow up when you can point to a real reason in the conversation. Remind the fan what they asked about, give them an easy next step and stop after a refusal or repeated silence. In Unly, you can configure automatic follow-ups, choose their delay, limit them to known buyers and add examples to guide the tone.
For a creator or agency, the hard part is deciding which paused conversations deserve another message. A fan who asked about a specific set needs a different response from someone who has already said no. Use the same decision process on OnlyFans, MYM or Fansly; adapt the sending controls to the platform and tools you use.
Read the last exchange: send, wait or stop?
Open the conversation in the platform’s native inbox before writing a reminder. Find the request, the last answer and any time the fan mentioned. An unopened message, an online status or a previous purchase does not tell you whether another offer is welcome.
| What you see | Next action | What the message should do |
|---|---|---|
| They asked about a set, then paused. | Send one contextual reminder after giving them time. | Refer to that set and offer a simple choice. |
| They said they would come back after work. | Wait for that window. | Pick up their request when the timing makes sense. |
| They said the offer was not for them. | Stop that offer. | Acknowledge the answer without another pitch. |
| Your previous reminder also got no reply. | Stop the sequence. | Leave room for them to return. |
| A new set matches something they explicitly requested. | Check that the interest still applies. | Explain what is new and why it relates to their request. |
| They asked you to stop messaging. | Stop and update your exclusions. | Remove them from the relevant sending workflows. |
A previous purchase can help you understand their preferences. It is not permission to keep pitching the same offer. If price was the issue, read how to qualify a PPV request before changing the price rather than sending another discount.
Choose the timing from the conversation
A pause during an active exchange and a fan saying I’ll look tomorrow
need different handling. For the first, a short reminder may fit. For the second, wait until tomorrow. A configured delay cannot replace that decision.
Use one contextual reminder as your starting rule. If it gets no answer, stop that sequence. Any later outreach needs a fresh reason, such as the content they requested becoming available, and must still respect what they last told you.
- Why this fan?
Name the request or preference you are following up on. If you cannot find one, do not send.
- Why now?
Check their stated availability and the messages they have already received. Do not add a reminder on top of a recent broadcast.
- Why this offer?
Confirm the content answers their request and has not already been bought. If it does not fit, change the action.
- Where does it stop?
Stop the offer after a refusal, discomfort or unanswered reminder. Make that rule clear to anyone handling the account.
Write a message that makes the next step easy
Keep the reminder shorter than the original offer. Use one real detail and one easy question. Skip guilt, invented urgency and claims that the content was made for that fan unless it actually was.
An unfinished choice
Have you got photos from the blue outfit shoot?
Yes, I have a photo set and a video from that shoot. Which are you after?
Were you after the photos from the blue outfit shoot? Happy to leave it if you’ve changed your mind.
The detail comes from their request. The question resolves the unfinished choice. If they do not reply, do not send another reminder about that set.
A time they gave you
I’m at work. I’ll have a look tonight.
Did you still want the details of that set? No rush if tonight doesn’t work.
Wait for the time they mentioned. Sending this a few minutes after their work message would ignore the context.
A clear refusal
No thanks, I’m not interested in that set.
Got it, I’ll leave that one.
Do not follow with a discount or another reminder for the same set. If they want to keep chatting, respond to the topic they choose.
Configure Unly around that method
Open the account’s configuration and go to Behavior. Unly provides an Automatic follow-up switch, Known buyers only, a Follow-up delay and custom follow-up examples. Start by deciding the audience and timing, then write the examples.
- Choose whether to enable it. Keep automatic follow-up off if your conversations usually need next-day handling. The available delays are 2, 5, 10, 15, 20 and 30 minutes.
- Narrow the audience. Enable Known buyers only to restrict follow-ups to fans Unly already identifies as paid-media buyers. Review the current exchange even for a returning buyer.
- Guide the tone. Prepare at least five short examples, as the interface recommends. Refer to unfinished requests and let the fan decline. Use different situations to define your voice; follow-up examples are not a fixed sending sequence.
- Open Fan selection. In that separate tab, use a whitelist to handle only selected fans, or a blacklist to exclude listed fans from agent conversations. Apply exclusions when someone asks you to stop.
- Save and review. Read the resulting conversations in the platform’s native inbox. If the timing or approach is wrong, disable automatic follow-up while you adjust it.
Keep the stopping rule in your review process. A follow-up delay sets timing; it does not define how many reminders your team should allow. For tone and offer settings, continue with customizing AI replies and PPV pricing. The MYM AI chatbot guide covers the wider Unly workflow.
Check every source of outgoing messages
A fan can receive a broadcast, a welcome message and a conversational follow-up from separate workflows. Review them together before adding another message. For an agency, assign one person to check the account’s outgoing schedule so each operator sees the same plan.
Fansly’s mass-message documentation describes audience filters, included and excluded lists, individual exclusions and scheduling. Use those platform controls to select who receives a broadcast; keep a broad announcement separate from a reminder about one fan’s request.
Fansly also documents delays and cooldowns for its event-triggered automated messages. These are Fansly controls. Review them alongside Unly’s settings and your manual sends, because changing one workflow does not configure the others.
Before a welcome-message sequence, read what a welcome message should do. Before a broadcast, read when mass PPV messages are useful.
Measure replies and refusals before sending more
Keep a simple manual review log: why you followed up, when you sent, whether the fan replied, whether they declined and whether a purchase followed. Record each step separately. A reply may mean a conversation reopened; it does not mean the fan wanted to buy.
The fan replies about the request
Answer that request. Check whether the reminder gave them enough context to continue.
The reminder gets no answer
Stop that sequence. Review relevance and timing before trying the same approach with other fans.
The fan refuses or asks you to stop
Close the offer or exclude them from the relevant messages. Do not count an annoyed reply as success.
To compare two approaches, use the same type of conversation over comparable periods. Calculate reply rate as fans who replied divided by fans who received a follow-up. Count each fan once and allow the same time for a reply in both groups. Compare refusals alongside it. Change one thing at a time: audience, delay or wording. The creator KPI guide explains how to connect those observations to sales decisions.
Start with one account in Unly. Set the audience, delay and examples, then review what is actually sent. Try Unly and use this decision grid as your team’s follow-up checklist.