OnlyFans Auto Messages: How to Set Up Welcome and Online Messages

Set up an OnlyFans welcome message or a message for fans who come online. This guide takes you from choosing recipients and writing the message to saving a draft, reviewing it and launching. When a fan replies, your team can continue the conversation.

Choose where to start:

• Set up your first welcome message.
• Set up a message for online fans.
• Troubleshoot missing or late messages.

Welcome and online messages were the most common automations in the agency setups we reviewed. All values shown are teaching examples; individual client configurations are not published.

Choose the right message type

Open Automation → Mass Messages, select a model and click New Message.

AgencyKey supports one-off priority campaigns and automated messages triggered by events. An event is something a fan does, such as subscribing. The system checks your conditions before sending a message.

A priority campaign runs once. An automation stays active and responds to new events. For each automation, choose whether it should message a fan only once or allow repeat sends. A chain can contain one message or several messages sent in order.

A PPV (pay-per-view) message contains content that a fan pays to unlock. The PPV purchase trigger is available, but it was rarely used in the agency setups we reviewed. If the purchase happens during a conversation, your team can respond in that chat: thank the fan, ask a question or discuss other content. A separate automation is useful when you want a prepared response to the purchase.

Set up an OnlyFans welcome message

Agencies commonly use a free welcome message with a short question. For your first draft, prepare one such message. Before launching, agree with your team on who will handle replies and show them the greeting.

Turn off other welcome messages

Choose the recipients

Create a Subscriber welcome automation. To greet every new fan, select All new subscribers.

For a welcome message aimed at a particular group, choose Only fans in selected lists and select the relevant list. Additional conditions and exclusions also apply when you choose All new subscribers, so check that they do not filter out people you intend to welcome.

Set the delay and frequency

Set Sending frequency for each fan to Once per fan. For this teaching example, choose After a delay under First message after the event and enter 2–5 minutes. The system chooses a random delay within that range for each new subscriber.

Once per fan applies to this automation. It does not prevent other campaigns from messaging the same person.

You can change the delay or send immediately after the event. Choose timing that gives your team a chance to respond when the fan writes back.

Write the greeting

Write one free message with a single question, using the audience's language and the model's usual tone. For example:

Hi! Glad you are here. What would you like to know about me?

Save and check your first draft

For this first draft, one message is enough. Check the model, text and delay. Then review recipients and exclusions: decide who should receive the greeting and which chats or groups to skip. Make sure additional conditions do not filter out fans you intend to welcome.

Click Save draft. The editor closes and the campaign appears in the table. It cannot send messages until you launch it separately.

To open it again, choose More actions → Edit campaign. Before launching, review the audience and exclusions and follow the review and launch checklist. Make sure your team is ready to respond.

You can add a follow-up later if you need one.

Set up a message for fans who come online

Choose Fan comes online. Someone may come online several times a day, so limit repeat sends and check recipients and recent chat exclusions before launching. These settings help keep another invitation from arriving during a conversation with your team.

Choose when to send

You can send without an added delay or choose After a delay. New online automations have no added delay by default.

The Also include fans who are online at activation switch lets you contact fans who are already online when you launch the automation. If it is off, the automation waits for new online events.

With this switch on, the option for sending without an added wait is called Without a delay. With it off, the option is called Immediately after the event. Neither setting adds a waiting period. Delivery still depends on the sending queue and sending speed.

Before sending the first message, the system checks that the fan is still online. If the fan has gone offline, the message may be skipped.

Limit repeat sends

Choose Once per fan to message each fan only once within this campaign. To allow repeat messages, choose Every matching event and set a pause before the same fan can receive another chain.

This teaching example uses 12 hours. If the first message was successfully sent at 10:00, this automation cannot start another chain for that fan before 22:00. Reaching the end of the pause does not send a message by itself: a new matching event is required.

The repeat limit applies within one campaign. If a model has several online automations, each runs independently. Check that the same fan will not receive similar messages from several campaigns.

Click Save draft, then follow the review and launch steps.

How the timing settings differ

