Auto Messages

Use Auto Messages to create rules that send DMs automatically when a fan event happens.

Common uses include expiring subscriptions, renewals, top spenders, and live stream reminders.

Accessing Auto Messages

1. Open Fansly with the FBuddy extension enabled, then click the FBuddy icon in the top bar.
2. Select Auto Messages.
3. The Auto Messages panel opens so you can view and manage all rules.

If you see an Open Auto Messages card in creator chat, you can also click Open Auto Messages to open the same panel.

If the panel is not available and you are not on Pro, you will see an upgrade message.

Auto Messages features

Prerequisites

• Auto Messages is a Pro feature.
• A Management Session must be connected.
• The session must have Send Messages enabled.
• The Management Session status shows Configured or Not configured.

In the panel header, open Management Session status from Not configured to Configured by:

1. Clicking Open Setup.
2. Pasting your Fansly management claim link in Management Session URL.
3. Clicking Save Management Session URL (or Update Management Session URL if one is already saved).

If you also use Smart Lists, keep Send Messages set to ON and keep the other permissions off unless another feature specifically asks for them.

Creating and saving a rule

1. Open the Auto Messages panel.
2. Click New Auto Message.
3. Choose a Type.
4. Enter the trigger values for that type:
   • Expiring Subscribers: Days Before Expiry.
   • After Renewal: Days After Renewal.
   • Renewal Milestone: Milestone Month.
   • Top Spender Milestone: Top Percent.
   • Going Live: Auto Delete After.
5. Add your message text.
6. Add optional attachments in the media section.
7. Optional: choose a Subscription Tier filter (not available for Top Spender Milestone).
8. Toggle Active if you want the rule to run now, then click Save.

Tips:

• Save is blocked until Management Session is configured.
• A message is required before save.
• Message text supports up to 10,000 characters.

Trigger types

• Expiring Subscribers
  • Send after a fixed number of days before a subscription expires.
  • Allowed range: 0 to 365 days.
  • Optional Subscription Tier filter lets you limit this to one tier.
• After Renewal
  • Send after a renewal event.
  • Allowed range: 0 to 30 days.
  • Optional Subscription Tier filter limits scope.
• Renewal Milestone
  • Send when the subscription reaches a milestone month.
  • Allowed range: 1 to 120 months.
  • Optional Subscription Tier filter limits scope.
• Top Spender Milestone
  • Send to the highest-spending fans by percentage.
  • Allowed range: 1 to 100 percent.
  • No tier filter for this type.
• Going Live
  • Sends once per live stream to current subscribers, expired subscribers, and followers.
  • You can set Auto Delete After in the range 0 to 168 hours.
  • Set to 0 to disable auto-delete.

Message text can include placeholders using the toolbar buttons for personalization.

Going Live messages do not support placeholders.

Message fields

• Message: max 10,000 characters.
• Attachments: optional; sent in the exact order shown.
• Active: turn a rule on or off without deleting it.

Managing existing rules

• Active switch: pause or resume sending for one rule.
• Open the action menu (•••) on a rule to use:
  • Send Test DM: verify the rule can send.
  • Edit: update message, trigger, attachments, and active state.
  • Delete: remove a rule.
• Recent Logs shows recent sends with timestamp, fan, and rule type.
• Recent Logs shows the latest sends first (up to 25 entries).

Use the message icon in a log row to open the fan chat for that row.
For Going Live rows, it opens your Fansly creator chat.

Troubleshooting

• Management session is not configured: open Open Setup, save a valid Management Session URL, and make sure Send Messages is enabled.
• I don’t see the Save or Test buttons: your Management Session is likely Not configured; configure it and reopen.
• A rule saves but does not run: confirm your Management Session is configured and Send Messages is enabled, then check your Active toggle.
• Test DM fails: verify the same permission requirement above.
• I see save errors about field range: check the number is in the allowed range for that type.
• I want the feature visible but it is not: confirm you are signed into a Pro account.