Capability template for customer success and account management
Account commitments check
Before the next customer conversation, the account manager gets one list of what each side promised in recent meetings and emails, each linked to its source and marked open, done or unclear, with a suggested owner. Nothing goes to the customer.
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 manager walks into the next conversation knowing what has been promised on both sides since the last review, and what became of each promise. Our own promises are in the list as plainly as the customer's. Nobody is surprised by something said six weeks ago in a meeting they did not attend.
Every line points to the meeting or email where it was said, in the words used. A promise whose date moved shows both dates and who agreed the change. A promise that has been kept shows the record that says so. A promise with no record of completion is marked open, not failed: the notes supplied may cover only part of the relationship, and the list says where they do not. Wording that was only a hope ("we'll try") is marked unclear until someone firms it up.
The list ends with the items that need a decision, each as a question for the account manager, who chooses whether to chase, complete or renegotiate. The AI assistant prepares the list. It writes nothing to the customer and changes no record.
Who starts the work, and when
The account manager or customer success manager who owns the account starts it a few days before a customer conversation, such as a renewal discussion, an escalation call or a regular check-in. It can run again when new notes arrive or the date of the conversation moves. The account manager reads the list, confirms or changes each owner and decides what to do about each open or unclear item.
What they supply
- Notes and emails from recent customer conversations, each with its date, type and attendees, for the period you set.
- Follow-through records, such as support tickets, release notes, delivery logs or sent files, with a date for each.
- The people on both sides, with each person's side and role.
- The settings: the account name, the period, today's date and the date of the next conversation.
- Where they have them: the draft agenda for that conversation.
What comes out
One list in a fixed order. At the top, the sources used, any stretch of time or meeting the sources do not cover, and the counts of commitments by side and by status. Then our commitments, the customer's, and any whose side the notes do not state. Each line gives the words, who said them and when, the due date and any change to it, the status with its evidence, and a suggested owner.
After the list come the open and unclear items that are not on the draft agenda, and the questions for the account manager. A commitment that touches price, scope or service levels is marked so it can be checked against the agreement; the assistant does not interpret the agreement.
An invented example
Illustrative example with invented data. An invented 40-person software company prepares for a conversation with Customer A, an invented 120-person logistics firm. The people are invented too: Maya, our account manager; Tom, our support lead; Ines, Customer A's operations director; Paul, Customer A's IT lead.
What the person supplies
Settings. Account: Customer A. Period: 1 September to 16 November 2026. Today: Monday 16 November 2026. Next conversation: Thursday 19 November 2026. Account manager: Maya. Gap length: the default, 21 days.
People. Maya, our side, account manager. Tom, our side, support lead. Ines, Customer A, operations director. Paul, Customer A, IT lead.
Draft agenda for 19 November. Renewal timeline. Dispatch module demo. Seat usage.
Source 1. Meeting, Tuesday 15 September 2026, "Quarterly check-in". Attendees: Maya, Tom, Ines, Paul. Notes:
- Ines said Customer A will send the list of depot users who need accounts by 25 September.
- Maya said she will confirm the price for the extra 30 seats before the end of September.
- Tom said the fix for the slow route-report export is in testing and will ship by 15 October.
- Paul will find out whether the single sign-on certificate renews in November.
- Ines would like a training session for dispatchers. Maya said "we'll try to find a time".
Source 2. Email, Monday 28 September 2026, Maya to Ines: "Hi Ines, the prices for the extra 30 seats are attached. Could you send the depot user list by Friday 2 October? We had it down for the 25th, and we need it to set up the accounts."
Source 3. Email, Tuesday 29 September 2026, Ines to Maya: "Thanks Maya. The list will come to you on Friday."
Source 4. Meeting, Tuesday 20 October 2026, "Support review call". Attendees: Maya, Tom, Ines. Notes:
- Tom said the route-report export fix has slipped; the new date is 6 November.
- Ines said "We'll name a second administrator next week."
- Maya said "I'll send you the training options this week."
- The September invoice will be corrected to show the right purchase order number.
- Tom has a call with Customer A's finance team on 3 November.
Follow-through records. Export with the headers Date, Reference, What happened:
- 2026-10-05, Ticket 3318: "Depot user list received from Ines (depot-users.xlsx)."
- 2026-11-06, Release 4.12: "Route-report export fix released to all customers."
What comes out
ACCOUNT COMMITMENTS CHECK: Customer A
For: Maya, account manager. Next conversation: Thursday 19 November 2026. Period: 1 September 2026 to 16 November 2026. Prepared: Monday 16 November 2026.
Sources used:
S1 Tuesday 15 September 2026, meeting, "Quarterly check-in".
S2 Monday 28 September 2026, email, Maya to Ines.
S3 Tuesday 29 September 2026, email, Ines to Maya.
S4 Tuesday 20 October 2026, meeting, "Support review call".
R1 Monday 5 October 2026, record, ticket 3318.
R2 Friday 6 November 2026, record, release 4.12.
Left out: none.
Coverage: 4 sources, 15 September to 20 October, and 2 follow-through records. Gap over 21 days: 20 October to 16 November (27 days), no source. Referred to, not supplied: Tom's call with Customer A's finance team on 3 November (S4).
Commitments: 7 (ours 3, theirs 3, side not stated 1). Open 3, done 3, unclear 1. Past due: 2.
OUR COMMITMENTS
C2 Maya to confirm the price for the extra 30 seats before the end of September. Made 15 September (S1: "before the end of September"). Due Wednesday 30 September (read as). Status: DONE. Evidence: S2, 28 September, email with the prices attached. Terms: price; check against the agreement. Suggested owner: Maya. Nothing further.
C5 Maya to send the dispatcher training options. Made 20 October (S4: "I'll send you the training options this week"); first raised 15 September (S1) as "we'll try to find a time", which was soft wording. Due Friday 23 October (read as). Status: OPEN, PAST DUE. Evidence: none; no source or record shows it done. That is not evidence it was not done. Suggested owner: Maya.
C3 Tom to ship the fix for the slow route-report export. Made 15 September (S1: "will ship by 15 October"). Due Friday 6 November, changed from Thursday 15 October by Tom (S4), the person who owes it. Status: DONE. Evidence: R2, 6 November, "Route-report export fix released to all customers." Suggested owner: Tom. Nothing further.
THEIR COMMITMENTS
C1 Ines to send the list of depot users who need accounts. Made 15 September (S1: "by 25 September"). Due Friday 2 October, changed from Friday 25 September by Ines (S3: "The list will come to you on Friday"), agreeing to the date Maya asked for in S2. Status: DONE. Evidence: R1, 5 October, "Depot user list received from Ines (depot-users.xlsx)." Suggested owner: Ines. Nothing further.
C6 Ines to name a second administrator. Made 20 October (S4: "next week"). Due Friday 30 October (read as). Status: OPEN, PAST DUE. Evidence: none; no source or record shows it done. That is not evidence it was not done. Suggested owner: Ines.
C4 Paul to find out whether the single sign-on certificate renews in November. Made 15 September (S1). Due: not stated. Status: OPEN. Evidence: none; no source or record shows it done. Suggested owner: Paul.
SIDE NOT STATED
C7 The September invoice to be corrected to show the right purchase order number. Made 20 October (S4); the notes do not say who said it. Due: not stated. Status: UNCLEAR, side not stated. Evidence: none; no source or record shows it done. Suggested owner: Maya, to establish whose it is.
NOT ON THE DRAFT AGENDA
Draft agenda supplied: 3 items (Renewal timeline; Dispatch module demo; Seat usage). Open or unclear items with no matching agenda line: C5, C6, C4, C7.
DECISIONS FOR MAYA: 4
1. C5, ours, past due since Friday 23 October. You said you would send the dispatcher training options that week and no record shows they went. Complete it, renegotiate the date, or leave it?
2. C6, theirs, past due since Friday 30 October. Ines said Customer A would name a second administrator the following week and no record shows a name. Chase it, renegotiate the date, or leave it?
3. C4, theirs, no due date. Paul said he would find out whether the single sign-on certificate renews in November and no source records an answer. Chase it, agree a date, or leave it?
4. C7, side not stated. The notes of the 20 October call do not say who promised the invoice correction; you, Tom and Ines were all present. Whose is it first?
Draft for Maya's review. Nothing has been sent to Customer A and no record has been changed.
Where it fits
- Software technology: fixes, access and training promised in support calls are easy to lose before the renewal.
- Professional services: promises about deliverables and dates are made by several people across a long engagement.
- Marketing and advertising: a retainer collects small promises in weekly calls and email threads.
- Customer success and account management: the check an account manager makes before facing the customer.
- Growth & scaling: more accounts per manager means more promises held only in memory.
- Established businesses: long relationships carry promises from before the current team.
It is separate from meeting agenda, notes and follow-ups, which serves one internal meeting, and from quarterly business review preparation, which builds the review around the customer's goals. It is also separate from the sales call preparation brief, which is a sales brief for one prospect that includes what has been said and promised so far; this is a two-sided list of promises with a status for each, for an existing customer. Account handoff records what was promised in the sale.
What has to change for your company
Decide how far back the period reaches and where the notes live. Set the owner you suggest by default for each kind of promise, such as support fixes, billing corrections and training. Decide which kinds of promise count as touching terms. Agree how long a gap in the sources is worth reporting. Decide which follow-through records the assistant may read. The account manager remains the person who confirms the list.
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. 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 an account whose history your account manager already knows, with cases agreed first: a promise whose date moved, a promise kept but never written down, a hopeful remark, a note with no speaker named. The account manager checks every line against its source before anyone relies on the list. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
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: