All prompts
Onboarding Kickoff Sequence
Draft a three-email onboarding sequence tied to the outcome the customer bought, not a generic welcome tour.
Onboarding email fails when it introduces the product instead of driving the first outcome. The sequence that works has one job per email and pre-empts the place you already know customers get stuck.
01
The template
Copy it, swap the {{marked}} variables for your account, and run it.
Draft a 3-email onboarding sequence for a new customer. Each email should move
them toward their first real outcome, not just introduce features. Number them
and give each a subject line and a single clear call to action.
Customer: {{customer_name}}
Why they bought (the outcome they want): {{purchased_outcome}}
Who the emails go to (role, sophistication): {{recipient}}
The one action that = "activated" for us: {{activation_event}}
Timeline they expect: {{timeline}}
What tends to stall customers like this: {{known_friction}}
Rules:
- Each email has exactly one call to action. No "and also" pileups.
- Tie every email to their purchased outcome, not to our feature list.
- Email 2 should pre-empt the known friction point, not wait for them to hit it.
- Keep each email under 120 words. Onboarding email fatigue is real.
Variables
- {{customer_name}}
- Customer namee.g. Bellwether Retail
- {{purchased_outcome}}
- The outcome they boughte.g. get store managers off spreadsheets and into live inventory dashboards
- {{recipient}}
- Recipient role / sophisticatione.g. a regional ops lead, comfortable with tools but time-poor
- {{activation_event}}
- Your activation evente.g. three store managers log in and build their first dashboard
- {{timeline}}
- Expected timelinee.g. live before the holiday season, so roughly 4 weeks
- {{known_friction}}
- Known friction pointe.g. customers stall on connecting their POS data source in week 2
02
Worked example
A CSM at a retail-analytics vendor is onboarding a new account that needs to be live before the holiday rush. She knows from experience that accounts stall on the POS integration in week two, and she wants the sequence to head that off instead of firefighting it later.
Customer: Bellwether Retail Why they bought: get store managers off spreadsheets and into live inventory dashboards Who the emails go to: a regional ops lead, comfortable with tools but time-poor The one action that = activated: three store managers log in and build their first dashboard Timeline they expect: live before the holiday season, roughly 4 weeks What tends to stall customers like this: customers stall on connecting their POS data source in week 2
03
Good output vs bad output
GOODEvery email has one CTA, ties back to the holiday-readiness outcome, and Email 2 pre-empts the POS stall instead of waiting for it.
EMAIL 1 (Day 1) Subject: Let's get your first dashboard live this week You bought this to get your store managers out of spreadsheets before the holidays. That starts with one dashboard, one manager, this week. Reply with the name of the store you want to pilot and I'll set the first one up with you live. One 30-minute call, and you'll have something real to show. CTA: Reply with your pilot store. EMAIL 2 (Day 7) Subject: The step most teams get stuck on (POS data) Most teams hit a wall here: connecting your POS as the data source. It looks fiddly but it's a 15-minute job with the right person in the room. Here's the one-pager, and here's a slot to do it together so you don't lose a week to it. CTA: Book the POS connection session. EMAIL 3 (Day 14) Subject: Three managers live = you're set for the season You're one step from the finish line: three managers building their own dashboards. That's the point where this runs without you. Who are the other two managers, and can we get them in this week? CTA: Send me the two names.
BADLooks fine at a glance. Here is why it fails.
EMAIL 1 Subject: Welcome to Bellwether Retail's journey with us! We're so excited to have you on board! Our platform has powerful features including dashboards, alerts, reporting, integrations, mobile access, and much more. Log in anytime to explore everything we offer. Check out our help center, join our community, follow us on LinkedIn, and don't miss our webinars! EMAIL 2 Subject: Have you explored all our features yet? Just checking in! Have you had a chance to explore dashboards, alerts, and reporting? Let us know if you have any questions. We're here to help! EMAIL 3 Subject: How's it going? Hi again! Just following up to see how things are going. Feel free to reach out anytime. We hope you're loving the platform!
- No next stepEmail 1 lists seven things to do ("explore everything, help center, community, LinkedIn, webinars") which is the same as asking for nothing. The time-poor ops lead does none of them.
- Missing contextThe POS integration stall, the one thing the CSM knew would derail this account, is never addressed. The sequence walks straight into the known trap.
- Generic filler"How's it going?" and "we hope you're loving the platform" are check-ins with no action, the emails customers filter to trash.
- Wrong registerFeature-tour tone ("powerful features including...") ignores that they bought a specific outcome, not a product tour.
04
Guardrails
When NOT to use this
- Do not use a canned sequence for a strategic or heavily customized enterprise onboarding; those need a real project plan, not three emails.
- Skip if you do not actually know the activation event. A sequence with no target destination just adds noise.
Responsible use
- Do not schedule these to auto-send without a human tailoring the first line to the real person. Automation that ignores context is why customers ignore onboarding email.
- If you personalize with account data, keep it to what the customer already told you; do not surface internal notes.
A human must review the output before it reaches the customer.
05
Model + settings
- Model
- Claude Sonnet, this is bread-and-butter drafting.
- Temperature
- 0.6 (a bit higher, you want warmth and variety across three emails)
- Settings
- Feed it the activation event and the friction point every time; those two fields are what separate a real sequence from a welcome tour.
- Generate variants for different recipient sophistication levels and keep a small library.