--- title: "Field Service Warranty Cost Recovery | Kylon" description: "How a field service recovery desk classes each repair job as recoverable, covered, billable or absorbed, and re-walks the quarter after every change, in one Kylon room." url: "https://kylon.io/use-cases/field-service-cost-recovery" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Field Service Cost Recovery: Repair Jobs Classified by Who Pays, Before the Quarter Closes Use Case8 min read # Field Service Cost Recovery: Repair Jobs Classified by Who Pays, Before the Quarter Closes Each repair job is charged to the manufacturer, the contract, the customer or the company. Agents walk every Pipedrive job against the Notion site pages in one Kylon room, re-walk the quarter after each change, and the desk lead approves every field. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Repair jobs, manufacturer claims and contract allowances that shift together When a quarter closes, the recovery desk decides who pays for every repair job its field crews ran: the equipment manufacturer under warranty, the service contract, the customer as billable work, or the company itself. A failed inverter still under the maker's warranty is recoverable. A tracker motor on a site whose contract covers six call-outs a quarter may be covered or billable, depending on how many call-outs came before it. Contracts are Pipedrive deals and jobs are Pipedrive activities. Each site's asset register, claim allowance and any goodwill concession sit on a Notion page. The cost recovery standard and the warranty register are in Google Drive, and the details field crews forget to log turn up in Slack. A spreadsheet tries to hold the quarter together, and it goes stale the first time the manufacturer answers. ## Who works in the room People - Recovery desk lead Posts each review request, approves every field change and note, and signs off the quarter - Warranty claims specialist Files claims with the equipment manufacturer and brings back its response - Account managers Own the service contracts, publish amendments and record goodwill concessions Agents - FinRecovery analyst Walks every in-scope job in order against its contract, its site page and the warranty register, and proposes the four recovery fields Pipedrive[Notion](https://kylon.io/integrations/notion)Google Drive - AdaNotes and close-out Drafts the claim response and close-out notes for each contract deal and checks the walk's allowance counts before approval PipedriveGoogle Drive[Slack](https://kylon.io/integrations/slack) Fin leads every recovery walk and is the room's default agent, so the desk lead's requests reach Fin without a mention. Ada works on notes and close-out. When a walk changes which jobs were not accepted in full, Fin mentions Ada in the thread with those jobs, and Ada takes the lead to draft the notes in the form the standard requires. At close-out, Fin opens a thread for Ada whose first message is the brief: the final position of every job and the list of contracts. One agent leads a thread at a time, so the walk and the notes never overlap. ## How a quarter's recovery review runs Each request comes from the desk lead in the room, and each stage ends with an approval before Pipedrive changes. ```mermaid flowchart TD request([The desk lead posts a review request]) walk["Fin classes every job from its
contract, site page and warranty"] ok1["Recovery desk lead approves
before any activity is written"] file["Warranty claims specialist files
claims with the manufacturer"] wait([Nothing is filed or noted while the
manufacturer's answer is pending]) complete["Recovery desk lead decides
the response is complete"] rewalk["Fin walks every job again from
the first, recounting allowances"] notes["Ada drafts a claim response note
on each job not accepted in full"] ok2["Recovery desk lead
approves the fields and notes"] amend([An amendment notice covers
the whole quarter]) apply["Fin applies it in the walk, leaving
deals and site pages as they are"] confirm["Account manager confirms
how the amendment reads"] close["Ada drafts a close-out note
on every contract deal"] sign["Recovery desk lead
signs off the quarter"] request --> walk --> ok1 --> file --> complete wait -.- complete complete --> rewalk --> notes --> ok2 amend --> apply --> confirm ok2 & confirm --> close --> sign class walk,rewalk,notes,apply,close agent class ok1,file,complete,ok2,confirm,sign person class request,wait,amend event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Quarter dispositions | Every in-scope job is classed as manufacturer-recoverable, contract-covered, billable or absorbed, with recoverable and billable amounts | Fin, from Pipedrive jobs, Notion site pages and the warranty register | The desk lead approves before any activity is written | | Waiting on the manufacturer | Nothing new is filed with the manufacturer and no notes go on any deal while its answer is pending | Fin and Ada hold | The desk lead decides when the response is complete | | Claim response | Every job is walked again from the top, allowance counts included, and jobs not accepted in full get a claim response note | Fin, then Ada for the notes | The desk lead approves the fields and the notes | | Contract amendment | The amendment notice is applied across the quarter, and deals and site pages are left as they are | Fin | The account manager confirms how the amendment reads | | Close-out | Every contract deal gets a close-out note, including contracts with nothing to recover or bill | Ada, checked by Fin | The desk lead signs off the quarter | A quarter's recovery review. The sites, contracts and amounts in it are illustrative. ## Why every change means walking the quarter again Recovery depends on order. A contract allows a set number of covered call-outs per quarter, and a job's class depends on how many came before it. When the manufacturer rejects a claim, that job falls back to the contract and uses an allowance slot, and a later job that looked covered can become billable. Fin walks every in-scope job again from the first, recounting the allowance as it goes, and proposes only the fields that actually change. Amendments work the same way, with one difference. When account management publishes an amendment that applies to the whole quarter, the notice itself is the authority. Fin applies it inside the walk without editing contract deals or Notion site pages, so the original terms stay on record and the amendment sits beside them in the folder. No notes are written at that step. ## What the checks catch - Nothing filed with the manufacturer and no notes written while its answer is still pending - Allowance counts recounted from the first job of the quarter on every walk, not carried over from the last one - Claim response notes on jobs not accepted in full, and nothing on claims the manufacturer accepted - An amendment applied to job fields only, with no edits to deals or site pages - A close-out note on every contract, including one with nothing to recover and nothing to bill ## What stays with people - Approving the recovery fields before any Pipedrive activity changes - Filing claims with the manufacturer and deciding whether to dispute a rejection - Granting goodwill concessions, which account managers record on the site page - Signing off the quarter's close-out ## Integrations in this workflow Kylon is not a field service or billing system and it replaces neither. It sits across Pipedrive, Notion and the desk's documents, and the room is where the work between them is coordinated. The desk lead's Pipedrive connection is shared with this room as a lasting grant, and every write Fin or Ada makes still waits for an approval in the thread. - Google Drive - [Notion](https://kylon.io/integrations/notion) - Pipedrive - [Slack](https://kylon.io/integrations/slack) - **Pipedrive** holds contracts as deals and repair jobs as activities, with the four recovery fields and the deal notes - **Notion** holds the site pages: asset register, claim allowance and any goodwill concession - **Google Drive** keeps the cost recovery standard, the warranty register, the manufacturer's response and amendment notices - **Slack** is where technicians and account managers add job details the record is missing ## Where to start Use a quarter that is already closed, so every answer can be checked. Connect Pipedrive, share the Notion site pages with the room, and write one rule into the room guidelines: every change is applied by walking the quarter again from the first job, and nothing is written to Pipedrive until the desk lead approves. > “Every contract ends the quarter with a note, even the ones where nobody owes anything.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our field service cost recovery desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Google Drive, Notion, Pipedrive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the recovery desk lead, the warranty claims specialist and the account managers. Help me invite them to this Room. 3. Build a Cost Recovery App with Job, Contract, Recovery and Status columns, one record per in-scope job. Fill it from the open Pipedrive activities and deals for the period we are reviewing. 4. Walk every job in order against its contract, its Notion site page and the warranty register in Google Drive. Propose a class and the four recovery fields for each job, recount the allowance from the first job each time, and show me the ones that need attention. 5. Draft claim response notes and close-out notes for each contract deal. Hold everything until the desk lead approves each field change and note before anything is written to Pipedrive. Flag any amendment for the account manager to confirm before it is applied. 6. Write the walk order, the approval chain and who confirms what into this Room's guideline, so every period follows the same steps. 7. After one clean period, offer to turn the opening walk into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Utility Crew Dispatch: Storm Tickets Matched to Crews and Re-Checked as Feeders Clear Storm outage tickets, crew and shift assignments, the printed board, field reports and feeder clearances run through one Kylon room. Agents work ClickUp tickets and the Airtable crew roster, and the restoration lead approves every dispatch. Energy & field servicesScheduling & dispatch ](https://kylon.io/use-cases/utility-crew-dispatch)[ ### Property Tax Appeals: The Right Parcels Filed Within Each County's Capacity Parcel triage, filing allocation, manifest review, comparable corrections and appeal letters run through one Kylon room. Agents compute each county's median and check every filing against Airtable, and the tax manager approves each change and each letter. Real estateFinance operations ](https://kylon.io/use-cases/property-tax-appeals)