Most agency onboarding advice covers the obvious pieces: intake form, kickoff agenda, access request, welcome email.
Those matter. But they're not usually where client trust leaks.
The messy parts are smaller and more awkward:
- confirming scope without sounding defensive
- translating sales promises into delivery reality
- explaining why a delay is now a timeline risk
- identifying stakeholders who can derail approvals
- restarting momentum when a client goes quiet
These are the moments teams handle from memory. Which means they get handled differently every time.
Here are five prompts — one for each of those moments — that I would add to any agency onboarding system because they cover the gaps most templates ignore.
Prompt 1 — Scope-lock confirmation
When to run it: Right after the proposal is signed, before kickoff.
What goes in: Proposal scope, any sales notes, and known exclusions.
What comes out: A client-facing confirmation that makes the boundary feel helpful instead of hostile.
You are writing a scope confirmation note for a new agency client.
Project scope:
[PASTE SIGNED SCOPE]
Known exclusions or assumptions:
[PASTE EXCLUSIONS / ASSUMPTIONS]
Write a short client-facing note that:
1. Confirms what is included in the project
2. Lists any important assumptions in plain language
3. Clarifies what is not included without sounding defensive
4. Explains how new requests will be handled if they come up
5. Ends with a friendly request to confirm alignment before kickoff
Tone: calm, confident, professional. Avoid legal language. Do not use phrases like "per our agreement" or "out of scope" unless absolutely necessary.
Why it matters: Most scope creep does not start with a malicious client. It starts with a vague shared understanding. This prompt turns the signed proposal into a usable working boundary before delivery pressure begins.
Prompt 2 — Sales-to-delivery handoff translator
When to run it: Before the internal kickoff.
What goes in: Sales call notes, proposal, and client intake answers.
What comes out: A delivery-team brief that separates promises from assumptions.
You are helping an agency hand a new client from sales to delivery.
Sales notes:
[PASTE NOTES]
Signed proposal:
[PASTE PROPOSAL OR SUMMARY]
Client intake answers:
[PASTE INTAKE]
Create an internal delivery handoff brief with these sections:
1. What the client believes they bought
2. What we are contractually responsible for
3. Promises or expectations mentioned in sales notes that need verification
4. Risks, constraints, or unclear items
5. Questions the delivery lead should ask before work starts
Be precise. If something is only implied, label it as [ASSUMPTION]. If something conflicts, label it as [CONFLICT — RESOLVE BEFORE DELIVERY].
Why it matters: The handoff problem is not usually lack of notes. It is lack of translation. Sales language is optimistic; delivery language needs to be operational.
Prompt 3 — Stakeholder and approval map
When to run it: After intake, before kickoff.
What goes in: Client contacts, departments, approval notes, and timeline.
What comes out: A simple map of who can approve, delay, or derail the project.
You are creating a stakeholder and approval map for a new client project.
Known contacts and roles:
[PASTE CONTACTS]
Project timeline:
[PASTE TIMELINE]
Any notes about approvals, legal, brand, finance, leadership, or external vendors:
[PASTE NOTES]
Create a practical stakeholder map:
1. Primary day-to-day contact
2. Final approver(s)
3. People likely to influence feedback or delay decisions
4. External dependencies or vendors
5. Approval risks to clarify in kickoff
6. Suggested kickoff question to uncover hidden stakeholders
If the information is missing, do not guess. Mark it as [UNKNOWN — ASK CLIENT].
Why it matters: Agencies often discover the real decision-maker only after the first deliverable is rejected. This prompt makes hidden approval risk visible early.
Prompt 4 — Timeline-impact follow-up
When to run it: When the client has missed an access, content, feedback, or approval deadline. "Just checking in" emails train clients to ignore you; this prompt turns the follow-up into a timeline conversation.
What goes in: What is missing, when it was requested, and what work it blocks.
What comes out: A firm but non-blaming follow-up that links missing input to timeline impact.
You are writing a client follow-up about a missing input that now affects the project timeline.
Missing item:
[WHAT IS MISSING]
Originally requested on:
[DATE]
Current project impact:
[WHAT THIS BLOCKS]
Deadline needed to avoid delay:
[DATE]
Write an email that:
1. Briefly reminds the client what is still needed
2. Explains why it matters in one sentence
3. States the timeline impact if it is not received by the deadline
4. Offers an easy next step or alternative if they are stuck
5. Stays professional and calm
Avoid blame. Avoid long apologies. Do not bury the deadline.
Why it matters: Timeline-impact emails teach clients that inputs and deadlines are connected — without blaming them for the delay.
Prompt 5 — Quiet-client reactivation note
When to run it: When a client disappears after signing or after kickoff.
What goes in: Last contact, pending items, and the next milestone.
What comes out: A reset message that restarts momentum without sounding annoyed.
You are writing to a client who has gone quiet during onboarding.
Last meaningful contact:
[DATE + CONTEXT]
Pending items:
[LIST]
Next milestone we are trying to reach:
[MILESTONE]
Write a short reactivation email that:
1. Acknowledges they may be busy without over-apologizing
2. Restates the next milestone and why it matters
3. Lists the smallest possible action they can take today
4. Gives two options if they need more time
5. Ends with a clear question that is easy to answer
Tone: helpful, direct, not passive-aggressive.
Why it matters: Silence is not always disinterest. Sometimes the client is overwhelmed, unsure what to send, or waiting for someone internally. The goal is to reduce the next action until it is easy to restart.
How to actually use these
Do not paste these into an LLM once and call it a system.
Put them into the moments where the problem happens:
- scope-lock confirmation → immediately after signing
- sales-to-delivery handoff → before internal kickoff
- stakeholder map → before client kickoff
- timeline-impact follow-up → after missed input deadlines
- quiet-client reactivation → after 5–7 days of silence
The prompts work because they turn vague judgment calls into repeatable micro-processes. Your team still uses judgment. They just no longer start from a blank page when the situation is tense.
If your agency already has intake forms and kickoff checklists, these are the next layer: the prompts for the uncomfortable middle of onboarding.
That middle is where trust usually breaks.
If you want a simple trigger map for where these fit, start with the free onboarding checklist at https://agencyonboardingos.com/checklist and add these prompts to the steps where your team currently improvises.
Lisa Sakura builds Agency Onboarding OS — practical onboarding workflows, templates, and AI prompts for small agencies at https://agencyonboardingos.com.
Top comments (0)