Write a client onboarding email for a newly signed engagement. Make it clear, warm, and operationally precise. Use only the approved facts below. Do not promise outcomes, dates, scope, support levels, access, legal terms, or exceptions that are not documented. Do not restate the entire contract. Client, engagement, and approved scope: [CLIENT AND SCOPE] Onboarding milestones, owners, and dates: [MILESTONES] What we need from the client: [CLIENT RESPONSIBILITIES] Communication, access, billing, and policy details: [POLICY DETAILS] Tone and sender relationship: [TONE AND SENDER] Produce: 1. A subject line and a 220-300 word onboarding email. 2. A scannable first-week checklist divided into “Our team,” “Your team,” and “Joint decisions.” 3. A short internal handoff note naming dependencies, risks, and items that require confirmation before kickoff. The email must include a welcome, one-sentence value reminder grounded in the approved scope, the kickoff date or how it will be scheduled, a named client action with a due date if supplied, one primary contact path, and a clear next milestone. State what happens if a dependency is delayed without blaming the client. If policy details conflict with a client request, describe the approved path rather than improvising an exception. Before answering, check that every commitment matches [MILESTONES] and [POLICY DETAILS], and that responsibilities are assigned to a person or team. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [CLIENT AND SCOPE] | Provide the client name, service or product purchased, approved scope, and any excluded work that needs to be clear. | Hearth & Pine Home Goods; 90-day paid-search management engagement covering Google Ads audit, campaign rebuild, and weekly optimization; landing-page development is excluded. |
| [MILESTONES] | List kickoff, setup, review, launch, or training milestones with owners and confirmed or provisional dates. | Kickoff Oct 3, client success manager Lena owns; account access due Oct 5; audit review Oct 14; rebuild proposal Oct 21; first campaigns target Oct 31 pending approval. |
| [CLIENT RESPONSIBILITIES] | List client inputs, access, approvals, attendees, and due dates needed to begin or continue work. | Marketing lead Jordan provides Google Ads and Analytics access, brand guidelines, conversion definitions, and one approver for ad copy by Oct 5. |
| [POLICY DETAILS] | Provide approved communication channels, response times, billing or access process, privacy rules, and escalation path. | Weekly email update every Tuesday; requests through shared project board; business-day response target is one day; billing questions go to [email protected]; no credentials in email. |
| [TONE AND SENDER] | State who is sending the email, their relationship to the client, and the desired tone. | Lena, client success manager; professional and practical, with a new client after contract signature. |
How to use
- Pull dates, owners, scope, and policies from the signed agreement and delivery plan before pasting them into the prompt.
- Keep client actions limited to the dependencies that actually gate kickoff; assign a due date when one is known.
- Compare the generated commitment language against the contract, especially around launch dates, support, access, and results.
- Follow up with: 'Create a client-facing project-board checklist from this email, with owner, due date, and dependency columns.'
Variations
Kickoff agenda
Use before the first onboarding meeting.
Create a 45-minute client kickoff agenda for [ENGAGEMENT]. Confirmed goals and scope: [SCOPE]. Attendees and roles: [ATTENDEES]. Decisions and inputs needed: [DEPENDENCIES]. Milestones: [MILESTONES]. Produce a timed agenda, preparation list for each side, and a decisions-and-actions table. Keep contract terms intact and do not promise unapproved deliverables. Check that every agenda item has an outcome, owner, or decision purpose.
Onboarding questionnaire
Use when you need structured information before delivery starts.
Create a client onboarding questionnaire for [SERVICE]. Information required for kickoff: [REQUIRED INPUTS]. Privacy and access rules: [POLICIES]. Client roles: [ROLES]. Produce grouped questions with a one-line reason for each, indicate required versus optional, and include a secure alternative for sensitive information. Do not request data that is unnecessary for the service. Check that every question maps to a delivery decision, setup task, or compliance need.
Delay update
Use when an onboarding dependency has slipped.
Write a client update about an onboarding delay. Engagement: [ENGAGEMENT]. Delayed dependency and owner: [DEPENDENCY]. Verified impact: [IMPACT]. Available paths and recommendation: [OPTIONS]. Next checkpoint: [NEXT CHECKPOINT]. Draft a 150-word email that states the fact, explains the schedule consequence without blame, gives the client a concrete action if needed, and names the next update. Do not promise a revised date unless confirmed. Check that the recommendation follows the approved scope and policy.
Tips
- Treat onboarding as a mutual plan: the client needs to know what your team will do as clearly as what they must provide.
- Name the dependency behind each date; “launch October 31 pending approval” is safer and more useful than an unconditional launch promise.
- Keep contract scope separate from optional ideas, so a welcome email does not accidentally create a new deliverable.
- Put credentials and sensitive files in the approved secure channel, not in the onboarding email or a chat transcript.
FAQ
How detailed should a client onboarding email be?
It should cover the first actions, owners, timing, and communication path. Put detailed working instructions in the project board, guide, or kickoff materials.
Should the email include all contract terms?
No. Reference the approved scope and the operational details needed to begin. Use the signed agreement for full legal and commercial terms.