The initial delay, the pause between messages and the repeat limit work independently. Here is where to find each setting:

• First message after the event / First message for each fan sets the delay before the first message. The label changes with the send settings. The welcome example uses 2–5 minutes after subscription.
• After previous: sets the pause before the next message in the same chain. The example uses 2 minutes.
• Pause before messaging the same fan again → Cooldown (hours) sets the minimum interval before a new chain can start for that fan. The example uses 12 hours after the first message of the previous chain.
• Exclude recent chats → Activity period sets how far back the system checks for chat activity. The example skips fans your team has chatted with in the past hour.

Welcome: first message and follow-up

Suppose a fan subscribes at 10:00 and the system chooses a 3-minute delay from the configured range of 2–5 minutes. In this example, the first message is successfully sent at 10:03. With a 2-minute pause, the follow-up can be sent after 10:05, only if the fan has not replied and the other conditions are met. A reply at 10:04 cancels the remaining messages.

Online: when a repeat becomes possible

In a separate online automation, the first message is successfully sent at 10:00 and the cooldown is 12 hours. This campaign cannot start another chain for that fan before 22:00. After 22:00, a new matching event and the other conditions are still required. Reaching the end of the cooldown sends nothing by itself.

Activity period looks back: for example, it checks chat activity during the past hour. It does not add an hour to the sending delay.

Choose your audience and protect active conversations

Use Send To to set recipients and exclusions.

Select recipient lists

Add regular lists or Smart Lists under Recipients. If you select several lists, a fan only needs to belong to one of them. The fan must also meet all additional conditions you set.

To build a group based on spending, messages, or subscription status, create a Smart List first. Then open Smart Lists under Recipients and select it. AgencyKey uses its rules directly; you do not need to enable OnlyFans sync.

For example, the Smart Lists guide selects Buyers $100+ as recipients and Buyers who messaged recently under Do not send. The team can handle those recent conversations individually. You can also pin the same groups above your chats.

Selecting a synced copy under OnlyFans lists uses that copy's membership instead. It may differ from the original Smart List while a sync is still in progress.

Exclusions take priority. A fan who is on both an included list and an excluded list will not receive the message.

In this teaching example for an online automation, Exclude recent chats is enabled with an Activity period of the past hour. Assume all other conditions are met.

Passing selection does not guarantee delivery. Before sending, the system still checks conditions such as whether the fan is online.

A welcome automation set to All new subscribers does not need an included list. Other automated event types need at least one.

For automated messages, use Smart Lists with Fans as their only audience. The Following audience is not supported here.

Skip recent chats

Recent chat exclusions were common in the online automations we reviewed. They let you skip fans your team has chatted with during the period you specify.

Enable Exclude recent chats and set the Activity period. The screenshot uses the past hour. This is an example: a different interval may suit shorter or longer conversations.

Under What counts as activity?, review the Regular mass messages and Priority messages switches. These switches control whether those sends count as recent activity. For example, enable priority messages if you want an online automation to wait after a priority campaign. Both switches are off by default.

The system checks recent conversations when selecting recipients and again before sending. An overlap is still possible if a conversation starts while the automated message is already being sent.

Exclude fans your team handles separately

If your team works individually with a group of fans, add their list under Do not send. For example, you could exclude regular buyers from a general invitation to chat.

Base the list on how your team works with those fans. High spending alone does not mean someone should never receive an automated message.

Skip chats with unread fan messages

Enable Exclude chats with unread messages from the fan to skip chats where your team has not yet read the fan's message.

This check happens before the first message of a chain. Canceling follow-ups after a new fan reply is a separate rule.

Understand variants and chains

Add a follow-up if it helps

In Message chains, click Add message to add a follow-up. You might send a greeting first, followed by a short message if the fan has not replied.

In this teaching example, set After previous: to 2 minutes and 0 seconds. This is a 120-second pause after the first message is successfully sent:

Are you still here? I would love to get to know you.

If the fan replies, the remaining messages in that chain are canceled. You do not need to enable a separate setting for this in the editor. Your team can continue the conversation.

