Capability template for customer success and account management
Feedback follow-through updates
When a change ships or a decision lands on something customers asked for, your account owner gets the list of who asked, the confirmed status of each request, and an individual draft update for each person in the channel they prefer. No update promises a date or feature the team has not confirmed.
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
Every customer who took the time to ask hears back, personally, about what they asked for. The update speaks to their request, in their terms: what is live now, what part is still open and where that part stands. It arrives by email, in a call, in a message or at their next account meeting, whichever they prefer.
Nothing in it runs ahead of the team. Each date and each feature in a draft is traced to the change record the product or service team confirmed, and the draft shows where each one came from. Internal targets stay internal. A customer who has asked not to be contacted, or who tied the request to cancelling or to looking at other tools, is held back for the account owner to handle in person.
The account owner approves every update and sends it. The AI assistant sends nothing and changes no record.
Who starts the work, and when
The account manager or customer success manager starts it once the responsible team has confirmed, in writing, what a change does, what it leaves out and when it is available, or has decided not to go ahead. That is usually the day a change goes live or the week a decision is made. It runs once per change, across the account owner's own accounts.
The product manager or service lead who owns the change confirms the status. The account owner checks any open question with them before anything is sent.
What they supply
- The change record. What the change does and does not do, the status of each part left out, who gets it and from when, what may be shared, any workaround and guide, and what must not be mentioned, with the name of the role that confirmed it.
- The feedback export. One row per request, with its link to the change, the requester and the account owner.
- The contact preferences export. Each person's preferred channel, whether they have asked not to be contacted, and any timing notes.
- The run settings. The account owner, today's date and the responsible team.
- Style notes, if you have them: sign-off, tone and words you avoid.
What comes out
A single draft for the account owner, in a fixed order:
- The status to verify, restated from the change record, with any question the record leaves open.
- The requesters, one line per person: what they asked for and when, their status and the points it rests on, and how they will hear. Repeat requests from one person are merged.
- The draft updates, one per person, each in their channel, each ending with a check that traces every date and feature it mentions.
- The held requests, with the reason: account owner first, not to be contacted, requester to confirm, status unclear.
- Possible matches not linked to the change, requests on other owners' accounts, and the requests a person marks as updated after sending.
An invented example
Illustrative example with invented data. Company A, the customers, the people, the requests and the dates below are all invented. Company A is an invented 40-person company that sells visit-scheduling software to cleaning and maintenance businesses. Its product team shipped a spreadsheet export that several customers had asked for. Jo Harlan, an account manager, supplied the inputs below in full on Wednesday 4 November 2026; the follow-through the capability returned comes after them.
The inputs
1. The change record (from the product manager for scheduling)
Change: Schedule export to spreadsheet
Item ID: FR-112
Decision: shipped
Available from: 2 November 2026
Date confirmed by: Product manager, scheduling, 3 November 2026
Available to: all plans
What it does:
1. Exports the visits for any chosen date range, from Reports > Visits > Export.
2. Produces a CSV file that opens in common spreadsheet programs.
3. Gives each visit's date, start time, customer name, address, assigned
crew, visit type and status.
What it does not do:
1. Send the export automatically on a schedule. Status: under review.
2. Include custom fields, such as a customer's own reference field.
Status: planned, no date.
Reason we can share: (blank)
Workaround we can share: For now, anyone with access to Reports can run
the export by hand for the week they need. Answers: What it does not do 1.
Guide: Help article "Exporting visits to a spreadsheet"
Search words: export, spreadsheet, CSV, download
Do not mention: The internal target of Q1 2027 for custom fields. It is
not confirmed.
Status confirmed by: Product manager, scheduling, 3 November 2026
2. The feedback export
request_id,received_date,account,requester_name,requester_role,channel_received,request_text,linked_item,plan,account_owner
R-201,2026-06-09,Customer B,Marta Quill,Operations manager,email,"We need the week's visits in a spreadsheet for payroll. Copying them over by hand takes most of Friday afternoon.",FR-112,Standard,Jo Harlan
R-208,2026-07-02,Customer D,Lena Osei,Office administrator,in-app message,"Is there a way to download the schedule? Our crew leads want a printed copy.",,Plus,Jo Harlan
R-214,2026-07-15,Customer C,Theo Brandt,Owner,in-app message,"Could the schedule export go out by itself every Monday at 7am to my office manager?",FR-112,Standard,Jo Harlan
R-219,2026-08-04,Customer D,Lena Osei,Office administrator,email,"When you add the export, please include our customer reference field. We match visits to invoices on it.",FR-112,Plus,Jo Harlan
R-220,2026-09-21,Customer B,Marta Quill,Operations manager,email,"Any news on the spreadsheet export?",FR-112,Standard,Jo Harlan
R-223,2026-09-30,Customer E,Accounts team,,in-app message,"Need visits as CSV for month-end.",FR-112,Standard,Jo Harlan
R-226,2026-10-12,Customer F,Owen Paddick,Director,email,"Still no export. If this isn't sorted before our renewal in December we will look at other tools.",FR-112,Plus,Jo Harlan
R-229,2026-10-20,Customer G,Ruth Kanne,Finance lead,phone call,"Asked for a spreadsheet export of the month's visits.",FR-112,Standard,Jo Harlan
R-231,2026-10-27,Customer H,Sam Ivers,Operations lead,email,"Export to spreadsheet please.",FR-112,Standard,Kit Morrow
3. The contact preferences export
account,requester_name,preferred_channel,do_not_contact,notes
Customer B,Marta Quill,email,no,
Customer C,Theo Brandt,phone call,no,Mornings before 10am
Customer D,Lena Osei,account meeting,no,Next quarterly review 18 November 2026
Customer F,Owen Paddick,email,no,Renewal 1 December 2026
Customer G,Ruth Kanne,email,yes,Asked on 22 October 2026 not to receive product update messages
Customer H,Sam Ivers,email,no,
4. Run settings and style notes
Account owner: Jo Harlan, account manager
Today: 4 November 2026
Responsible team: Product manager, scheduling
Style notes: none
The output
FEEDBACK FOLLOW-THROUGH UPDATES: Schedule export to spreadsheet (FR-112)
For: Jo Harlan, account manager. Prepared 4 November 2026 from: change record confirmed by the product manager, scheduling, on 3 November 2026; feedback export (9 rows; 8 linked to FR-112; 7 of those on Jo Harlan's accounts); contact preferences (6 rows).
STATUS TO VERIFY WITH THE PRODUCT MANAGER, SCHEDULING
- Decision: shipped. Available from: 2 November 2026. Available to: all plans.
- What it does: 1. Exports the visits for any chosen date range, from Reports > Visits > Export. 2. Produces a CSV file that opens in common spreadsheet programs. 3. Gives each visit's date, start time, customer name, address, assigned crew, visit type and status.
- What it does not do: 1. Send the export automatically on a schedule: under review. 2. Include custom fields, such as a customer's own reference field: planned, no date.
- Reason we can share: none supplied. Workaround we can share: anyone with access to Reports can run the export by hand for the week they need (answers What it does not do 1). Guide: help article "Exporting visits to a spreadsheet".
- Questions before anything is sent: none.
REQUESTERS: 6 requesters at 6 accounts, from 7 linked requests (1 merged as a repeat request)
- Marta Quill, Operations manager, Customer B. Requests R-201 and R-220, received 9 June 2026 and 21 September 2026, via email. Asked for: the week's visits in a spreadsheet for payroll; then asked for news. Status: Delivered. Basis: What it does 1, 2, 3. Update by: email. Draft: D1.
- Theo Brandt, Owner, Customer C. Request R-214, received 15 July 2026, via in-app message. Asked for: the schedule export sent automatically every Monday at 7am to his office manager. Status: Partly delivered: the export is live; sending it automatically on a schedule is under review, no date set. Basis: What it does 1, 2; What it does not do 1. Update by: phone call, mornings before 10am. Draft: D2.
- Lena Osei, Office administrator, Customer D. Request R-219, received 4 August 2026, via email. Asked for: the export, including the account's customer reference field, which it uses to match visits to invoices. Status: Partly delivered: the export is live; custom fields, including the customer reference field, are planned, no date set. Basis: What it does 1, 2; What it does not do 2. Update by: account meeting, 18 November 2026. Draft: D3.
- Accounts team, role not stated, Customer E. Request R-223, received 30 September 2026, via in-app message. Asked for: visits as a CSV file for month-end. Status: Delivered. Basis: What it does 1, 2. Update by: none while held. Draft: held: Requester to confirm.
- Owen Paddick, Director, Customer F. Request R-226, received 12 October 2026, via email. Asked for: the export, before the account's renewal in December. Status: Delivered. Basis: What it does 1, 2. Update by: none while held. Draft: held: Account owner first.
- Ruth Kanne, Finance lead, Customer G. Request R-229, received 20 October 2026, via phone call. Asked for: a spreadsheet export of the month's visits. Status: Delivered. Basis: What it does 1, 2. Update by: none while held. Draft: held: Not to be contacted.
DRAFT UPDATES (for Jo Harlan to edit and approve)
D1. To: Marta Quill, Customer B. Channel: email.
Subject: The spreadsheet export you asked for is live
Body:
Hi Marta,
In June you asked for a way to get the week's visits into a spreadsheet for payroll, and you checked in again in September. That export went live on 2 November 2026, on all plans.
Go to Reports > Visits > Export and choose a date range. You get a CSV file that opens in common spreadsheet programs, with each visit's date, start time, customer name, address, assigned crew, visit type and status.
The help article "Exporting visits to a spreadsheet" walks through it. If it does not fit how you run payroll, reply and tell me what is missing.
Jo Harlan
Promise check: dates: June (R-201, received 9 June 2026), September (R-220, received 21 September 2026), 2 November 2026 (Available from). Features: date-range export from Reports > Visits > Export (What it does 1); CSV file for spreadsheet programs (What it does 2); the visit details listed (What it does 3); all plans (Available to).
D2. To: Theo Brandt, Customer C. Channel: phone call.
Call: mornings before 10am.
Talking points:
- In July you asked whether the schedule export could go out by itself every Monday at 7am to your office manager.
- The export went live on 2 November 2026, on all plans: Reports > Visits > Export, any date range, as a CSV file.
- Sending it automatically on a schedule is not part of this change. It is under review, no date set.
- Anyone with access to Reports can run the export by hand for the week they need.
- The help article "Exporting visits to a spreadsheet" shows how.
- Would running it by hand each Monday cover what your office manager needs?
Not to say: any date or timing for automatic sending, and any timing word such as "for now" or "soon".
Promise check: dates: July (R-214, received 15 July 2026), 2 November 2026 (Available from); "every Monday at 7am" repeats the customer's own request and commits to nothing. Features: date-range export from Reports > Visits > Export (What it does 1); CSV file (What it does 2); all plans (Available to); running it by hand (Workaround we can share).
D3. To: Lena Osei, Customer D. Channel: account meeting.
Meeting: 18 November 2026.
Agenda line: The visit export, and your customer reference field.
Talking points:
- In August you asked for the visit export to include your customer reference field, which you use to match visits to invoices.
- The export went live on 2 November 2026, on all plans: Reports > Visits > Export, any date range, as a CSV file that opens in common spreadsheet programs.
- Custom fields, including your customer reference field, are not in the export. They are planned, no date set.
- The help article "Exporting visits to a spreadsheet" shows how to run it.
- How do you match visits to invoices without the reference field in the export?
Not to say: any date or quarter for custom fields, including the internal target under "Do not mention".
Promise check: dates: August (R-219, received 4 August 2026), 2 November 2026 (Available from). Features: date-range export from Reports > Visits > Export (What it does 1); CSV file for spreadsheet programs (What it does 2); all plans (Available to). Open part: custom fields, planned, no date set (What it does not do 2).
HELD, NO DRAFT
- Account owner first: R-226, Owen Paddick, Customer F. The request says the company will look at other tools if the export is not sorted before its renewal in December; the contact notes give the renewal as 1 December 2026. Status: Delivered.
- Not to be contacted: R-229, Ruth Kanne, Customer G. do_not_contact is yes; the notes say she asked on 22 October 2026 not to receive product update messages. Status: Delivered.
- Requester to confirm: R-223, Accounts team, Customer E. A team name rather than a person, and not in the contact preferences. Status: Delivered.
- Status unclear: none.
POSSIBLE MATCHES NOT INCLUDED
- R-208, Customer D, Lena Osei, received 2 July 2026: asks whether the schedule can be downloaded, for a printed copy for crew leads. Search word found: "download". Jo Harlan decides whether to link it to FR-112.
OTHER OWNERS' ACCOUNTS
- Kit Morrow: 1 requester (R-231).
AFTER SENDING (for a person to do in the feedback tool)
- D1: mark R-201 and R-220 as updated once sent.
- D2: mark R-214 as updated once sent.
- D3: mark R-219 as updated once sent.
Drafts for Jo Harlan's approval. Nothing has been sent and no record has been changed.
Where it fits
- Customer success and account management, where the account owner closes the loop with the customers they look after.
- Product management, which confirms what shipped, what is still open and what may be shared.
- Software technology, where feature requests are tracked against a product and customers watch for what changes.
- Professional services, where clients ask for changes to a portal, a report or a way of working.
- Marketing and advertising, where an agency's clients ask for changes to reporting and dashboards.
- Growth & scaling, when requests outnumber the account owner's memory of who asked for what.
- Established businesses, where a long feedback backlog has customers who have never heard back.
It sits between two other capabilities. Customer feedback themes finds what customers keep asking for; Customer satisfaction detractor follow-up follows up low scores. This one answers each person who asked once a change or decision lands.
What has to change for your company
- Your columns. Map your feedback tool's and contact list's headers to the defaults once; the capability stops and asks when a header does not match.
- The change record. Agree who on the product or service team fills it in and confirms it, and where it is kept.
- Your status words, if you already use others with customers.
- The words that hold a request for the account owner, such as your own terms for escalations.
- Channels and tone. Message lengths, sign-off, and whether two people at one account get one combined update.
- Your platform. It runs in ChatGPT, Claude, Copilot or Gemini, from files you supply; it needs no connection to your feedback tool.
What has been checked
Fully Powered AI wrote this capability template from its own published map of the work. It was editorially reviewed on 10 November 2026. It was tried on its invented example in Claude on 10 November 2026 in two runs; the record of the second, made on the instructions as revised after the first, 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 a change your team shipped recently, with hard cases written in advance: a person who asked twice, a customer who has opted out, a request tied to a renewal, an internal target date in the record, an export with a renamed column. The account owner checks every draft against the change record before anyone relies on it. Pilot acceptance-test preparation builds that test set, and What we test before we call an AI workflow ready shows the record.
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: