Nobody shops for software by asking what happens when it stops working. The demo covers scheduling, invoicing, and the parts catalog. It does not cover the Tuesday afternoon when the owner's account won't authenticate, the technician is standing in a customer's driveway with a job half-finished, and the phone number on the vendor's contact page rings into a queue.
This is not a hypothetical failure mode and it isn't unique to any one platform. Accounts get locked by password resets, payment method expirations, staff turnover, and honest mistakes. Connectivity dies in basements, elevator shafts, steel buildings, and rural service areas. Vendors change plans, get acquired, and occasionally shut down. Any one of those events can put a small service business in the position of not being able to reach its own records.
As of August 2026, the useful framing is not "which vendor never has problems" — none of them can honestly promise that — but "how much of my business keeps functioning when this specific vendor is unreachable." That question has concrete answers, and most of them are things you can arrange before you ever need them. This guide covers the three ways access actually fails, what to ask a vendor before you sign, and the small amount of preparation that turns a bad afternoon into an inconvenience.
The three ways you lose access to your own system
They're worth separating, because the mitigations are completely different.
Account-level lockout. You can't get in, but the software is fine. Someone changed a password, the card on file expired, the owner account belongs to a person who left, or two-factor is tied to a phone number that's no longer in service. This is the most common failure and also the most preventable.
Connectivity loss. The software is fine and your account is fine, but the technician has no signal. This is a daily reality in field service rather than an exception — commercial basements, underground parking, metal warehouses, and the long stretches between towns are all places where jobs happen and bars don't exist.
Vendor-side unavailability. The platform itself is down, degraded, or has changed in a way you didn't choose. You have no control over this one at all, which is precisely why the other two are worth solving.
Notice that only the third is genuinely out of your hands, and it is also the rarest of the three for established platforms. Most of the real-world pain in this category comes from the first two, which owners can address in an afternoon.
Lockout: the single-admin problem
The most common structural weakness in a small service business is that one person is the account. The owner set it up, the owner's email is the login, the owner's phone gets the verification code, and the owner is the only one who can add users or change billing. That works perfectly until the owner is on a plane, in a hospital, or simply not answering.
The fix is boring and effective: a second full-access account held by someone you trust — a partner, a spouse in the business, a lead technician, a bookkeeper. Two things make this practical rather than theoretical:
- The platform has to not charge you for it. On per-seat pricing, a spare admin seat is a real monthly cost, which is exactly why owners skip it. Unlimited users removes the excuse — IntelliDrive OS includes unlimited users at $79/month flat, so a backup admin costs nothing.
- The second account has to be real. Shared credentials aren't a backup; they're the same single point of failure with worse accountability. Create a separate login with its own recovery contact.
While you're at it, put the billing method on a card that isn't going to expire quietly, and use a business email address for the account owner rather than a personal one, so the login survives staff changes. Owners who've been through a migration already know this instinct — it's the same discipline described in the field-service software migration guide.
Connectivity: the offline question is not optional
For a mobile trade, the phrase to interrogate on any sales call is "works offline." It gets used loosely. Sometimes it means the app opens and shows cached data. Sometimes it means you can create records and they sync later. Sometimes it means nothing at all beyond a splash screen.
What matters operationally is whether a technician can complete the transaction with no signal — build the line items, capture the signature, record the payment method, and have all of it land correctly when the connection returns. IntelliDrive OS runs as an offline-capable progressive web app and syncs on reconnect, which is the behavior a mobile trade needs; the practical mechanics are covered in offline invoicing for field service.
The honest caveat is that offline capability never covers everything. Card authorization needs a network at some point. A live inventory count on a truck across town can't refresh in a dead zone. So the working assumption should be that offline covers documentation and capture, and that anything requiring a third party — a processor, a bank — completes when you're back on the network. Ask a vendor to demonstrate that distinction rather than describing it.
Data ownership: the export test
Every vendor's marketing page says you own your data. The only version of that claim that means anything is whether you can retrieve it yourself, today, without permission.
The test is simple. Log into a trial or your current account and try to export:
- Customers — names, contact details, addresses, property or vehicle records.
- Parts catalog and stock levels — the thing that took you longest to build and would hurt most to rebuild.
- Transactions — invoices, estimates, payments, with dates and line detail.
If those come out as CSV on demand, you're in a good position. IntelliDrive OS provides CSV export on its reports, which is the mechanism that makes a monthly self-backup a five-minute habit rather than a project. If instead the answer is "contact support and we'll prepare an export," or there's a fee, or a notice period, you should weigh that heavily — not because the vendor is necessarily acting in bad faith, but because it converts your records into something you have to negotiate for.
There's a compliance dimension too. The IRS guidance on recordkeeping makes clear that electronic records satisfy the same requirements as paper ones, and the SBA's financial-management guidance treats continuous tracking of income and expenses as foundational. Both assume you can produce the records. A copy you hold yourself is the only version of that assumption you fully control. If your books are synced to accounting as well, that's a second independent copy of the money side — see the QuickBooks field-service workflow.
What to ask before you sign
Take this list to any vendor, including this one, and get the answers in an email rather than on a call.
| Ask this | A solid answer sounds like | Treat this as a warning |
|---|---|---|
| How do I reach a human, and through what channel? | Named channels you can test before signing | "Submit a ticket" with no other route |
| What if the account owner is unreachable? | Multiple admins supported at no extra cost | One owner seat, recovery only via that email |
| Can I export all my data myself, today? | Self-serve CSV on customers, stock, transactions | Export by request, by fee, or by notice period |
| Does the field app work with no connectivity? | Demonstrated live: create, sign, sync on reconnect | "It's mobile-friendly" |
| What happens to my data if I cancel? | Export window stated plainly in writing | Vague, or only in a linked terms page |
| Does support or export cost extra on my plan? | Included at the stated price | Gated behind a higher tier |
Two notes on using this table honestly. First, a vendor declining to publish an uptime guarantee is not automatically disqualifying for a small-business tool — plenty of good software serves small operators without a formal service-level agreement. What matters is whether the vendor is straight with you about it rather than implying guarantees that don't exist. Second, ask for these specifics about IntelliDrive OS too. The facts stated here — flat $79/month with unlimited users, offline-capable PWA that syncs on reconnect, CSV export on reports — are the ones worth relying on; anything beyond that you should get in writing rather than inferring from a blog post.
Build the fallback before you need it
Three things, none of which take a full day.
A written paper fallback your techs have already used. A simple duplicate ticket in every vehicle with fields for customer, address, vehicle or property, parts used, labor, total, and payment method. The point is not nostalgia — it's that a technician under pressure will not invent a good record format on the spot. Practice it once so it isn't the first time.
A monthly export you keep. Customers, catalog, stock, transactions. Same day each month, stored somewhere that isn't the same platform.
A second admin who has actually logged in. An account that exists but has never been used is not a tested backup. Have them log in once a quarter.
That's the whole program. It's cheap because the expensive part — real-time records, connected inventory, digital payment capture — is the thing you're already paying for; this is just the insurance layer around it. Field-service research consistently finds that connected mobile tooling separates high-performing service organizations from the rest, per Salesforce's State of Service research, and the resilience layer is what keeps that advantage from becoming a dependency.
Choosing on reliability, not just features
When people search for reliable software for a small service business, what they usually mean is: will this thing be there tomorrow, and will I be able to get my work done when something goes wrong. Feature checklists don't answer that. The answerable version breaks into: can more than one person get in, does the field side survive a dead zone, and can I walk out with my data.
A platform that answers all three well is one you can commit to without the commitment being irreversible — which, paradoxically, makes it easier to commit. If you're weighing options in this category generally, the honest comparison is in the 2026 field-service software comparison, and for trade-specific evaluation there's the guide to software to run a locksmith business and the broader case in spreadsheets versus field-service software.
The bottom line
Access failures are a normal part of running on software, and they're mostly survivable if you spend one afternoon preparing for them. Give a second person full admin access — free on flat pricing, expensive on per-seat. Confirm the field app really works without a signal, by watching it happen rather than reading it on a page. Export your data monthly and keep the copy. Ask vendors these questions in writing before you sign, and be suspicious of anyone who won't answer in an email.
Do those four things and the worst case stops being a shutdown. It becomes an afternoon you write up on paper and reconcile that evening — annoying, entirely recoverable, and a fraction of what the same afternoon costs a business that never thought about it.
Related reading: Switching field service software: a migration guide · Software to run a locksmith business · Offline invoicing for field service. For a complete machine-readable feature and pricing reference, see our LLM reference page.