Choose a follow-up that makes sense without an answer to the first message:

• Works without a reply: “Are you still here?”
• Needs a reply: “Why do you like that?” This assumes the fan has already told you what they like.

Leave questions that depend on the fan's answer to the team member handling the chat. Show your team all the messages in the chain so they know how the conversation starts.

Prepare message variants

A campaign can contain several message chains. To add another, click Add chain in Message chains. Each chain can contain a single message or several sent in order.

For example, you could prepare three ways to start a conversation: an introduction, a question about interests and an invitation to chat. Each variant could have an opening message and a short follow-up.

Each time the automation runs for a fan, it selects one chain and sends only that chain's messages.

In a new recurring automation with several chains, use Choose a chain for each event to select In order or Randomly, without repeating the previous variant. The system keeps this history separately for each fan.

Every variant should suit the selected audience. Avoid a question that only makes sense after a particular purchase in a general campaign: the system does not choose the chain based on what the fan has said in the chat.

Decide whether to delete messages automatically

For online messages, you may want to remove a short invitation once it is no longer relevant. You may prefer to keep a welcome message so your team can see how the conversation began.

Enable Delete messages automatically, then choose which messages to delete:

• Unread only leaves a message in the chat if it has been read.
• Read and unread allows deletion regardless of whether the message was read.

The timer starts separately for each successfully sent message. Purchased PPV messages are not deleted. A message may also remain if it can no longer be deleted.

Before enabling automatic deletion, check whether your team needs those messages in the conversation history.

Review and launch the automation

Save draft saves your settings and closes the editor. You must launch the campaign separately before it can send messages.

Before launching, check that:

• The model, event and recipients are correct.
• The text matches the model's language and tone.
• Delays and repeat limits are set.
• The appropriate chats and fan groups are excluded.
• Other campaigns will not send similar messages to the same audience at the same time.
• Your team has reviewed the message chain and is ready to respond.

When you are ready:

1. Find the draft in the table and open More actions → Edit campaign.
2. To start now, click Activate automation at the bottom of the editor. This opens the review window.
3. Check the settings and click Activate automation in that window.

For a later start, select At a scheduled time under Activate automation and set the date and time. The launch button is then labeled Schedule activation.

The activation time is when the system starts waiting for matching events. It is not a delivery time for every message.

After launching, check the first messages and replies. Make sure the intended fans received the messages and the team knows how to continue the conversations.

For a running automation, Edit name and note is the only editing action.

To change a live campaign's audience, messages or rules, open More actions → Create a copy and edit the copy. Before activating the copy, use Stop sending on the original campaign if the two should not run together.

Check whether the messages are helping

For a free welcome message, check whether fans reply and whether your team continues those conversations. You may need to read the chats or ask the team for a separate report: the campaign table does not show all this information. A Free label or a dash in Result does not tell you how many conversations the message started.

For paid messages, Result shows the buyer count, conversion and earnings. Campaign revenue covers purchases of that campaign's paid messages. Tips and later sales made in individual chats are not included. Refresh requests updated table data.

When comparing settings, change one substantial element at a time, such as the opening question. Use comparable periods and account for the audience and your team's availability to reply.

The Sent count tracks the first message of each chain; follow-ups do not increase it. In a teaching example, 10 fans each receive one chain of two messages. Sent shows 10, even if all 20 messages are sent.

With a recurring automation, the same fan can receive another chain, so the send count can exceed the number of unique recipients.

Troubleshoot missing or late messages

If the cause is unclear, contact support with the campaign name, model and time of the event so they can investigate.

Create a draft with the AI agent

The built-in AgencyKey AI agent can explain settings and create a campaign draft directly in the CRM. Select AI agent in the sidebar or click the floating AI button and describe what you need.

Creating a draft requires campaign creation permissions. When choosing a provider, check for a Read-only label: that option can explain settings but cannot create the campaign.

Replace @username with the model's username and try this prompt:

If the agent asks you to confirm creation, check the proposed settings. The saved draft appears under Mass Messages. Open it, review the model, text and recipients, then launch it when your team is ready to respond.