When dispatch goes down, every single van in your fleet stops earning until somebody manages to fix it.
A service company does not have one deadline. It has forty a day, and they all run through dispatch. If that platform is down at seven in the morning, nobody knows where to go.
Your phones are the other half. A homeowner with no heat calls three companies and books whoever picks up. Losing calls for two hours in January is not really an inconvenience.
Dispatch and scheduling stay up during your busiest week of the year.
Techs take payment on a tablet without card data spreading everywhere.
Your customer list and service history get backed up and tested.
Vans get devices that survive being dropped, shared, and left outside.
Thirty minutes is the longest you wait, no matter what you need from us.
New techs are set up before they arrive, and closed out when they go.
After-hours calls reach somebody, because your on-call tech works then too.
Trades IT gets judged on two mornings a year: the first hard freeze and the first heat wave. Everything has to hold when call volume triples, dispatch is running flat out, and every single technician is being routed straight to the next address.
The scheduling platform is your business, so it gets treated that way. Monitoring, vendor escalation, and a documented recovery route matter far more here than on an ordinary office network.
Card details taken at a customer's own door should never touch your general network. Segmentation keeps payment traffic separate, which is also what your acquirer's questionnaire is actually asking about.
Customer records and service history are the most valuable thing you own. Backups get tested, and access gets structured so a departing technician cannot walk out with the whole database.
Field devices are chosen and configured to be dropped, shared between techs, and left in a hot van. Each person still gets their own login rather than one shared password.





For most service companies one application is the business. Dispatch, scheduling, job history, and invoicing all live inside it, and when it is unavailable there is no manual fallback that holds past about an hour. That makes it a different kind of system from a file server, and it deserves different treatment: monitoring that tells us before your dispatcher notices, a documented escalation path into the vendor, and a written answer to what your office does for the first hour.
The awkward truth about these platforms is that we do not build them, so nobody can promise the vendor will never have an outage. What we can do is know your configuration, hold the vendor relationship, escalate as a partner rather than as a customer opening a ticket, and make sure your team has a paper route for the first hour. That beats discovering all of it at seven in the morning.
Dispatch and field platforms get monitored, so we usually know before your dispatcher calls us.
The vendor escalation route is documented, so nobody has to start in a general support queue.
Your office has a written route for the first hour, before anything has been restored yet.
The moment a technician takes a card payment on a tablet at somebody's front door, your business is inside the payment card rules whether anybody told you or not. In practice that mostly means one thing: card data should not be traveling across the same network as everything else, and the devices handling it should be doing nothing much else. Most trades companies are compliant largely by accident because they use a processor's own app, and the questionnaire still has to be answered honestly.
We are not a payment auditor and we do not certify anybody, which is the right arrangement for you. What we do is set the network up so payment traffic is separated properly, document how the devices are configured, and go through the self-assessment questionnaire with you so the answers match reality. Your processor will accept a truthful answer far more comfortably than an optimistic one.
Payment traffic gets separated from the rest of your network, rather than simply sharing it.
The self-assessment questionnaire gets answered from how your devices are actually configured.
Devices handling card payments do not also double as the tablet somebody browses on.
If a service company burned down tomorrow, the vans and the tooling could be replaced. The list of every customer, what equipment they have, when it was last serviced, and which of them are on maintenance agreements could not. That database is most of what the business is actually worth, and in a lot of companies it is protected rather less carefully than the petty cash. It also walks out of the door with anybody holding full access and a grievance.
Two different problems live here and they need different answers. Losing the data is a backup problem, and the only backup that counts is one somebody has watched restore. Somebody taking a copy is an access problem, which means structuring who can export what rather than giving every office user the run of the system. Both are ordinary work, and both get deferred until one matters.
Backups of your customer database get restore-tested, rather than just scheduled and assumed.
Export and bulk download permissions get limited to the handful of people who genuinely need them.
Access closes the day somebody leaves, including on any personal device still signed in somewhere.
The owner of a service company is usually also the person who reboots the router, resets the dispatch password, and rings the internet provider. That works until the volume arrives, and then it competes directly with actually running the whole business.
Dispatch Comes First
Dispatch gets treated as the system your revenue runs through rather than as one more line-of-business application. Monitoring, vendor escalation, and a written recovery route exist well before the morning you actually need any of them.
Cards Stay Separate
Payment traffic is kept separate from the rest of your network, which is both the sensible arrangement and roughly what your card processor's own questionnaire is asking you to confirm honestly every single year without exception.
Answered Fast
White glove support in a trades business means dispatch never waits longer than half an hour, whether it's August or February. Extended hours cover the evening calls your own on-call technician is probably already taking anyway.
Vans Get Real Kit
Field devices get chosen and configured for vans rather than desks, with individual logins instead of one password the whole crew knows. Replacing a dropped tablet stops being a half-day problem for somebody in the office.
Two things run in parallel. We escalate into the vendor as a partner rather than joining the general queue, and your office switches to the written first-hour route that was agreed before the season started. That route is usually low-tech on purpose: the day's schedule printed or exported each morning, phone numbers for the crews, and one person taking bookings on paper. It will not feel good, but it means the vans keep moving while the platform comes back, which is the part that actually costs money.
Yes, and most owners find that out later than they would like. The obligation attaches to the business accepting the payment, not to the app doing the processing. The practical exposure is usually smaller than it sounds because processors handle the sensitive part, but you still have to complete a self-assessment questionnaire truthfully and your network still has to be arranged so card traffic is not mixed in with everything else. We handle the network side and go through the questionnaire with you; the formal certification side belongs to an independent assessor.
In most companies we look at, yes, and usually nobody had decided that. Export and reporting permissions in dispatch platforms are frequently left open to every office and field user, so a full customer download is a few clicks for anybody with an account. Fixing it is unglamorous: limit bulk export to the small number of people who need it, log when it happens, and close accounts the same day somebody leaves rather than at the end of the month. None of that is difficult, and it is very hard to do retrospectively.
By expecting them to fail and planning the replacement rather than the repair. Field devices have a genuinely shorter life than office equipment, so they belong in the budget as a rolling replacement instead of an emergency purchase each time one dies. The bigger point is configuration: a replacement should be usable within an hour because the setup is documented and the data lives in the cloud rather than on the device. Encryption matters too, since a tablet left in an unlocked van is the most likely way you lose customer data.
Most owners find out how thin their security was on the day it fails, and how slow their IT company is on the same day. You can find out now instead, on a call that costs nothing, from somebody who will say it plainly.
Call (702) 874-3767 today or fill out the form below to see firsthand what white-glove IT services look like.