Repair work disappears
Scheduled revenue continues while callout and ad-hoc repair invoices fall to zero at the same site.
Equipment maintenance
Flat contract billing can hide a valuable change at one site: callouts and ad-hoc repairs have gone elsewhere. ChurnRisk separates those revenue lines and puts the open service history beside them.
Site and agreement level warnings, with a low confidence ceiling until field-service data is connected.
How the work repeats
Scheduled maintenance follows an agreement and renewal date. Callouts follow the assets and whatever breaks. A multi-site client can keep the main agreement while quietly testing another contractor for repair work at one facility.
The loss appears first in the split. Contract revenue stays flat, ad-hoc repair revenue reaches zero, and response-time complaints sit unresolved near the renewal date.
Useful changes
Contract, repair, site, and renewal signals remain separate.
Scheduled revenue continues while callout and ad-hoc repair invoices fall to zero at the same site.
A multi-site contract renews with fewer facilities or a narrower service scope.
A planned preventive maintenance visit passes without the expected invoice or supporting email trail.
Response-time or technician-quality complaints remain open as procurement starts asking for comparisons.
Warning examples
These examples are illustrative and use the maintenance pack.
The agreement renews in 47 days. Two response-time complaints remain unresolved. Ad-hoc repair revenue at this site has been zero for four months.
The client renewed with one fewer site. The removed facility still appears in recent service correspondence.
A planned preventive maintenance visit passed without an invoice. The field-service record is outside ChurnRisk and needs checking.
Illustrative warning copy. Figures and events are sample data from the industry pack.
False alarms
Operational changes can create clean-looking gaps in the ledger.
New equipment can remove the repair demand while the relationship remains sound.
A facility closure explains lost service volume and should not trigger a retention message.
Maintenance need can pause during a known production shutdown, then return on schedule.
Advance contract billing creates an apparent invoice gap even when scheduled work continues.
An open service complaint blocks renewal-pitch copy. Commercial terms stay with procurement, not the site contact.
Connector limits
This pack is capped at low confidence until a field-service connector exists.
QuickBooks can separate recurring contract lines from repair revenue when invoices carry the site and service type. Connected mailboxes can show response-time complaints, tender language, and facility contact changes.
ChurnRisk does not connect to work-order, field-service, or asset management platforms today. Technician conversations that stay on site or by phone are also invisible.
Missing work-order data caps confidence at 40%. Missing asset-management data caps it at 45%, and technician conversations outside email cap it at 50%. A confident-looking invoice pattern cannot override those ceilings.
Read the current connection boundaries for QuickBooks and Gmail or Outlook. The How It Works page explains how missing data becomes an unknown instead of a healthy reading.
Monday workflow
A call comes after the service record is checked.
Compare agreement billing with callout and repair work for the same facility.
Confirm whether equipment was replaced, decommissioned, or covered by a planned shutdown.
Bring response time, repeat-fault callbacks, and the renewal date onto the same review.
Route service recovery to the facility contact and commercial questions to procurement. A person places the call.
See the full product workflow, including evidence, confidence, and approval before any customer contact.
Related industries
For site contracts where scope and service credits change the monthly bill.
For managed agreements where the service system sets a strict confidence ceiling.
Compare plans on Pricing, or use the demo to test one account with labeled sample data.
Start with your agreement and repair lines, or walk through one renewal where the field-service record still needs a human check.
There is no field-service connector today. The page keeps that limitation visible on every affected warning.