Straight into the service manual page
WrenchQuarry
More

Dispatch software terms to check: 2 tools compared

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

The terms that matter most in dispatch software are uptime, outage remedies, claim deadlines, trial length and cancellation rules.

Features matter too, so test the scheduling board, the quote builder and the map view. But demos show the parts that look good on a quiet Tuesday afternoon. The terms decide what happens at seven on a Monday morning, when the job sheet will not load and three techs need their routes, and they shape what you pay over the life of the contract.

It also covers FreshBooks, with fewer specific points. It looks only at contract-side points with a specific, sourced answer. It does not rank the products on features or say which one suits your trade best.

Owners and dispatchers read terms differently. An owner looks at the monthly bill and the length of the contract. A dispatcher looks at whether the system stays up during the working day, and what the team can do when it does not. Read this with the person who will be on the phone when something breaks.

Start with the uptime promise

A service level agreement, or SLA, describes how available a service will be and what you get if it is not. Many small firms never open it, and that is a mistake. A sales rep saying the product is very reliable gives you nothing written to enforce. The uptime line is usually the first thing a sales rep quotes and the last thing anyone reads.

ServiceM8 publishes its Service Level Agreement. The page says the company knows that customers depend on ServiceM8 to be available 100% of the time. It then makes a specific guarantee: ServiceM8 will be available 100% of the time in a given month, excluding scheduled maintenance.

Read the exclusion as carefully as the guarantee. Scheduled maintenance is carved out, so the 100% figure does not cover every hour the system might be unavailable. Before you sign, ask how maintenance is announced, how much notice you get, and whether it usually lands outside your busiest hours. Those answers affect your schedule more than the headline number does.

Think about how the figure is measured. The promise is written per month, so ask how the vendor counts downtime, whether it reports outages it has already fixed, and where it publishes past availability. A promise is only as useful as the reporting behind it.

Mobile access is a separate promise

Dispatch software is only half the job. The rest happens on phones and tablets in attics, crawlspaces and mechanical rooms, where techs check job details, update status, collect signatures and take photos. For many firms the mobile app is the part the crew uses most, so it deserves its own check.

The same agreement treats mobile access as a separate guarantee. It says you can access the service through a mobile device, iPhone or iPad, where network connectivity is available, 100% of the time in a given month. Notice the condition. The guarantee covers the service when a phone has a connection. It does not promise a signal in a basement or at a rural job site.

That gap is what your crew will feel. Ask the team which parts of your service area have weak coverage, and test those spots during any trial. Then agree on a fallback before it is needed: what a tech does when the job sheet will not load, who takes the call, and how the job gets written up afterward. A paper form in the van and a rule for entering it later is a plain, cheap answer. The guarantee does not promise your phone will have a signal, so the fallback needs a plan from your side.

Print the fallback on one sheet and leave it in the van: the office number, where the paper forms are and who enters them later. A fallback nobody can find at seven on a Monday is not a fallback. For the job-handoff side, see Field Service Work Order Checklist for Dispatch Handoffs.

Test the handoff, not just each screen. Have a tech start a job on the phone, add a photo, change the status, then check that the office view shows the same update. Agree the status words first, using work order statuses before dispatch. Dispatch is only as useful as the handoff between the van and the desk.

What a ServiceM8 outage credit is worth

When an outage happens, the remedy is set out in the same agreement. The vendor says it will issue a credit on your next bill for 5% of your monthly fee for every 30-minute period of downtime, up to 100% of your fee for the month. The credit comes off a future bill. It is a discount, not a refund of money you have already paid.

Do the arithmetic before you need it. Each full 30-minute period of downtime earns a credit of 5% of the monthly fee, and the total stops at 100% of the fee for the month. A credit will not make up for a lost day of dispatch. The useful question is how the vendor's own remedy scales, so you can judge whether the terms offer meaningful protection for a shop your size.

Two limits matter. The first is the exclusion. The terms do not cover downtime caused by your equipment, or by third-party equipment that is not within ServiceM8's primary control. Your office router, a dead tablet battery or a laptop with a faulty network card are your problem. A mobile carrier failure is less clear. It may fall under the third-party wording, so ask the vendor directly how it treats a carrier outage.

During the outage itself, decide early which jobs can run on paper and what customers with booked appointments should hear. Those choices are cheap to make in advance and costly to improvise under pressure.

The 30-day clock on credits

The second limit is timing, and it catches more owners than the exclusion does. The terms say customers must request the credit within 30 days of the outage, and that failing to make contact within 30 days forfeits the right to receive it.

The credit is not automatic, whatever many owners assume. Someone has to notice the outage, know the rule and make the request. The 30 days run from the outage itself, not from the day someone reads the email about it. A credit you never claim is worth nothing.

Set up a simple routine. Give one person the job of logging every outage with the date, the start and end times and a short note on what failed. When an outage is logged, put a reminder in the calendar for the 30-day mark and make the request well before that date. A dated log is far easier to work from than memory if a credit is ever disputed.

Who picks up when it breaks

An SLA tells you about the platform. It says little about the people you call when something goes wrong at a job site. For a dispatcher the questions are practical: who answers, how do you reach them, and what do they need from you before they can start?

Ask each vendor for its support channels in writing: phone, chat, email or ticket, and whether the channel you need is included in your plan or costs extra. Ask whether support covers the hours your dispatch desk actually runs. A help line that closes at the end of an ordinary office day is of little use to a plumber on an evening callout.

Ask what the support team will want when you report a problem, such as the account name, the user who saw it, the device and app version, and a screenshot. Keep that list on the dispatch desk so the first call takes minutes, not an hour of searching.

