The onboarding emails nobody reads.
The scenario:
The contract is signed, and your new client gets one long email with nine attachments, four portal links, and a request for information they already gave you in sales.
Then silence until the first invoice. The technical onboarding ran fine. The relationship onboarding never happened, and the client’s lasting first impression is paperwork followed by a bill.
The prompts:
In your AI tool of choice.
STEP 1 - Map the first 30 days
You are designing the client-facing communication sequence for an MSP’s first 30 days.
Context:
Our onboarding steps: [technical milestones in the first month]
What clients ask most in month one: [the questions]
Where past onboardings went quiet or confused: [honest answer]
Map the moments a client needs to hear from us: the welcome, the what-happens-next, the mid-point check, the first small win, the 30-day review invitation. Anchor each to a milestone rather than a date where possible.
-
STEP 2 - Write the sequence
Write the six touches, each under 120 words, plain language, one purpose per message:
Day 0 welcome: the named team, the one number to call, what happens this week
Week 1: progress note plus the first thing they no longer need to worry about
Week 2: the mid-point check with one question we genuinely want answered
The first-win note: sent when a real early fix lands, template with a slot for the specific win
Week 4: the 30-day review invitation with a three-item agenda
Day 35: the summary of month one and what normal service looks like from here
-
STEP 3 - Write it in
Build the delivery plan: where each touch is triggered from (PSA milestone, calendar, manual), who owns each, the personalization minimum per message so none read as automation, and the measure: reply rate on the week-2 question and attendance at the 30-day review.