New engineer. The client doesn’t know yet.
Your best engineer is moving to a different account. Their replacement starts next week.
The client doesn’t know yet. How you introduce the new engineer determines whether the client sees this as a disruption or a non-event. Most MSPs send a one-line email. The good ones transfer trust deliberately.
The scenario:
You need to introduce a new primary engineer to a client in a way that maintains confidence.
The prompt:
You’re writing a client communication for an engineer transition.
Context: [paste the client relationship details, outgoing engineer’s tenure, and incoming engineer’s background]
Create a 3-part communication plan:
Email 1 (1 week before): Introduce the change, highlight the new engineer’s relevant experience, explain the transition plan
Email 2 (day of): Confirm the handoff is complete, provide the new engineer’s direct contact, list what’s been briefed
Follow-up call: New engineer reaches out within 48 hours to introduce themselves personally
Tone: Confident and planned, not reactive. The client should feel this is an upgrade, not a disruption.