Lifecycle email flows

Lifecycle email flows are available to Fetchply super administrators under Admin → Email Flows. Use them for focused account messages such as welcoming a new user, checking in after a delay, or helping an inactive user continue setup.

Create a flow

1. Open Admin → Email Flows and select New flow.
2. Give the flow a clear internal name.
3. Choose when it starts: after a user verifies a new signup, or after a user has been inactive for a duration you choose.
4. Add email and wait steps in the order they should run.
5. Edit each email's subject, preview text, headline, message, and optional button.
6. Send yourself a test, then select Activate.

New flows begin as drafts and send nothing until activated. Signup flows do not backfill older accounts when first activated. Inactivity flows begin watching existing accounts after they use the dashboard again.

Personalize an email

You can use these variables in email content:

• {{name}} — the account holder's name
• {{email}} — the account email
• {{agentName}} — the first agent on the account, or a general fallback
• {{dashboardUrl}} — a link to the Fetchply dashboard

The live preview shows the branded email while you edit it. A test email uses sample account details and does not count as a flow delivery.

Add send-time conditions

Conditions are checked immediately before an email sends. A later email can require that the user is still inactive, has or does not have an agent, or has a detected open or click on an earlier email. When several conditions are added, all of them must match.

“No open detected” is not proof that an email was unread. Image blocking and email privacy features can hide or create open signals. Click detection is usually a stronger engagement signal.

Delivery safeguards

Only verified, non-banned customer accounts can enter a flow. Staff accounts are excluded. Fetchply leaves at least 24 hours between optional lifecycle emails across all flows for the same user. Every flow email includes a link to stop optional lifecycle messages, and a permanent delivery failure suppresses future flow mail to that account.

Pausing a flow keeps enrolled users in place without sending. Reactivating it lets them continue. Archiving stops the flow and removes it from the normal flow list.

Troubleshooting

A new user did not enter a signup flow

Confirm the flow was active before the account was created and that the user verified their email. Accounts created before the flow's first activation are not added later.

An email is waiting longer than its delay

The user may have received another optional lifecycle email recently. Fetchply waits until the 24-hour delivery gap has passed, then continues automatically.

A conditional email was skipped

Open the flow's Activity tab and check the recipient. Conditions use the account and engagement state available at send time. If any condition does not match, the email is skipped and the flow continues.

A delivery shows a provider uncertainty error

Fetchply does not automatically retry an email when the provider response is unclear, because doing so could send a duplicate. Review the recipient and provider activity before deciding on a manual follow-up.

Open or click numbers stay at zero

Confirm engagement webhooks are enabled for the sending account. Opens also depend on the recipient loading tracked images; clicks appear only for links in the email.