Also ask whether the vendor posts status updates during a widespread problem, and where. A status page you can check before you call beats waiting on hold while your schedule slips. Treat each of these answers as something to get in writing, not something to assume.

Test support during the trial too. Send one real question on a weekday morning and another late in the day, and note how long each takes to get a useful answer. That is the best preview you will get of a bad week.

Workiz and its free trial

Workiz's pricing and plans page says the company offers a 7-day free trial that lets you explore all the features of the platform without any commitment. That is the most concrete trial term here, so take it seriously.

Seven days is short for a shop with a full schedule. Plan the trial around real work rather than a tour of the menus. Load your actual service area, technician names, price book and a handful of recent jobs whose outcomes you already know. Have one dispatcher and one tech run live jobs through the system, not made-up ones. If the first time anyone opens the mobile app is day six, you will learn very little about it. Start the trial in a normal week, not one with a holiday or a slow spell, so the test reflects your real mix of jobs.

Note what slowed people down, what they had to type twice and what they could not find. That friction list is the real evaluation. A feature list tells you what a product can do. The friction list tells you whether your team will actually use it on a Thursday afternoon with jobs running late.

Check what happens at the end of the trial too. Ask how billing starts, whether a card is needed to begin and what happens to your data if you stop, all in writing before you enter payment details.

Annual plans and the real cost

The vendor describes its annual saving of $400+ as better value for long-term use, so ask what that saving is measured against. Ask for the monthly price and the annual price side by side, in writing, for the exact plan and number of users you need.

Also compare what you will pay as you grow. A plan that looks fine for three people can feel very different at ten. Ask how pricing changes when you add a van, a dispatcher or a seasonal tech, and whether the annual rate changes if you add users partway through the year.

The annual discount only helps if you stay. A saving on a twelve-month commitment does nothing for a firm that quits in month four because the crew never adopted the tool. If the trial is unfinished or the dispatcher is still unsure, a monthly plan costs more each month but limits the damage of a wrong guess.

Find the cancellation terms in the agreement you will actually sign: the notice period, whether the plan renews automatically, and what you get back if you cancel early. Check whether you can export your data when the contract ends, and in what format. A plan that is cheap to start and hard to leave is expensive in the end. A pricing page is a sales page, and the binding answer is in the contract. Have your bookkeeper and your attorney, if you have one, read that document before anyone clicks accept.

FreshBooks: what this section covers

This section gives no FreshBooks rule, number or date for job-management use, trials or outage remedies.

The one line we found describes payroll and expense recording. It is marketing: FreshBooks's own site says you can "Easily pay yourself or your team with unlimited payruns and automated tax calculations and expense recording, all without ever leaving FreshBooks." The quote says nothing about scheduling, dispatch or job status, which is the work between the phone call and the invoice. Check that side yourself.

Ask FreshBooks the same questions you would ask anyone. Does it publish an SLA, and what does it guarantee for availability and mobile access? What is the remedy when the service fails, and how long do you have to claim it? How long is the trial, and does it include the features you will use? What do a month and a year cost, and what do the cancellation and data export terms say? Get the answers in writing and compare them with the ServiceM8 and Workiz answers above.

If your firm already runs its books in FreshBooks, the link between the two systems matters. A dispatch tool that connects cleanly to your invoicing can cut down on re-typing job details. Check whether an integration exists, and test it with a sample invoice before you rely on it for billing.

If FreshBooks is already part of your office, do not read its gaps here as a verdict. They mark what this post does not cover, and the vendor can fill them in writing.

Read the terms side by side

Here is the comparison on the points this post covers.

TermServiceM8WorkizFreshBooks
Monthly availability100% in a given month, excluding scheduled maintenanceNot checkedNot checked
Mobile access100% in a given month, where network connectivity is availableNot checkedNot checked
Outage remedy5% of monthly fee for every 30-minute period of downtime, up to 100% of the month's feeNot checkedNot checked
Claim windowWithin 30 days of the outageNot checkedNot checked
Free trialNot checked7 days, no commitmentNot checked
Annual pricingNot checkedAnnual saving of $400+, a vendor figureNot checked

A cell marked Not checked is a question to put to the vendor, not a sign that the vendor lacks the term.

ServiceM8 publishes the most specific terms here, so its promises are the easiest to test and to hold the vendor to. Workiz gives a trial length and an annual figure to plan around. A published term is a good sign, but the question that matters is whether those terms fit how your firm runs its days.

Keep the numbers apart when you compare. A credit formula, a free trial and an annual discount measure different things, so do not add them together or use one as a substitute for another. Ask three questions of each tool: what happens when it is down, what it costs to find out whether it works for you, and what it costs to leave.

Split the work

Owners and dispatchers should each own part of this. The owner reads the uptime terms, the annual pricing and the cancellation terms, and asks vendors for written answers. The dispatcher runs the trial on live jobs, keeps the friction list, and tests the mobile app in the weakest signal spots on your service map. The dispatcher also owns the 30-day reminder for each logged outage, counted from the outage itself, because a missed ServiceM8 claim window means losing that credit.

Agree on who signs the final agreement, and make sure that person has read the terms, not the sales summary. If the owner is away when you decide, the dispatcher should not be left guessing about cancellation rights or renewal dates. Put the trial end, the renewal date and the cancellation notice deadline in the shared calendar. Revisit the terms before each renewal, not only at sign-up. Prices and support hours can change quietly, and the notice deadline is the moment to decide again.

Before you sign with any vendor, pull up its current terms and check them against this post. Pages change, so the current page and the agreement you sign are the documents that count.

Related guides: Avoidable truck rolls: 3 dispatch mistakes to fix · Boiler water: 2 temperature checks and safety terms · Check 5 guardrail and toeboard limits before dispatch.

Sources

More field guides