Intent boundary: This guide owns controlled evaluation intent. The GorillaDesk review owns commercial fit, current plan signals, and buying questions. Official documentation establishes what to test; only observed evidence on the intended plan, devices, roles, and region can establish whether it passes.
one synthetic recurring route survives an urgent insert, field completion, invoice correction, and export without duplicate or unexplained work
The process succeeds only when the team can explain the result, recover from exceptions, and retain evidence.
The control sequence
Freeze the purchased boundary
Record Basic, Pro, or Growth; routes or schedules; users; devices; country; taxes; payments; messaging; QuickBooks; documents; GPS options; AI; and every temporary trial entitlement. Do not test an all-feature environment and assume the lower paid plan behaves the same.
Build a representative recurring route
Create five synthetic customers with service windows, site notes, different durations, recurring frequencies, material requirements, and one restricted-access property. Generate the next occurrences and verify ownership, instructions, and billing rules.
Break the route on purpose
Insert an urgent job, cancel one stop, delay another for weather, and reassign a technician. Record route order, office effort, customer messages, field updates, and whether any appointment is duplicated or orphaned.
Test office and technician boundaries
Use the actual desktop and mobile roles. Verify that the office can see the necessary map and schedule information while a restricted technician sees only assigned work and cannot cross financial, reporting, subscription, or location-history boundaries.
Complete the field evidence
On each intended mobile platform, open the assigned stop, add time, notes, photos, materials or chemicals, a signature or document where required, and completion status. Repeat the critical sequence under weak connectivity and document recovery behavior.
Invoice the recurrence and correct it
Create an unsent invoice from synthetic work, verify tax, subscription or recurring-billing behavior, and perform one safe correction. Use no real customer, card, payment, payout, refund, or message solely to manufacture editorial evidence.
Trace accounting and communication costs
If QuickBooks is required, reconcile object counts and totals through creation, edit, duplicate, and recovery in a controlled company. Separately count every SMS, VoIP, review, AI, payment, and advanced GPS dependency that changes steady-state cost.
Export and rehearse exit
Export customers, sites, jobs, schedules, invoices, payments, materials, documents, attachments, notes, and location or activity history where available. Reconcile identifiers and counts, then obtain retention, support-export, number-portability, cancellation, and deletion rules in writing.
Pass conditions for a GorillaDesk pilot
| Control | Pass evidence | Investigate | Reject signal |
|---|---|---|---|
| Recurring route | Occurrences, ownership, instructions, and billing remain traceable | One named manual control handles an exception | A normal exception duplicates or loses work |
| Dispatch recovery | Urgent inserts and weather changes reach office, field, and customer correctly | One notification needs a documented fallback | Route state becomes stale or irreconcilable |
| Field + permissions | Required evidence is captured and restricted actions stay denied | A bounded device or role limitation has an owner | Mandatory evidence or governance cannot be enforced |
| Finance + cost | Invoice and accounting totals reconcile with every add-on itemized | One vendor-assisted recovery is documented | Duplicates, balances, or recurring charges remain unexplained |
| Data exit | Required records, files, and identifiers are retrievable and reconciled | A written support export is required | Mandatory history or compliance evidence cannot be recovered |
Failure modes to expose
- Testing only a clean route with no urgent insert, cancellation, reassignment, or weather delay
- Comparing plan names without routes, usage charges, add-ons, and trial-only capabilities
- Treating mobile app availability as proof of weak-signal behavior
- Using an admin account to represent technician permissions
- Connecting accounting without control totals and a duplicate recovery test
- Waiting until cancellation to ask how files, history, phone assets, and payment records are exported
Worksheet questions
- 01
Which exact plan, routes, users, devices, locations, and add-ons will be purchased?
- 02
Which recurring exceptions happen in a normal week and which one is an immediate reject condition?
- 03
What must each customer, office user, and technician see after a same-day route change?
- 04
Which materials, chemicals, photos, signatures, documents, and location records are mandatory?
- 05
Which actions must work under weak connectivity on each field device?
- 06
Who owns invoice corrections, failed payments, accounting duplicates, and communication exceptions?
- 07
What is the steady-state monthly cost at expected route and message volume?
- 08
Which records and files must remain retrievable after cancellation?