Skip to main content
Automated messages let you set up a message once and let it send itself whenever a fan does something — subscribes, resubscribes, buys a PPV, or comes online. Unlike a regular mass message that you send by hand to a list, an automated message waits for the fan to act and then reaches out on its own. Navigate to Automation → Mass Messages, pick a model, and click New Message to get started.

What you can do

  • Greet new subscribers automatically the moment they subscribe
  • Welcome fans back when they resubscribe
  • Follow up with fans right after they buy a PPV
  • Reach out the moment a fan comes online
  • Send the message once per fan, or every time the fan matches
  • Add a pause so the same fan isn’t messaged too often
  • Temporarily pause and resume a live automation from the campaign table
  • Skip fans you’ve chatted with recently
  • Target the right audience with the same lists and filters as a regular mass message

New Message picker

When you click New Message, the picker opens with two groups: Pick a card under Automated messages to open the editor. The selected event appears as a full-width card in the editor header, followed by a When to send section for frequency and timing.

Triggers

Each automated message reacts to one fan event. Pick the trigger when you choose the card. While the campaign is still an editable draft, click the event card in the editor header to change it; the current message content remains in the form.

When to send

The When to send section is where you decide how the automated message behaves. It appears only for automated messages, not for regular mass messages.

Action

Choose how soon the message goes out after the fan triggers it:

Frequency

Choose how often the same fan can receive the message:

Trigger pause

This option appears only when Frequency is set to Send every time. Turn it on to wait a set number of hours before the same campaign can message that fan again, so an active fan isn’t messaged over and over.
Automations for the same model and event run independently. If a fan is eligible for several of them, more than one automation can start a message chain. Use audience rules, pauses, or campaign status to prevent unwanted overlap.

Skip recent chats

Automated messages share the same Send To section as regular mass messages — the same Include and Exclude rules and fan lists. For automated messages, the Exclude column has one extra option worth knowing. In the Exclude column, turn on Exclude recent chats and set a period in minutes. Fans with a chat inside that window are skipped when the audience is evaluated. This reduces interruptions but cannot prevent a fan from starting a new conversation after evaluation.
Exclude recent chats is available on regular mass messages too — it lives in the shared Send To section. See Targeting for the full Include / Exclude reference.

Targeting

Pick who an automated message can reach using the same filters as a regular campaign. Add filters to narrow the audience, and use excluded Fan Lists or Smart Lists to leave fans out. For Subscriber welcome, choose one of two audience modes:
  • All new subscribers — no included list is required. Excluded lists, additional conditions, creator-account exclusion, and recent-chat safeguards still apply.
  • Only fans in selected lists — choose at least one included Fan List or Smart List. Switching away from this mode does not erase the saved list selection.
Other automated events still require at least one included Fan List or Smart List before launch. For the full reference, see Targeting.

Tracking your automated messages

Automated campaigns appear in the same table as regular ones. A Type column shows whether each campaign is a regular Mass Message or which trigger it runs on (for example, Nudge or Subscriber welcome). Hover over the status of a finished campaign to see why it ended.

Pause and resume an automation

Use Pause campaign in the Mass Messages table to temporarily stop new trigger sends. A message already being sent may still complete. While the automation is Paused, matching fan events are ignored and are not saved for replay. After Resume campaign, the automation reacts only to new events. The pause confirmation also includes Pause scheduled messages, enabled by default. Keep it enabled to hold delayed messages already created by this automation; they are released for immediate sending when you resume. Clear it only when those already scheduled messages should continue even though new trigger sends are paused. Pause is reversible. Stop sending and starting deletion are permanent for that campaign’s future triggers. Pause and Resume also require the separate Pause and resume permission.

Editing a launched campaign

Once an automated campaign is launched, only its name and note can be changed. The trigger, rules, message, and audience are locked while it runs. To change anything else, duplicate the campaign and edit the copy.
Duplicating an automated campaign keeps it automated — the copy comes back with the same trigger and rules, ready to adjust.

Save, review, and launch

Save creates a draft; it does not activate the automation. Review its event, frequency, audience, message, price, and exclusions, then use Launch. Choose Now to start listening for events immediately or At a scheduled time to activate it later. The delay after the event is applied only after activation and an eligible event.

Permissions

Viewing campaigns, creating or editing drafts, launching, pausing and resuming, stopping, deleting sent messages, and changing the sending rate are separate permissions. Deleting sent messages from an active automation also stops future triggers permanently. Controls that your role cannot use are hidden or disabled, and creator scope determines which model accounts are available.

Common issues