Intent boundary: This is a controlled test protocol, not a claim that Service Autopilot passed. Official sources establish the documented plan and workflow boundaries, while ServiceTech Signal has not completed a direct account run. Record every result as observed, vendor documented, blocked by plan, quote, market, role, device, or account, or not tested. Do not publish a numerical score from desk evidence.
one synthetic recurring route survives a weather delay, urgent insert, skipped visit, crew handoff, billing correction, automation failure, and complete exit without unexplained or duplicate work
The process succeeds only when the team can explain the result, recover from exceptions, and retain evidence.
The control sequence
Freeze the purchased and regional boundary
Record Startup, Pro, Pro Plus, or Elite; annual term; signup fee; administrative and mobile licenses; locations; devices; payments; messages; maps; Client Portal; QuickBooks; Automations; Marketplace; training; onboarding; and every temporary trial entitlement. Confirm regional availability and do not use a higher-tier demo to represent the paid configuration.
Build one representative master schedule
Create only fictional customers and properties with weekly, biweekly, seasonal, and one-time work, including service windows, access instructions, duration, crew skill, material need, tax and billing rules. Generate the next occurrences and reconcile customer, property, route, job, appointment, and invoice scope before changing anything.
Break the recurring route deliberately
Delay one stop for weather, skip one visit, insert urgent work, move a time window, and reassign a crew member. Record route order, travel assumptions, office effort, customer communication state, mobile updates, recurrence, and billing after each exception. A shorter-looking route is not proof of optimization.
Prove the crew and permission boundary
Use the intended office and Team App roles on every supported device. Verify assignments, notes, comments, notifications, before-and-after photos, map or location controls, time, materials, completion, price visibility, customer history, reports, settings, and cross-location access. Repeat critical reads and writes under weak connectivity.
Complete and correct the financial chain
Create an unsent estimate and invoice from synthetic completed work, verify service, tax, discount, deposit, recurring charge, balance, and job-costing scope, then make one safe correction. Do not contact a real customer or use a real card, bank, payout, refund, or financing request solely to manufacture evidence.
Break one automation without repeating the customer action
Define one bounded trigger, consent state, stop condition, owner, retry rule, and human override. Create a reversible failure and verify run visibility, alerts, duplicate prevention, recovery, and whether a retry repeats a message, task, route change, invoice, or customer record.
Reconcile accounting and total cost
If QuickBooks is required, use a controlled company to trace one customer, invoice, payment-state, correction, rejected record, duplicate-prone retry, and final balance. Separately itemize the plan, signup fee, licenses, messaging, portal, maps, payments, Marketplace products, implementation, training, support, taxes, and renewal.
Export before commitment
Export customers, leads, properties, master schedules, routes, jobs, appointments, estimates, invoices, payments, expenses, files, photos, forms, communications, users, permissions, reports, automation history, and configuration where available. Reconcile counts and identifiers, then obtain support-assisted export, retention, cancellation, recovery, and post-termination access rules in writing.
Pass conditions for a Service Autopilot recurring-service pilot
| Control | Pass evidence | Investigate | Reject signal |
|---|---|---|---|
| Recurrence + identity | Every occurrence remains attached to the correct customer, property, service, route, and billing rule | One documented manual review owns a bounded exception | Normal changes multiply, orphan, or silently lose recurring work |
| Route exception | Weather, skipped work, urgent inserts, and reassignment remain explainable across office, crew, customer, and billing state | One route decision needs a named dispatcher | An ordinary exception creates stale, duplicate, or unbillable work |
| Crew + permissions | Required field evidence synchronizes and restricted data stays restricted | A known device or role gap has a tested fallback | Mandatory evidence is lost or a restricted user crosses a critical boundary |
| Automation + finance | Failure and retry remain visible, owned, non-duplicative, and financially reconcilable | One support-assisted recovery is written and timed | Retry repeats a customer action or leaves an unexplained balance |
| Cost + exit | The written quote is complete and required records remain usable outside the platform | One quoted cost or assisted export has an accountable owner | Renewal cost or mandatory operating and audit data cannot be established |
Failure modes to expose
- Testing a clean route without weather, skipped work, urgent insertion, reassignment, or billing correction
- Treating a map sequence or vendor efficiency claim as measured route optimization
- Using the all-feature trial or demo to represent Startup, Pro, Pro Plus, or Elite without recording entitlements
- Assuming messaging, Client Portal, QuickBooks, Smart Maps, payments, training, licenses, or onboarding are included without an itemized quote
- Using an administrator account to represent technician, dispatcher, manager, customer, or multi-location permissions
- Calling one successful automation reliable without a failure, stop rule, visible owner, safe retry, and human override
- Connecting accounting without control totals, edit ownership, duplicate recovery, and a zero-difference reconciliation
- Exporting a report while omitting relationships, files, photos, communications, users, permissions, automation history, configuration, and post-cancellation access
Worksheet questions
- 01
Which exact plan, annual term, signup fee, licenses, add-ons, trial entitlements, locations, devices, and regions are being tested?
- 02
Which identifiers keep a customer, property, service, occurrence, route stop, job, appointment, estimate, invoice, and accounting record unique?
- 03
Which recurring exceptions happen in a normal week, and which result removes the product from the shortlist?
- 04
What must the customer, dispatcher, manager, and crew member each see after a weather delay, skipped visit, urgent insert, or reassignment?
- 05
Which mobile actions and evidence must survive weak connectivity on every intended device?
- 06
Who owns failed automation, duplicate review, invoice correction, rejected accounting records, and customer communication?
- 07
What is the normalized first-year and renewal cost at the expected users, routes, messages, payments, locations, and support level?
- 08
Which records, relationships, files, history, configuration, and access must remain recoverable before and after cancellation?