Capability template for customer success and account management
Missed milestone client reply
When a client challenges a delay, a deliverable or an earlier commitment, the account director gets a draft reply and an internal action note that keep confirmed facts apart from proposed recovery steps and the decisions still needed. Nothing is sent.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
The account director answers an unhappy client with the record in hand instead of from memory. The reply responds to what the client actually said, states only what the project records and the delivery team support, and leaves every decision that belongs to the director visibly open. The client gets a prompt, specific answer, and the agency has not promised a date, a credit or a position on who was at fault before anyone with the authority has chosen.
The same pass produces the internal note the director needs before sending: which of the client's claims the records support, which they contradict, which are not in the records at all, and what has to be decided today.
Who starts the work, and when
The account director, or the account manager on the director's behalf, starts it when a client message challenges a missed date, an unsent deliverable or something the agency said earlier. It runs once per challenge. The director reads both pieces, edits them, takes the delivery team's confirmations, and decides whether, when and how the reply goes out. The director also decides on any concession and on any revised commitment.
What they supply
- The client's message, word for word, with the date it arrived.
- The agreed milestones: what was due, on which date, where it was agreed and who owns it.
- The approval history: each submission and each response, with dates.
- The scope and terms notes: the lines of the statement of work or schedule about revision rounds, feedback windows and extras.
- The record of what was said: anything either side told the other about scope, dates or extras, and where.
- Project status from the delivery team, with any date the delivery lead has confirmed, who confirmed it and when.
- The recovery options already authorised, and who authorised them. If there are none, say so.
- Your reply settings: sender, tone, channel, working days and how they are counted, any public holiday dates, and who authorises credits and fee changes.
- The client's subject line and the contact's name, if you want them used.
- Today's date.
What comes out
- A draft reply to the client, in your style. Facts appear only where a record supports them. Any date, concession or position that nobody has yet approved appears as a marked gap for the director to fill or remove.
- An internal action note with the client's points checked against the records, a dated timeline, the confirmed facts, the proposed recovery steps, the decisions needed with an owner for each, and what stays open.
If the records cannot support a reply, for example when the milestone record is missing, the capability says what it needs and drafts nothing.
An invented example
Illustrative example with invented data. The agency, the client, the project, the dates, the quotations and the roles below are all invented. The agency is an invented 28-person marketing agency building a landing page for a client called Client K. First come the inputs the account director supplied, in full, then the draft reply and internal action note the capability returned. The last input is today's date.
The inputs
Client message (received Friday 16 October 2026, 09:10, from Client K's marketing director)
We were promised the final landing-page copy on 9 October and nothing has
arrived. Our campaign launches on 26 October and we have lost a week. On
the kickoff call we were told a second round of revisions was included,
and now your team says it is extra. I need a firm build date today, and I
expect this sorted at no cost.
Milestone record
Milestone | Deliverable | Date agreed | Where agreed | Owner
M1 | Landing-page copy, first draft | 2026-10-02 | SOW v2, schedule table | Copy lead
M2 | Landing-page copy, final | 2026-10-09 | SOW v2, schedule table | Copy lead
M3 | Landing-page build, ready for review | 2026-10-21 | SOW v2, schedule table | Web lead
Scope and terms notes
SOW v2 section 3: "Two rounds of client revisions on copy are included; further rounds are quoted."
SOW v2 section 4: "Client feedback is due within two working days of each submission."
Approval history
Date | Item | By | Event | Note
2026-10-02 | Copy, first draft | Agency | Submitted |
2026-10-06 | Copy, first draft | Client | Changes requested | Round 1, 14 comments
2026-10-08 | Copy, version 2 | Agency | Submitted |
2026-10-12 | Copy, version 2 | Client | Changes requested | Round 2
2026-10-14 | Copy, version 3 | Agency | Submitted |
Commitments and statements record
Date | Said by | Channel | What was said
2026-09-21 | Account director | Kickoff call notes | Two rounds of copy revisions included.
2026-10-13 | Account manager | Email to client | Round 2 is outside the original scope and will be quoted.
Delivery status
Item | Status | Delivery-confirmed date | Confirmed by | Date confirmed | Condition
Copy, version 3 | With client for approval | | | |
Landing-page build | Not started | | Web lead | 2026-10-15 | Four working days from the day copy is approved
Authorised recovery options
Option | Authorised by | Conditions | Limit
Move the build ahead of another project | Delivery director, 2026-10-15 | Copy approved by Monday 19 October | Does not shorten the four-day build
Joint call with the copywriter to settle remaining changes | Account director | Client asks for the call; the agency arranges it within one working day of the request | None
Reply settings: sender the account director; email; plain, warm and direct; Monday to Friday; working days counted after the day of the event; no public holiday dates supplied; the person who authorises credits and fee changes is not named.
Today's date: Friday 16 October 2026.
The draft reply and internal action note
DRAFT REPLY: not sent
To: Client K's marketing director
Channel: email
Subject: Landing-page copy: where it stands
Thank you for writing this morning. I understand your campaign launches
on 26 October.
Where the copy stands: version 2 went to you on 8 October. You sent
changes on 12 October, and version 3 went to you on 14 October. It is with
you now for approval.
On the second round of revisions: [DECISION 1: the account director
states the agency's position here.]
Where the build stands: our web lead confirmed on 15 October that the
build takes four working days from the day the copy is approved.
[DECISION 2: the build date, stated only once the web lead has confirmed
it as a date.]
What we can do to help: if you approve the copy by Monday 19 October, our
delivery director has agreed to move your build ahead of another project;
this does not shorten the four-day build. I can also set up a call between
you and our copywriter to settle any remaining changes, arranged within
one working day of your asking. To keep the build on the shortest path, we
need your response on version 3 by today, Friday 16 October, which is the
end of the two-working-day feedback window in section 4 of our statement
of work.
On cost: [DECISION 3: the account director states the agency's position
here, after whoever authorises credits and fee changes has decided.]
[DECISION 4: when the account director will next be in touch.]
[Account director]
---
INTERNAL ACTION NOTE: Client K, landing page, 16 October 2026
Client's points checked
1. "We were promised the final landing-page copy on 9 October": Supported.
Milestone M2, final copy, agreed 9 October (SOW v2, schedule table).
2. "nothing has arrived": Contradicted. Approval history: version 2
submitted 8 October; version 3 submitted 14 October. The records do not
say either was submitted as the final copy, and show no approval.
3. "Our campaign launches on 26 October": Not in the records. The client's
statement only.
4. "we have lost a week": Responsibility disputed. 9 to 16 October is 7
calendar days and 5 working days, and the approval history shows no
approval of the final copy.
Dated facts: version 2 submitted 8 October; changes requested 12
October, 2 working days later (the feedback window in SOW section 4);
version 3 submitted 14 October, 2 working days after the changes were
requested. Cause not assigned.
5. "we were told a second round of revisions was included, and now your
team says it is extra": Records disagree. SOW section 3: "Two rounds of
client revisions on copy are included; further rounds are quoted."
Kickoff notes, 21 September: "Two rounds of copy revisions included."
Account manager email, 13 October: "Round 2 is outside the original
scope and will be quoted." Round 1 was requested 6 October, round 2 on
12 October. Not resolved here.
6. "I need a firm build date today": Request. See Decision 2. No build
date is delivery-confirmed.
7. "I expect this sorted at no cost": Request. See Decision 3. No credit,
fee change or free work is authorised in the options supplied.
Timeline
21 Sep (Mon) Kickoff: two revision rounds included (statements record).
2 Oct (Fri) M1 first draft due; submitted (milestone record; approval
history). Elapsed since 21 Sep: 11 calendar days; 9 working days
(22 to 25 Sep, 28 Sep to 2 Oct).
6 Oct (Tue) Client requested changes, round 1 (approval history). Elapsed
since 2 Oct: 4 calendar days; 2 working days (5, 6 Oct).
8 Oct (Thu) Version 2 submitted (approval history). Elapsed since 6 Oct:
2 calendar days; 2 working days (7, 8 Oct).
9 Oct (Fri) M2 final copy date (milestone record). Elapsed since 8 Oct:
1 calendar day; 1 working day (9 Oct).
12 Oct (Mon) Client requested changes, round 2 (approval history).
Elapsed since 9 Oct: 3 calendar days; 1 working day (12 Oct). Since
version 2 (8 Oct): 4 calendar days; 2 working days (9, 12 Oct), the
feedback window in SOW section 4 (scope notes).
13 Oct (Tue) Account manager email: round 2 outside scope (statements
record). Elapsed since 12 Oct: 1 calendar day; 1 working day (13 Oct).
14 Oct (Wed) Version 3 submitted (approval history). Elapsed since
13 Oct: 1 calendar day; 1 working day (14 Oct). Since 12 Oct: 2 calendar
days; 2 working days (13, 14 Oct).
15 Oct (Thu) Web lead confirmed four working days' build from approval
(delivery status). Delivery director authorised moving the build ahead
if copy is approved by 19 October (authorised recovery options).
Elapsed since 14 Oct: 1 calendar day; 1 working day (15 Oct).
16 Oct (Fri) Client message received; version 3 is awaiting approval
(client message; delivery status). Elapsed since 15 Oct: 1 calendar
day; 1 working day (16 Oct). Since version 3 (14 Oct): 2 calendar days;
2 working days (15, 16 Oct), so the SOW feedback window ends today
(scope notes). Since M2 (9 Oct): 7 calendar days; 5 working days
(12 to 16 Oct).
Confirmed facts
- Final copy date agreed: 9 October (M2) (milestone record).
- Version 2 submitted 8 October; version 3 submitted 14 October
(approval history).
- Client requested changes on 6 and 12 October (approval history).
- Version 3 is with the client for approval (delivery status).
- Web lead confirmed on 15 October that the build takes four working days
from the day copy is approved. No build date confirmed (delivery
status).
- SOW section 4: client feedback is due within two working days of each
submission; for version 3 that is 16 October (scope notes).
Proposed recovery steps
- Move the build ahead of another project (delivery director, 15 October;
conditions: copy approved by Monday 19 October, not yet met; date not
confirmed).
- Joint call with the copywriter (account director; conditions: client
asks for the call and the agency arranges it within one working day of
the request; date not confirmed).
Decisions needed
- DECISION 1: the agency's position on round 2. Decides: account director
(and whoever handles contracts, if it becomes a question about the
SOW's meaning). Facts: point 5. Needed by: no deadline stated by the
client.
- DECISION 2: whether and what build date to state, and the revised
commitment on M3 (agreed 21 October). Decides: account director, after
the web lead confirms a date. Facts: only a duration is confirmed; the
arithmetic from a confirmed duration, not a confirmed date: copy
approved Friday 16 October gives Thursday 22 October, already after
21 October; approved Monday 19 October gives Friday 23 October; approved
Tuesday 20 October gives Monday 26 October, the launch day; approved
Wednesday 21 October gives Tuesday 27 October, after it. Needed by:
today, per the client.
- DECISION 3: the agency's position on the client's expectation of no
cost. Decides: account director; any credit, fee change or free work is
for whoever authorises them, and none is authorised in the options
supplied. Facts: points 5 and 7. Needed by: no deadline stated on cost;
the client's "today" attaches to the build date.
- DECISION 4: when the account director will next be in touch. Decides:
account director. Facts: none in the records. Needed by: before sending.
Left open
- Responsibility for the week since 9 October is not assigned.
- Which of SOW section 3 and the 13 October email governs round 2 is not
settled. If it becomes a question of contract terms, take it to whoever
handles contracts.
- The 26 October launch date has not been checked against any project
record.
- No public holiday dates were supplied, so every Monday to Friday was
counted as a working day.
- Whether feedback on version 3 would count as a third round, which the
SOW says is quoted, is not settled; the request for a response could be
read as inviting one.
- The person who authorises credits and fee changes is not named in the
inputs.
Before sending
- The web lead confirms whether any build date can be stated (Decision 2).
- The delivery director's 15 October agreement is still in force.
- The reply states 16 October, the end of the SOW section 4 feedback
window, as the date for the client's response. That deadline falls on
the day of sending; decide whether to state it today, given that
approval by Monday 19 October is what the build-ahead option needs.
- The joint call is read as arranged by the agency within one working day
of the client asking; the option's conditions say so.
- The subject line is the assistant's wording and the contact's name was
not supplied; check both.
- Confirm that version 3 reached the right contact on 14 October; the
approval history records the submission, not receipt.
- Fill in or remove each of Decisions 1 to 4.
Nothing has been sent, offered or committed. The account director approves
the reply, any concession and any revised commitment.
Where it fits
- Customer success and account management, where the first answer to a challenge shapes the rest of the relationship.
- Project and delivery, whose confirmed dates are the only ones the reply may state.
- Marketing and advertising, where agencies run on dated deliverables, rounds of revisions and launch dates that sit on the client's side.
- Professional services, where the person who holds the client relationship also answers for the schedule.
- Software technology, for build projects with milestones, acceptance steps and a client who is counting days.
- Growth & scaling, when more accounts than the director can hold in their head are running at once.
It sits beside three neighbours without overlapping them. Customer reply drafting answers any customer message from a tone guide and approved answers. Support escalation brief hands a support case to a senior person. Client-status update preparation is the scheduled update, not the answer to a challenge.
What has to change for your company
Name who may approve the wording, any concession and a new date; the capability treats all three as the director's. List which recovery options you have already authorised and under what conditions, and keep that list current, because the capability will not propose anything outside it. Set your reply style and the channel. Decide where the scope notes and the record of earlier statements live so they can be supplied quickly. Agree how a disputed question of responsibility is handled in your firm; the capability leaves it open and flags it.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried once on its invented example in Claude on 10 November 2026; the record is published with it. That run was made before the template's later revisions, which answer what the run showed and what review found, so the record describes the earlier wording and the earlier example. It has not been run again. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on past challenges your account director already knows the outcome of, with cases written in advance: a claim the records contradict, a date nobody has confirmed, a recovery option nobody authorised, a scope statement that disagrees with an earlier email. The director checks every fact in the reply against the records before anything is sent. Client-status update preparation is a good companion once the relationship is steady again.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: