7-Day Customer Onboarding Email + Task Checklist Template

Send-ready, compliance-safe 7-day onboarding sequence with daily customer and agent checklists tailored for support teams.

What You'll Get

A complete 7-day email sequence (Day 1 â†’ Day 7). Each message includes subject (<=60 chars), preheader (<=100 chars), 120-220 word body, one primary CTA (text + URL), a single measurable success metric with timeframe, and an agent follow-up trigger with first-line script.

Daily customer task checklist (3 measurable tasks per day) and daily agent task checklist (1-3 actions tied to monitoring and follow-up triggers).

Top-of-document 2-line sequence summary (primary goal + expected 7-day activation metric), Day 1 A/B subject variants, and recommended send time window.

A 3-bullet agent playbook for escalations and handoff to success/renewals, plus 3 operational next steps to finalize scheduling.

Embedded assumption flags and prompts to request missing placeholders (plan_name, product_name, audience_segment, brand_voice, primary_cta_url) before generation.

Policy-safe wording guidance and reminders to run legal or privacy review where applicable (PHI/financial constraints flagged).

How to Use

1Populate all required placeholders: {{plan_name}}, {{product_name}}, {{audience_segment}}, {{brand_voice}}, {{primary_cta_url}}. If any are missing, run the prompt ask-step to collect them before generating the sequence.

2Run the prompt in ChatGPT, review the 'assumptions' section included in the draft, and confirm product capabilities and allowed offers with stakeholders.

3Verify and replace {{primary_cta_url}} with tracked links, confirm link destination pages exist and are localized, then import the sequence into your ESP (with subject A/B variants and recommended send window).

4Configure automation: set click/open monitoring, create follow-up workflows for agent triggers, and add tags/priority flags for escalation rules.

5Perform legal/privacy review for wording that touches billing, data handling, or regulated claims; then localize language and timing by market before scheduling.

Map CTA destinations and automate follow-ups

Before scheduling, confirm each CTA URL leads to the exact activation surface (signup step, setup wizard, KB article). Add UTM parameters and configure your automation so that the agent follow-up trigger (e.g., 'no CTA click in 48 hours') creates a ticket with the prewritten first-line script queued for the assigned support rep.

Works Best With

Best used for crafting production-ready 7-day onboarding flows that agents and CS teams can operationalize

Provide exact plan_name, product_name, brand_voice, audience_segment, and primary_cta_url to avoid clarification steps

Have activation AHA clearly defined (the single action that equals activation) so metrics and triggers are precise

Supply any legal/offer constraints, localization needs, and preferred send windows up front for final-ready copy

Prompt Template


## Goal
- Produce a production-ready 7-day customer onboarding email sequence plus a daily task checklist for new customers on {{plan_name}} that is ready to send and operable by support/CS agents.

## Inputs
- Context: product, plan, primary activation goal, time-to-first-value constraints.
- Stakeholders: customer success, support agents, marketing (for templates/links).
- Constraints: legal/policy wording, character limits, allowed offers.
- Desired tone: {{brand_voice}}.
- Required format: 7 daily emails (Day 1 â†’ Day 7) each with subject line, preheader, email body, one primary CTA (text + URL), measurable success metric, agent follow-up trigger, plus a customer task checklist and agent task checklist per day.
- If any required input is missing, the prompt below instructs the model to ask clarifying questions before generating final content.

## Prompt
You are a customer success copywriter and onboarding strategist. Generate a complete, send-ready 7-day onboarding email sequence + daily task checklist for new customers on {{plan_name}} for {{product_name}} targeting {{audience_segment}} in a {{brand_voice}} voice. Use {{primary_cta_url}} as the canonical CTA destination when a URL is required.

Produce output as Markdown. For each Day 1 â†’ Day 7 include these sections and constraints exactly:

- Day heading: "Day X â€” [One-line aim]"
- Email
  - Subject line (<= 60 characters)
  - Preheader (<= 100 characters)
  - Body (concise, scannable; 120-220 words). Use short paragraphs and 1-3 bulleted steps where helpful.
  - Primary CTA: provide CTA text and the URL (use {{primary_cta_url}} unless a different URL is explicitly provided).
  - Measurable success metric: name a single KPI for this message (e.g., open rate target, CTR target, task completion %), expressed as a numeric target and timeframe.
  - Agent follow-up trigger: specify a clear rule for when an agent should follow up (e.g., "If CTA not clicked within 48 hours, trigger X"), the follow-up channel, and the exact first-line script for the agent (1-2 sentences).
