Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.fanaura.com/llms.txt

Use this file to discover all available pages before exploring further.

Every flow has a Settings tab where you configure how the flow behaves — who can enter, when messages send, and which sender identity to use. These settings apply to the entire flow and affect every fan who enters it.

​
Accessing Flow Settings

1

Open Your Flow

Open any flow in the Flow Builder.
2

Click the Settings Tab

Click the “Settings” tab at the top of the page (next to Canvas and Enrollment).

​
Flow Name and Description

​
Flow Name

The name you gave your flow when you created it. You can update it here at any time. Use descriptive names that tell you at a glance what the flow does:
  • “Presave Thank You — Email Drip”
  • “Release Day Multi-Channel Blast”
  • “IG DM Auto-Reply — LINK keyword”

​
Description

Add a description to explain the flow’s purpose in more detail. This is visible on the flow card in the launch detail page and helps team members understand the flow without opening it.
AI-generated descriptions are available — click the AI icon next to the description field and Fanaura will analyze your flow’s trigger, actions, and conditions to generate a clear summary automatically.
Even if you are a solo artist managing your own account, descriptions help future-you remember why you built each flow six months from now.

​
Enrollment Settings

These settings control how fans enter and interact with the flow.
Default: NoControls whether a fan can enter this flow more than once.
  • No (default): Once a fan has entered the flow, they cannot enter again — even if they trigger the event a second time. The flow runs once per fan.
  • Yes: Fans can enter the flow multiple times. Each trigger event creates a new enrollment.
When to use “No” (default):
  • Welcome sequences (you only want to welcome someone once)
  • Presave thank-you flows (one thank-you per presave is enough)
  • Any sequence where receiving it twice would feel repetitive
When to use “Yes”:
  • Purchase confirmation flows (fans may buy multiple items)
  • IG DM auto-responders (fans may DM different keywords at different times)
  • Always-on support flows where repeat interactions are expected

​
Timezone Settings

Timezone settings control when time-based actions and delays fire relative to clock time.
Default setting. All time-based operations use your account’s default timezone.
  • Delays like “Wait until 9 AM” fire at 9 AM in your timezone
  • Time windows use your timezone for start/end hours
  • Date-based delays use your timezone for midnight calculations
This works well when your fan base is concentrated in one timezone or region.
If you have fans in Australia, Europe, and the Americas, fan timezone is essential. Without it, a 9 AM EST send arrives at midnight in Sydney.

​
Time Windows

Time windows let you restrict when messages are sent, ensuring fans receive your messages during appropriate hours.

​
Enable Time Windows

Toggle on to activate time-restricted sending. When enabled, additional options appear:

​
Start Time and End Time

Set the window during which messages are allowed to send:
  • Start time: The earliest hour messages can send (e.g., 9:00 AM)
  • End time: The latest hour messages can send (e.g., 9:00 PM)
Messages scheduled outside this window do not get discarded — they wait until the next valid time. If a message is scheduled for 11 PM but your window ends at 9 PM, it will send at 9 AM the next day.

​
Active Days

Select which days of the week messages are allowed to send:
  • Monday through Friday: Business days only
  • Monday through Sunday: Every day (most common for fan engagement)
  • Custom selection: Check or uncheck individual days
Messages scheduled on inactive days wait until the next active day.

​
Example Configurations

  • Start: 9:00 AM
  • End: 9:00 PM
  • Days: Monday through Sunday
  • Timezone: Fan timezone
This ensures no fan receives a message before 9 AM or after 9 PM in their local time, any day of the week.

​
How Messages Queue During Off-Hours

When a fan reaches an action outside the time window:
  1. The message is queued (not discarded)
  2. Fanaura checks the next valid send time
  3. The message sends at the start of the next valid window
  4. Multiple queued messages send in sequence, with brief delays between them

​
Communication Defaults

Override your account-level defaults for this specific flow.
SettingDescriptionDefault
From NameThe sender name in the “From” field of emailsYour artist name
From EmailThe email address in the “From” fieldYour verified sending address
SMS NumberThe phone number used for SMS actionsYour provisioned SMS number
Override these defaults if a specific flow needs a different sender identity — for example, a flow from your record label or management team.

​
Analytics Settings

​
Mark Emails as Read

Controls whether emails sent from this flow are tracked for open/read status. This is typically enabled by default and is used for:
  • Open rate tracking
  • Fan-action delays (waiting for email open)
  • Conditions that check if a fan opened an email
Disabling this removes open tracking for emails in this flow, which some artists prefer for privacy-focused communications.

​
Settings Checklist

Before activating any flow, review these settings:
Review every setting before toggling your flow active. A misconfigured time window or enrollment rule can lead to unexpected fan experiences.
  • Flow name is clear and descriptive
  • Description explains the flow’s purpose
  • Re-entry is set correctly (do fans need to enter more than once?)
  • Stop on response is appropriate for this flow type
  • Timezone matches your audience (account vs. fan timezone)
  • Time window is configured if you want to restrict sending hours
  • Active days are set if you want to restrict sending days
  • From name and email are correct
  • SMS number is the right one (if you have multiple)

​
Tips and Best Practices

No one wants a text at 3 AM. Set a 9 AM - 9 PM window at minimum.
The effort is worth it. Fans notice when you respect their schedule.
Most flows should run once per fan. Only enable re-entry when repeated enrollment makes sense.
You will forget why you built a flow in three months. Descriptions save you from digging through the canvas to figure it out.
If you duplicate a flow, review the settings — they carry over from the original and might not be appropriate for the new flow.
When a fan replies to your pitch, a human should take over. Automated follow-ups after a real reply feel robotic.

​
What Happens Next

With your flow configured, you will want to monitor who enters it. Learn about enrollment tracking in Enrollment History.