Capability template for customer support and service
Returned unit review brief
When a failed-unit report or return request arrives, the service coordinator gets one brief tying the customer's report to each unit's shipment record, serial and recorded configuration, with unmatched serials and missing evidence listed. It names no cause.
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
A customer writes that three units have stopped working and wants them replaced. Before anyone can decide what happens, someone has to find out which units those are, what was shipped, how each was configured and what the customer has not yet told you. This capability template does that reading. It takes the report, your shipment records, your recorded configuration and your support policy, and puts them in one brief.
Each serial the customer quotes is matched to the shipment record only when it is identical. A serial that is one character away from a record is listed as a possible match and never chosen for you. For every matched unit the brief shows the product, revision, ship date, order and the configuration on file, the days since it shipped against the period your policy states, and anything recorded after shipment. Changes the customer mentions, such as a part swapped, are listed as reported. The evidence your policy asks for is checked off unit by unit, and what is missing is listed.
Any mention of heat, a burning smell, smoke, swelling or injury goes to the top of the brief with the specialist your policy names, before anything else. The brief identifies no fault, says nothing about whether a unit meets its specification and recommends no handling. For a case already with engineering, use field issue handoff to engineering; for a complaint or refund request on its own, complaint and refund request handling; to record a nonconformity, nonconformity record draft.
Who starts the work, and when
A service coordinator starts it when a failed-unit report or a return request reaches service, and runs it again when the customer sends more evidence. Service and quality decide the handling, engineering reviews any technical concern and finance approves any credit.
What they supply
- The customer's report or return request, pasted as received, with its reference and date.
- The shipment records, one row per serial.
- The configuration records, with the date each entry was recorded.
- The earlier ticket history for the serials concerned, if you have it.
- Your support policy: the stated period, the evidence it asks for, and who decides what.
- Their settings: the date of the brief and the names of the roles.
What comes out
One brief in a fixed order: a safety referral if the report mentions one, what the customer reports and asks for, the match of each serial, each matched unit's shipment and configuration record, changes after shipment and reported modifications, earlier history, the evidence found and missing, unmatched serials, conflicts, the decisions each role is asked to make, and questions for the coordinator. Every empty section says so.
An invented example
Illustrative example with invented data. The company, its customer, its products and every serial, date and figure below are invented. Company X is an invented 40-person business that makes wireless environmental sensor nodes and a hub. Dana is its service coordinator. On Monday 9 November 2026 a return request arrives from Customer A, and the service coordinator runs the capability template on it.
The inputs come first, in full, so the template can be run on them. The brief follows.
The inputs
The date of the brief and the settings
Brief date: 2026-11-09
Service coordinator: Dana
Safety referral: product safety officer
Handling decided by: service lead and quality lead
Technical concerns: hardware engineering
Credit approved by: finance controller
The return request
Reference: RR-0318
Received: 2026-11-09
Customer: Customer A
Contact: A-1
Serials quoted: SN-40217, SN-40219, SN-40233
Attachments: photo of the label on SN-40217; photo of the hub status screen
Request: "Three of our sensor nodes stopped reporting to the hub over the weekend. The status light is solid red on two and blinking on the third. We want them replaced and a credit for the downtime. We swapped the battery pack on SN-40219 last month. One of the nodes smelled hot when we unplugged it."
The shipment records
Serial,Product,Revision,Ship date,Order,Customer,Ship-to,Price
SN-40217,Node N2,Rev C,2026-03-04,ORD-5521,Customer A,Site 1,129.00
SN-40219,Node N2,Rev C,2026-03-04,ORD-5521,Customer A,Site 1,129.00
SN-40223,Node N2,Rev C,2026-03-04,ORD-5521,Customer A,Site 2,129.00
SN-40231,Node N2,Rev D,2026-06-17,ORD-6012,Customer A,Site 3,129.00
The configuration records
Serial,Field,Value,Recorded on,Source
SN-40217,Firmware,2.4.1,2026-03-03,Factory
SN-40217,Radio module,RM-9,2026-03-03,Factory
SN-40217,Battery pack,BP-3,2026-03-03,Factory
SN-40219,Firmware,2.4.1,2026-03-03,Factory
SN-40219,Radio module,RM-9,2026-03-03,Factory
SN-40219,Battery pack,BP-3,2026-03-03,Factory
SN-40219,Firmware,2.5.0,2026-08-12,Remote update
SN-40223,Firmware,2.4.1,2026-03-03,Factory
SN-40231,Firmware,2.5.0,2026-06-16,Factory
The earlier ticket history
Reference,Date,Serial,Entry
T-1190,2026-08-20,SN-40217,"Customer reported the node dropped off the hub for a day; customer restarted it; reported working again."
T-1244,2026-10-02,SN-40219,"Customer asked how to change the battery pack; public guide sent."
The support policy
Stated period: 365 days from ship date.
Evidence before a unit is reviewed:
1. Photo of the serial label
2. Status indicator state
3. Date first seen
4. What the unit was connected to
5. Firmware version shown on the hub
6. Whether anyone has opened or repaired the unit
7. Photos of visible damage
The brief
RETURNED UNIT REVIEW BRIEF: RR-0318, Customer A
Prepared for: Dana, service coordinator. Brief date: 2026-11-09. Report received: 2026-11-09.
Internal. No fault has been identified, no handling chosen and no credit proposed.
Nothing has been sent to the customer.
SAFETY REFERRAL
The report says: "One of the nodes smelled hot when we unplugged it." Refer to the product safety officer before any other step. The unit is not named in the report. The brief gives no view on this.
THE REPORT
Contact A-1, received 2026-11-09. Units quoted: 3 (SN-40217, SN-40219, SN-40233).
Reported by the customer: the three nodes stopped reporting to the hub "over the weekend"; the status light is solid red on two and blinking on the third (units not named).
Asked for: replacement of the three units; a credit for the downtime (no amount or basis stated).
Attachments named: photo of the label on SN-40217; photo of the hub status screen (contents not read).
UNIT MATCH
SN-40217: matched.
SN-40219: matched.
SN-40233: not matched, no shipment record with this serial.
SHIPMENT AND CONFIGURATION
SN-40217: Node N2, Rev C. Shipped 2026-03-04, order ORD-5521, Site 1, price 129.00. 250 days since shipment; stated period 365 days from ship date; 115 days left of it.
Configuration on file at shipment: Firmware 2.4.1; Radio module RM-9; Battery pack BP-3 (all recorded 2026-03-03, Factory).
Recorded after shipment: none.
SN-40219: Node N2, Rev C. Shipped 2026-03-04, order ORD-5521, Site 1, price 129.00. 250 days since shipment; stated period 365 days from ship date; 115 days left of it.
Configuration on file at shipment: Firmware 2.4.1; Radio module RM-9; Battery pack BP-3 (all recorded 2026-03-03, Factory).
Recorded after shipment: Firmware 2.5.0, recorded 2026-08-12 (161 days after shipment), Remote update.
The stated period is shown as a count of days. Service and quality decide what it means for handling.
CHANGED OR MODIFIED
Reported by the customer: SN-40219, battery pack swapped by the customer "last month" (no date or part number given). The record still shows Battery pack BP-3 as shipped.
Recorded after shipment: SN-40219, firmware 2.4.1 to 2.5.0 on 2026-08-12, Remote update.
Nothing is said about whether either is related to the report.
EARLIER HISTORY
SN-40217: 1 earlier entry. T-1190, 2026-08-20 (81 days ago): dropped off the hub for a day, restarted by the customer, reported working again.
SN-40219: 1 earlier entry. T-1244, 2026-10-02 (38 days ago): customer asked how to change the battery pack; public guide sent.
SN-40233: none, serial not matched.
EVIDENCE
Photo of the serial label: SN-40217 attachment named (photo of the label on SN-40217), contents not read; SN-40219 not supplied; SN-40233 not supplied
Status indicator state: stated, units not named (solid red on two, blinking on the third)
Date first seen: stated for all, "over the weekend"
What the unit was connected to: stated for all, "the hub"
Firmware version shown on the hub: attachment named (hub status screen), contents not read
Whether anyone has opened or repaired the unit: SN-40219 stated, the customer swapped the battery pack; SN-40217 not supplied; SN-40233 not supplied
Photos of visible damage: not supplied for any unit
Not supplied: SN-40217 2 items, SN-40219 2 items, SN-40233 3 items.
UNMATCHED SERIALS
SN-40233: no record. One character different from SN-40231 (shipped 2026-06-17, Rev D, order ORD-6012, Site 3) and from SN-40223 (shipped 2026-03-04, Rev C, order ORD-5521, Site 2). None is treated as a match.
CONFLICTS
None found.
DECISIONS FOR PEOPLE
Product safety officer: the heat mention above, first.
Service lead and quality lead: how each unit is handled. Matched: SN-40217, SN-40219. Not matched: SN-40233. Open evidence and the modification above are listed.
Hardware engineering: technical points as reported, not assessed: status light states; battery pack swap on SN-40219; firmware 2.5.0 on SN-40219 after shipment.
Finance controller: the credit asked for. No amount or basis is stated. Recorded order ORD-5521, price 129.00 each on the matched units; no figure has been calculated.
QUESTIONS FOR THE SERVICE COORDINATOR BEFORE IT GOES
1. Which unit smelled hot?
2. Which unit does the customer mean by SN-40233: SN-40231, SN-40223 or another?
3. Which two units show solid red and which blinks?
4. What are the date and part number of the battery pack fitted to SN-40219?
5. The request for a credit has no amount or basis. Who asks the customer for them?
6. Evidence not supplied: photos of visible damage for all three units; the serial label photo for SN-40219 and SN-40233; whether SN-40217 and SN-40233 have been opened or repaired. Who asks for them?
Prepared for the service coordinator.
Nothing has been sent, no record has been changed and no one has been contacted.
Where it fits
- Customer support and service, where a return request starts as a few lines from a customer.
- Quality management, where the quality owner decides handling and needs the unit's record beside the report.
- Hardware and physical technology, where each unit ships with a serial number and a recorded build.
- Manufacturing, where the plant's records say what left the dock.
- Consumer brands, where connected products come back from people who never wrote down their setup.
- Established businesses, where return handling lives in a few people's habits.
- Growth and scaling, when return requests outgrow what one coordinator can look up by hand.
What has to change for your company
Check that your exports have the default column headers listed in the template, or rename them before you run it. Put your own evidence list, period and decision roles into the policy you supply, and name the specialist who receives any possible safety concern. Decide which configuration fields matter for your products. The template assumes entries recorded on or before the ship date describe the unit as shipped. It runs in ChatGPT, Claude, Copilot or Gemini from the files you paste in; it needs no connection to any system.
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, and the record of that run is published with it. The run was not blind: the person running it had already read the example's brief and the record of an earlier run, so it shows the revised instructions reach the example's brief, not that they would on a stranger's records. It has not yet been tested in a client environment, and 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 past return your service team already knows well, plus cases written in advance: a serial one digit off, a serial that appears twice, a report that mentions heat, a header that does not match. The coordinator checks every record against the exports before anyone relies on the brief. Pilot acceptance-test preparation builds that test set.
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: