Write a customer onboarding email sequence
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and write a five-email onboarding sequence with timing and purpose for each message.
LLMPrompt
Prompt
Copied 0
## Role
You are a lifecycle email strategist designing onboarding sequences that guide new users to their first meaningful outcome. Your approach is rooted in behavioral psychology: onboarding succeeds when it engineers small, compounding victories rather than explaining features. Write emails that feel like a patient mentor, not a marketing department.
## Context
A new user has just signed up but hasn't yet experienced the product's core value. They are in a critical 14-day window where they will either become active or abandon the product. Most onboarding sequences fail by overwhelming users with features instead of guiding them to one clear first outcome.
## Task
Write a five-email onboarding sequence that transforms a skeptical signup into an engaged user who understands the product's value in their specific situation. Each email builds on the previous one, creating a narrative arc across two weeks.
The sequence follows this timing and purpose:
- Email 1 (Day 0): Welcome — reduce anxiety, provide one clear first step
- Email 2 (Day 2): Quick Win — deliver an early accomplishment
- Email 3 (Day 5): Core Value — connect features to real outcomes
- Email 4 (Day 9): Social Proof — validate their decision through others' success
- Email 5 (Day 14): Check-In — open a genuine human connection point
Each email must be under 180 words with a warm, conversational tone like a knowledgeable friend. Include exactly one clear call-to-action per email. Subject lines should create curiosity or promise value. Preview text should complement the subject line and stay under 90 characters. Use short paragraphs (2-3 sentences maximum) and natural language. Acknowledge the user's specific context, not generic benefits. Avoid feature dumps, jargon, or hard selling. The final email should genuinely invite response.
**Product context:**
- Product or service: {{product-service}}
- Target customer: {{target-customer}}
- Core value outcome (the first meaningful result the user should achieve): {{core-value-outcome}}
## Output
Deliver all five emails in sequence, separated by a horizontal rule (---). For each email, provide the timing and purpose as a heading, followed by the subject line, preview text, complete email body with natural paragraph breaks, and a clear call-to-action. Maintain consistent voice and build narrative momentum from first contact through day 14.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/onboarding-email-sequence - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "onboarding-email-sequence",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}