Create an automation

An automation reacts on its own to what happens on a creator's MYM account: a new subscriber, a purchase, a fan coming online. It reads like a sentence: when this event happens, if the fan meets these conditions, then do this action. Automations open from Tools › Automations, creator by creator.

The list of automations

Choose the creator in the left column. The top of the page sums up her automations: Active automations, Messages sent, Open rate, Response rate, Conversion rate and Revenue.

The table shows one rule per row, with its Status, its Trigger, its Conditions, its Actions and the results of its sends. The All statuses and All automations filters narrow the list, and the search finds a rule by name. A click on a row opens its details, without leaving the list.

At the end of each row, an icon opens the Execution history, and the three-dot menu offers Pause, Resume, Edit, Archive or Delete, depending on the rule's state. To create one, click New automation.

The principle: when, if, then

The editor shows the rule's Flow on the left, one card per step, and the open step on the right. A click on a card opens its step.

• When: the event that triggers the rule, only one per automation;

• If: the conditions the fan must meet, optional;

• Next: the Rotation, which only appears if the message has several variants;

• Then: the action, only one per automation.

You type the rule's name at the top. Generate with AI suggests one based on the event, the conditions and the messages.

When: the event

The Trigger step sorts events into three groups.

Some events have settings, under Trigger settings:

• Near expiration: the number of Days before expiration, and the send time;

• Birthday: the Days before birthday (0 for the day itself), and the send time;

• Media purchase, New tip and MOD purchase: a Minimum amount, for example to react only to purchases of €50 and more;

• Fan online: Restrict to a time window, to react only to fans coming online from 18:00 to 23:00, for example.

If: the conditions

The Conditions step lists the Checks on the fan. Without a condition, every fan affected by the event passes. Add a condition offers three groups:

• Profile: Fan status (Subscriber, Former subscriber, Interested), Has one of these tags, Has none of these tags;

• Value: Total spent and Total tips above an amount, Subscription age in months;

• Activity: Currently online, No message received recently, No recent message from the fan, No unread message from the fan.

You choose the conditions that suit you, none is required. The ones you add stack up: the fan must meet all of them, at the time of the event. A condition the event makes pointless is not offered, such as the status on a New subscriber or Currently online on Fan online. On New interested, no condition is available.

Then: the action

The Action step offers three choices: Send a message, Notify Slack or Notify Discord. The last two alert your team in a channel, see Slack and Discord connectors.

With Send a message, you write a Sequence of 1 to 10 messages. The first goes out when the rule triggers, after the Initial delay if there is one, and each next one a chosen delay after the previous one, from a few seconds (a run of bubbles) to 30 days. Each message can carry media, free or paid, from €5 to €1,000, at a fixed price or based on the fan's spending (see Dynamic pricing). Without media, Automatic deletion removes the message if the fan does not reply, or when the next message goes out.

Add a variant creates another version of the sequence, up to 6. The Rotation step chooses how to spread them:

• Per fan: each fan receives the variants in turn, never the same one twice in a row;

• Random: a variant drawn at random at each trigger;

• Sequential: one variant after the other, across all fans.

The Send settings, shared by all variants, have three settings:

• Initial delay: the wait between the event and the first message, in minutes;

• Minimum delay per fan: the same fan does not receive this automation twice within this delay;

• Stop the sequence when a fan replies, on by default: the next messages do not go out to a fan who has replied.

Activate, edit, pause

Activate automation saves the rule and starts it. As long as a setting is missing (the name, the action, an empty message), a banner lists what to fix, and each point takes you to the right place.

Only one active automation per event and per action: a second New subscriber rule that sends a message pauses the first one, after confirmation in This action is already automated. A rule that sends a message and a rule that notifies Slack on the same event run together.

To edit an active rule, open it with Edit, then Save changes. The new version applies to the next triggers. Sequences already started keep their version, and you choose for the Runs not started yet: Apply the new version or Keep their version.

Pause stops handling new events. For sequences already triggered, you choose Cancel pending steps or Let them finish. A rule that has already run is archived, with Archive.

The safeguards

A few rules protect fans from too many messages. They only apply to the Send a message action.

• A minimum between two sends to the same fan. The Minimum delay per fan is at least 72 h. For Media purchase, New tip and MOD purchase, it goes down to 1 h.

• No late message. If a live event (subscription, resubscription, end of subscription, purchase, tip) arrives late, the message does not go out.

• No message in a conversation already under way. New subscriber and Resubscription do not write if someone, the fan or the team, has already written since the subscription. New interested only writes in an empty conversation.

• No voice message on New interested.

Follow the runs

The Execution history lists, for a rule, each fan affected, the date, the status (Queued, Sending, Completed, Partial success, Failed, Cancelled), the messages sent and the errors. A link opens the fan's conversation.

A rule's details, opened with a click on its row, show its trigger, its conditions, its sequence and the statistics of each message.