- Customer task checklist (3 specific tasks the customer can complete that day to progress toward activation; each task must be measurable).
- Agent task checklist (1-3 actions for CS/support to take that day tied to the follow-up trigger or monitoring).

Also include:
- At the top, a 2-line sequence summary (primary goal and expected activation metric after 7 days).
- After Day 7, include a 3-bullet agent playbook summarizing escalation rules and the final handoff to success/renewals.
- At the end, provide 2 suggested subject-line A/B test variants for Day 1 and the recommended send time window.

Behavioral constraints and style rules:
- Do not include any claims about guarantees or legal commitments.
- Separate facts vs assumptions: flag any assumption you made about product capabilities or links.
- Keep language policy-safe and tone-appropriate to {{brand_voice}}.
- Ensure CTAs are actionable and measurable.
- If any of the required placeholders ({{plan_name}}, {{product_name}}, {{audience_segment}}, {{brand_voice}}, {{primary_cta_url}}) are missing or ambiguous, ask these specific clarifying questions before generating the full sequence:
  1) Confirm the exact {{plan_name}} label to appear in messaging.
  2) Confirm the main activation AHA for {{product_name}} (what a customer must do to be "activated").
  3) Confirm any legal or offer constraints to avoid mentions or promises.
- Output only the requested sequence and playbook in Markdown; do not include commentary or drafts.

## Output Format
Support: Diagnosis questions â†’ Response draft â†’ Next steps

- Diagnosis questions: For missing inputs, list the clarifying questions from the Prompt section.
- Response draft: The full 7-day sequence as specified (Day headings, Email, CTA, metric, agent follow-up trigger, customer and agent checklists), plus the 2-line sequence summary, 3-bullet agent playbook, and Day 1 A/B subject variants.
- Next steps: A short list (3 items) of operational actions for stakeholders to finalize and schedule the sequence (e.g., link verification, localization, automation setup).

## Guardrails
- Separate facts vs assumptions at top of the draft: explicitly label any assumptions used.
- No policy or legal claims without source; flag any content that may require legal review.
- Subject line and preheader length limits must be respected.
- Success metrics must be realistic and expressed numerically with timeframe.
- Agent follow-up triggers must include timeframe, channel, and first-line script.
- Escalation: if a customer fails to engage by Day 7 and shows negative sentiment in replies, route to human CS with priority flag and include a suggested 1-paragraph escalation note.
- Keep placeholders intact; do not invent URLs or plan names beyond the provided {{plan_name}} and {{primary_cta_url}}.

## Examples
- Mini decisions/actions excerpt (example output for Day 1):
  - Decision: Send Day 1 welcome email with onboarding checklist.
  - Actions: Owner: CS Ops â€” verify {{primary_cta_url}} and embed tracking (due: today); Owner: Agent â€” monitor CTA clicks and trigger follow-up if no click in 48 hours (script provided in email).

Variables

Usage Notes

Not for

â€¢ Handling PHI/medical onboarding that requires HIPAA workflows or storing health data.

â€¢ Replacing legal or billing authorization workflows that require signed agreements or regulated disclosures.

â€¢ Deployments where you cannot add tracking parameters or automated follow-up due to customer privacy constraints.

Do not include

â€¢ Any real customer PII (account numbers, SSNs, medical data) inside templates or example CTAs.

â€¢ Unverified promises, guaranteed outcomes, or legal/financial claims.

â€¢ Hard-coded URLs or plan names when those placeholders are not provided.

7-Day Customer Onboarding Email + Task Checklist Template

Generate a production-ready 7-day onboarding email sequence for a specific plan, with measurable KPIs, agent follow-up triggers and daily task checklists for customers and agents.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

Auto-fill & personalize from your inputs

AI-assisted edits: tone, structure, constraints

Attach context so outputs stay consistent

Iterate and save versions

What you'll get

Output format

Markdown

Best used when

When working on template or detailed.

Avoid when

Handling PHI/medical onboarding that requires HIPAA workflows or storing health data.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Plan Name