Onboarding Welcome And First-Value Sequence
Designs a multi-touch onboarding email sequence that drives a new customer to their first 'aha' moment fast.
Prompt
ROLE: You are a Customer Success onboarding strategist who designs sequences that get users to first value quickly.
CONTEXT: Product: [PRODUCT]. New customer segment: [SEGMENT]. Their primary goal / job-to-be-done: [GOAL]. The single action that correlates most with retention ('activation event'): [ACTIVATION_EVENT]. Typical time-to-value: [TTV]. Resources available to link: [RESOURCES].
TASK: Design a 4-email onboarding sequence:
1. Email 1 (Day 0): warm welcome + one clear first step toward GOAL.
2. Email 2 (Day 2): guide them to ACTIVATION_EVENT with a quick win.
3. Email 3 (Day 5): deepen usage with a tip tied to their segment and link a relevant resource.
4. Email 4 (Day 9): check progress, offer a human (book a call), and reinforce the outcome.
For each: give send timing, subject line, 70-110 word body, and one primary CTA.
OUTPUT FORMAT: A table-like block per email: Day | Subject | Body | CTA | Goal of this touch.
CONSTRAINTS: Each email must have exactly one primary CTA. Orient every message around GOAL and ACTIVATION_EVENT, not feature tours. No more than one resource link per email. Keep tone encouraging, never pushy. Avoid sending before value is plausible per TTV.How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniquePins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueForces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Customer Support & Success
Empathetic Escalation De-Escalation Reply
Crafts a calm, accountable reply that defuses an angry customer, acknowledges the failure, and offers a concrete remedy.
Tiered Triage And Severity Classifier
Classifies an inbound support ticket by severity, category, and routing queue with a justification and suggested SLA.
Knowledge Base Article From A Resolved Ticket
Converts a closed support conversation into a clean, searchable, evergreen help-center article with steps and edge cases.
Churn-Risk Save Outreach For At-Risk Accounts
Drafts a personalized retention outreach to a customer showing churn signals, anchored on their goals and usage data.