The step-4 edge case (a customer converting mid-sequence) is the one that most embarrasses a company when missed, since nothing looks worse than emailing a new paying customer that their trial is about to end. Building the cancel-on-convert check in from the start avoids that.
Automation
Build a multi-step onboarding drip for new customers
A scenario prompt that converts a described five-email onboarding drip into a recipe with exact timing, engagement branching, and unsubscribe-mid-sequence handling.
Works with Claude / GPT950 uses★ 4.5
The prompt
automation-multi-step-onboarding-drip-email
A SaaS company describes their process like this: "When someone signs up for a free trial, I want a welcome email right away, a 'getting started' tips email two days later, a check-in email on day 5 asking if they need help, and if they haven't logged in by day 10, a re-engagement email before the trial ends on day 14." AVAILABLE TOOLS: [App signup event (trigger), Uncanny Automator, email/SMTP, app login-activity data] Turn this into an implementation-ready automation recipe, thinking through what the plain description leaves ambiguous: 1. Trigger and sequence: specify the exact scheduling mechanism for a five-email sequence spread across 14 days, and confirm it's built as independently timed sends off the signup timestamp rather than one send waiting on the previous send completing, so a delayed step 2 doesn't push every later step back. 2. Conditions: the day-10 re-engagement email depends on login activity, so state the exact query, "has not logged in since signup" versus "has not logged in in the last 10 days," since those produce different results for someone who logged in once on day 2 and never again. 3. Actions in order: for each of the five emails, confirm what cancels a later step, specifically, if the day-5 check-in email prompts a support ticket and the customer gets help, should the day-10 email still fire, or does resolved-support count as enough engagement to skip it. 4. Failure handling: if a customer converts to a paid plan on day 6, right between two scheduled emails, confirm the recipe cancels all remaining trial-onboarding emails rather than sending a "your trial is ending" email to a paying customer. 5. One edge case specific to this exact workflow: someone who unsubscribes from marketing email after the welcome email but is still an active trial user. Decide whether the remaining steps are purely transactional (should still send) or marketing (should stop), and justify the split. Replace the workflow description and available tools with your own.