Workflow template for customer success and account management
Customer journey ending review
When a customer's journey ends on a sour note, your customer experience lead gets one review built from the records: whether the work was really finished at the final handoff, each difficult moment with its dates, the customer's own words, and follow-up options. The customer success lead chooses what to change.
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 last weeks of a journey are often what a customer remembers and tells others about. This review takes one ending (an offboarding, a cancellation, a project close, a delivery, an onboarding milestone) and reads it from the records rather than from memory.
It starts with the ending itself. It checks the final handoff against what "done" meant for that customer, so a warm closing email never passes for finished work: if anything was still open, the review says so plainly and names the message that called the work complete. Then it walks back through the journey and finds the moments that were hard on the customer, from facts in the log: a question that waited too long for an answer, a customer who had to ask twice, a promised date that slipped, a long stretch with no word from the team. Each moment carries its dates and the number of days involved.
What the customer said is quoted exactly. What the customer may have felt is offered only as a reading, with the question or record that would confirm it. The review closes with options in three kinds: what could still be done for this customer, changes to test in the journey for the customers who come next, each with a count that would show whether it helped, and gaps in the records worth closing.
The customer success lead chooses which change to test and whether anyone contacts the customer. The AI assistant contacts no one, offers no money, judges no member of staff and changes no record.
Who starts the work, and when
The customer experience lead or a customer success manager starts it after a journey's last planned handoff, when the ending deserves a closer look: a low close survey score, an unhappy exit comment, a complaint in the final weeks, a handoff that slipped, or a regular look at a few recent endings. It covers one customer's journey per run. The customer success lead reads the result and decides what happens next.
What they supply
- A short review brief: the customer, the kind of journey, its start date, which logged item was the final handoff, the reason for the review, any limits on contacting the customer, and a few settings with defaults included.
- The completion criteria: what "done" meant for this journey, with the status of each at the end, the item that shows it and its owner.
- The journey log: an export of the messages, calls, meetings, deliveries and internal notes, with the thread, stage, direction and owner of each, plus any date the team promised.
- The customer feedback: survey scores, exit comments, emails and call notes about the journey.
Each export has default column headers. When a header does not match, the review stops and asks which column is which.
What comes out
One review in a fixed order:
- How it ended: the final handoff, a plain verdict on whether the work was finished and every question answered, each criterion with its evidence, any closing words that ran ahead of the work, low scores, and what has happened since.
- Difficult moments, in date order, each with the facts, the dates and the days, and whether it touches unfinished work or the customer's feedback.
- The moments to look at first, up to three, chosen by a fixed rule, with the moment nearer the ending first when two are level.
- In the customer's words, quoted exactly, with call notes labelled as the note-taker's.
- Readings to confirm, each with what would confirm or rule it out.
- Follow-up options for this customer, changes to test in the journey, and changes to the records.
- Decisions for the customer success lead, with "none" wherever one does not arise.
It reviews one journey after it ends. To answer a customer asking to leave today, use Cancellation request response; to read the pattern across everyone who left in a quarter, use Churn risk and save plan; to check a deliverable before it is handed over, use Project handover readiness check.
An invented example
Illustrative example with invented data. Company A, Customer B, the people, the records and the dates below are all invented. Company A is an invented 30-person digital agency that builds online stores for small retailers and hands each one over at the end of the project. Customer B, an invented home-goods retailer, gave the close survey 5 out of 10. Noor Ellery, Company A's customer experience lead, supplied the inputs below in full on Wednesday 11 November 2026; the review the workflow template returned comes after them.
The inputs
1. The review brief
Customer: Customer B
Journey type: project close (a new online store, built and handed over)
Journey start: 2026-09-01
Final handoff: E19
Review date: 2026-11-11
Review owner: Noor Ellery, customer experience lead
Decision by: customer success lead
Reason for review: Customer B scored the close survey 5 out of 10.
Contact limits: none
Settings: (left blank: use the defaults)
2. The completion criteria
criterion_id,criterion,status_at_end,evidence_event,owner
C1,Store live on the customer's own domain,met,E14,Project manager
C2,Product catalogue imported and checked by the customer,met,E12,Project manager
C3,Payment and delivery settings tested with a live order,partly met,E16,Developer
C4,Two of the customer's staff trained to add products and process orders,met,E19,Project manager
C5,Admin guide delivered,met,E22,Project manager
C6,Support contact and hours confirmed to the customer in writing,not recorded,,Customer success manager
3. The journey log (exported from the project tool and the shared inbox)
event_id,date,thread,stage,channel,direction,owner,summary,criterion,due_date,fulfils
E01,2026-09-01,T1,Kickoff,video call,to customer,Project manager,"Kickoff call: scope agreed; launch planned for 9 October",,,
E02,2026-09-03,T2,Build,email,from customer,Project manager,"Sends the product spreadsheet; asks when he will see the first designs",C2,,
E03,2026-09-04,T2,Build,email,to customer,Project manager,"Says the first designs will be shared by 11 September",,2026-09-11,
E04,2026-09-14,T2,Build,email,to customer,Designer,"Shares the first designs for comment",,,E03
E05,2026-09-15,T2,Build,email,from customer,Designer,"Approves the designs with two changes",,,
E06,2026-09-16,T2,Build,email,to customer,Designer,"Confirms the two changes are made",,,
E07,2026-09-24,T3,Build,email,from customer,Project manager,"Asks whether the launch is still 9 October",,,
E08,2026-09-29,T3,Build,email,from customer,Project manager,"Asks again about the launch date; says a promotion is booked for the weekend of 10 October",,,
E09,2026-10-01,T3,Build,phone call,to customer,Project manager,"Call: the launch moves to 16 October because the catalogue import needs fixing",C2,,
E10,2026-10-01,T3,Build,internal note,internal,Project manager,"Catalogue import: 140 products missing prices; developer to fix",C2,,
E11,2026-10-02,T4,Launch,email,to customer,Project manager,"Sends the fixed catalogue and asks the customer to check it",C2,,
E12,2026-10-08,T4,Launch,email,from customer,Project manager,"Catalogue checked and approved",C2,,
E13,2026-10-09,T4,Launch,email,to customer,Project manager,"Confirms launch on 16 October; says a test order will be placed by 15 October",C3,2026-10-15,
E14,2026-10-16,T4,Launch,email,to customer,Project manager,"The store is live on the customer's domain",C1,,
E15,2026-10-17,T5,Launch,email,from customer,Project manager,"Two shoppers report that the delivery charge shows as zero at checkout",C3,,
E16,2026-10-20,T5,Launch,email,to customer,Developer,"Standard delivery charge fixed and a test order placed; express delivery still shows zero",C3,,E13
E17,2026-10-21,T5,Launch,email,from customer,Developer,"Asks when express delivery will be fixed",C3,,
E18,2026-10-22,T6,Handover,email,to customer,Customer success manager,"Invites the customer to the handover call on 23 October",,,
E19,2026-10-23,T6,Handover,video call,to customer,Project manager,"Handover call: two staff trained; project marked closed; admin guide to follow",C4,2026-10-26,
E20,2026-10-23,T6,Handover,email,to customer,Customer success manager,"Thank-you note: the project is complete; link to the close survey",,,
E21,2026-10-27,T5,Handover,email,from customer,Customer success manager,"Express delivery still shows zero; asks who to contact now the project is closed",C3,,
E22,2026-10-29,T7,Handover,email,to customer,Project manager,"Sends the admin guide",C5,,E19
4. The customer feedback
feedback_id,date,source,person,score,scale,refers_to,text
F1,2026-10-26,survey,"Tomas Reade, owner, Customer B",5,0 to 10,,"The store looks great and the training was clear. But we lost our promotion weekend when the launch moved, and nobody has told us when express delivery will work."
F2,2026-10-01,call note,"Tomas Reade, owner, Customer B",,,E09,"Not happy that the launch moved after the promotion was booked. Asked why he was not told sooner."
The output
JOURNEY ENDING REVIEW: Customer B, project close
For: Noor Ellery, customer experience lead. Decision by: customer success lead. Prepared 11 November 2026 from: brief; completion criteria (6); journey log (22 rows: 20 in the window, 2 after the end, 0 before the start, left out); feedback (2 items). Reason for review: Customer B scored the close survey 5 out of 10. Settings: reply target 2 days; silence limit 10 days; low score 6 or below on 0 to 10, 2 or below on 1 to 5; changes measured on the next 5 journeys. Defaults used: all four settings. Contact limits: none.
HOW IT ENDED
- Final handoff: E19, 23 October 2026, video call, Project manager: Handover call: two staff trained; project marked closed; admin guide to follow.
- Ending: Ended with work open and a question unanswered.
- Criteria: 3 met by the handoff; 3 open at the handoff; 2 still open on 11 November 2026.
- C1 Store live on the customer's own domain: met by the handoff, E14 on 16 October 2026. Owner: Project manager.
- C2 Product catalogue imported and checked by the customer: met by the handoff, E12 on 8 October 2026. Owner: Project manager.
- C3 Payment and delivery settings tested with a live order: partly met, E16 on 20 October 2026: standard delivery charge fixed and a test order placed; express delivery still shows zero. Owner: Developer.
- C4 Two of the customer's staff trained to add products and process orders: met by the handoff, E19 on 23 October 2026. Owner: Project manager.
- C5 Admin guide delivered: met after the handoff, E22 on 29 October 2026. Owner: Project manager.
- C6 Support contact and hours confirmed to the customer in writing: not recorded. Owner: Customer success manager.
- Questions unanswered at the handoff: E17, 21 October 2026.
- Closing words against open work: E19, 23 October 2026: Handover call: two staff trained; project marked closed; admin guide to follow, while C3, C5 and C6 were open. E20, 23 October 2026: Thank-you note: the project is complete; link to the close survey, while C3, C5 and C6 were open.
- Low scores: F1, 5 on 0 to 10, cut-off 6 or below.
- After the end: E21, 27 October 2026, from customer: Express delivery still shows zero; asks who to contact now the project is closed; unanswered. E22, 29 October 2026, to customer: Sends the admin guide.
DIFFICULT MOMENTS (4), in date order
- M1. 4 September to 14 September 2026, Build. Missed date: E03 said the first designs would be shared by 11 September; E04 shared them on 14 September, 3 days late. Open criterion: none. Named in feedback: none. Proposed link: none.
- M2. 16 September to 1 October 2026, Build. Silence: no item to the customer from E06 (16 September) to E09 (1 October), 15 days. Slow reply: E07 (24 September) answered by E09 (1 October), 7 days, 5 over the target. Asked again: E08 (29 September), with no item to the customer since E07; answered by E09 in 2 days. Open criterion: none. Named in feedback: F2. Proposed link: F1, "the launch" (E09, "the launch moves"), "promotion" and "weekend" (E08, "a promotion is booked for the weekend").
- M3. 9 October to 27 October 2026, Launch and Handover. Missed date: E13 said a test order would be placed by 15 October; E16 placed it on 20 October, 5 days late. Slow reply: E15 (17 October) answered by E16 (20 October), 3 days, 1 over the target. Unanswered: E17 (21 October), 21 days open on 11 November. Asked again: E21 (27 October), with no item to the customer since E17; unanswered, 15 days open on 11 November. Open criterion: C3. Named in feedback: none. Proposed link: F1, "express delivery" (E16, E17, E21). After the end: E21.
- M4. 23 October to 29 October 2026, Handover. Missed date: E19 said the admin guide would follow, due 26 October; E22 sent it on 29 October, 3 days late. Open criterion: none. Named in feedback: none. Proposed link: none. After the end: E22.
MOMENTS TO LOOK AT FIRST
- M3, placed by rule (a): it touches C3, still open.
- M2, placed by rule (b): F2 refers to E09.
- M4, placed by rule (d): 3 days late, level with M1, and nearer to the final handoff.
IN THE CUSTOMER'S WORDS
- F2, 1 October 2026, call note, Tomas Reade, owner, Customer B, the note-taker's words: Not happy that the launch moved after the promotion was booked. Asked why he was not told sooner. Link: E09.
- F1, 26 October 2026, survey, Tomas Reade, owner, Customer B, score 5 on 0 to 10: "The store looks great and the training was clear. But we lost our promotion weekend when the launch moved, and nobody has told us when express delivery will work." Link: proposed link to M2, "the launch", "promotion", "weekend"; proposed link to M3, "express delivery".
READINGS, TO CONFIRM
- M3: The records are consistent with the customer leaving the project without knowing who owns the express delivery problem: E17 asked when it would be fixed and had no reply, E19 and E20 described the project as closed and complete two days later, and E21 asks who to contact now. Rests on: E17, E19, E20, E21, F1. To confirm: ask the customer whether express delivery still shows zero at checkout and whether they know who supports the store now.
- M2: The records are consistent with the customer hearing of the launch delay only after asking twice, once a promotion had been booked: E07 and E08 asked about the date, E08 names the promotion, and the new date came in the call E09 on 1 October; the earliest records of the import problem in the log are E09 ("because the catalogue import needs fixing") and the internal note E10, both dated 1 October. Rests on: E07, E08, E09, E10, F1, F2. To confirm: check in the project tool when the catalogue import problem was first found.
- M4: The records are consistent with the admin guide reaching the customer six days after the handover call: E19 said it would follow by 26 October, and E22 sent it on 29 October. Rests on: E19, E22. To confirm: ask the two staff whether they needed the guide in the week after the handover call.
FOLLOW-UP OPTIONS (for the customer success lead to choose; none is recommended)
For this customer:
- O1. Finish C3: express delivery still shows zero at checkout (E16), and E16 records a test order for standard delivery only. Rests on: C3, E16, E17, E21. Owner if chosen: Developer.
- O2. Finish C6: no written confirmation of the support contact and hours is recorded. Rests on: C6, E21. Owner if chosen: Customer success manager.
- O3. Reply on T5 to E17 and E21: where express delivery stands and who supports the store now the project is closed. Rests on: E17, E21. Owner if chosen: Customer success manager.
Changes to test in the journey (proposed, untested):
- O4. At Handover: before the handover call, every customer question still open on a thread is given to a named owner, and the customer is told who that is. Rests on: M3. How you would know: items from the customer still unanswered on the final handoff date, from the journey log, over the next 5 journeys of this type. Owner if chosen: owner to choose.
- O5. At Build: when the launch date is at risk, the customer is told on the day the risk is first recorded, before they ask. Rests on: M2. How you would know: items from the customer asking about the launch date before a change to it was announced, from the journey log, over the next 5 journeys of this type. Owner if chosen: owner to choose.
- O6. At Handover: the admin guide is sent before or during the handover call, not after it. Rests on: M4. How you would know: days between the final handoff and the admin guide's evidence item, from the completion criteria and the journey log, over the next 5 journeys of this type. Owner if chosen: owner to choose.
- O7. At Handover: the project is called closed, and the thank-you note sent, only once every completion criterion is met; until then the customer hears what is still open and who owns it. Rests on: the ending (E19, E20; C3, C5, C6). How you would know: criteria open at the final handoff, from the completion criteria, over the next 5 journeys of this type. Owner if chosen: owner to choose.
For the records:
- O8. C6 is "not recorded": record each criterion's status at the handoff with the logged item that shows it. Rests on: C6.
- O9. F1 has no refers_to: link each close survey comment to the stage or item it is about when it arrives. Rests on: F1.
NOT CHECKED
Nothing.
DECISIONS FOR THE CUSTOMER SUCCESS LEAD
- Which change, if any, to test, and with which journeys: O4, O5, O6, O7.
- Work still open: C3, who finishes it and whether the customer is told; C6, who finishes it and whether the customer is told.
- Unanswered items: T5 (E17, E21), whether a person replies now, and who.
- Losses the customer names: F1, "we lost our promotion weekend": whether and how to acknowledge it; no amount is proposed.
- Records changes: O8, O9, whether to adopt.
- Referrals: none.
Review for Noor Ellery and the customer success lead. Nothing has been sent, no customer has been contacted and no record has been changed.
Where it fits
- Customer success and account management, where the customer experience owner looks after how customers are treated from the first week to the last.
- Project and delivery, where a project's close and final delivery are the handoff the customer judges the whole project by.
- Software technology, where offboarding a customer at the end of a contract or plan is the last impression of the product and the team.
- Professional services, where an engagement's close, the final deliverable and the last invoice decide whether a client comes back or refers others.
- Marketing and advertising, where an agency hands over a site, a campaign or an account and the client remembers how that handover felt.
- Established businesses, where long-standing customers expect a good ending, and a poor one travels.
- Growth & scaling, when more journeys are ending each month than the customer experience lead can follow by hand.
What has to change for your company
- Your completion criteria. Write down what "done" means for each kind of journey before it starts; the review reads the ending against them.
- Your columns. Map your CRM, help desk or project tool headers to the defaults once.
- One thread per topic in the log, so separate problems stay separate moments.
- Your settings: how many days a reply may take, how long a quiet spell may run, what counts as a low score, and how many journeys a change is measured on.
- Who handles refunds, chargebacks and formal complaints, so the review refers those to the right role and leaves them alone.
- Your platform. It runs in ChatGPT, Claude, Copilot or Gemini, from files you supply; it needs no connection to your systems.
What has been checked
Fully Powered AI wrote this workflow template from its own published map of the work. It was editorially reviewed on 11 November 2026. It was tried once on its invented example in Claude on 11 November 2026, and the record of that run is published with it. Afterwards the wording of the instructions was clarified on several points the run raised, and the example was edited to drop one link that the instructions did not support and one phrase that went beyond the records; it was not run again after those edits. 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 two or three endings your team remembers well, with hard cases written in advance: a closing message sent while work was open, a customer who asked twice, a call note that sounds like the customer's words, a feedback comment asking for a refund, an export with a renamed column. The review owner recomputes every day count from the log before anyone relies on the review. Pilot acceptance-test preparation builds that test set, and What we test before we call an AI workflow ready shows the record.
Who decides
Your people keep
- Which change to test
- Whether anyone contacts the customer
It does not
- Contacts no one
- Offers no money
- Judges no member of staff
- Changes no record
Questions people ask
Who is it for?
The customer experience lead or a customer success manager starts it after a journey's last planned handoff. The customer success lead reads the result and decides what happens next.
What do I need to supply?
A short review brief, the completion criteria, the journey log and the customer feedback.
What does it not do?
The AI assistant contacts no one, offers no money, judges no member of staff and changes no record.
Can a polite closing email count as a finished handoff?
No. It checks the final handoff against what done meant for that customer, so a warm closing email never passes for finished work.
What has been checked?
It was editorially reviewed on 11 November 2026. It was tried once on its invented example in Claude on 11 November 2026, then the instructions were clarified and the example edited, and it was not run again. It has not yet been tested in a client environment.
The full workflow template
Everything above is the outline. The complete workflow 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 workflow template 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 workflow 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: