Field Service Dispatch Software

Yes. Dispatch is an add-on module, not a standalone product. It installs into a Seedly CRM you already own and uses that CRM's contacts, permissions, automations, estimates and invoices. If you do not own the CRM, buy that first; Dispatch is worth nothing on its own.

5.7.1 or later on the 5.x line, and it has to be a 5.7.1 whose CHANGELOG entry is dated 2026-08-29 or later. That sounds fussy and there is a reason for it. 5.7.1 was cut three times under the same version number, the extension points this module binds into only landed in the last of them, and the version number alone cannot tell them apart. The installer checks before it writes anything, and on an older cut it refuses, names the missing extension points and leaves your CRM untouched. If you are behind, update the CRM first and the install is uneventful.

It is a one-time $599, and there is no subscription. If you own all three Seedly products, Seedly CRM, Seedly Sites and the Seedly Community Platform, Dispatch is free. Buy all three in one order and the receipt unlocks it as you tick the last box. If you already own all three from separate orders, that is still free but it is not automatic, so email me and I will set you up by hand.

Nothing. You bought the source, so there is no seat metering and no per-technician fee anywhere in the product. This is the single biggest difference between owning your dispatch software and renting it, and it gets bigger every time you hire.

It installs to the home screen and behaves like an app, and it keeps working through the dead spots that come with basements, crawl spaces and rural routes. It is not a native app distributed through the Apple or Google stores, which also means there is no app-store review sitting between you and a change you want to make.

No. Location is recorded only between the moment a technician taps on my way and the moment they tap arrived, it takes their own consent on their phone, and they can stop it whenever they like. The live map shows where each technician last reported from. The breadcrumb trail that draws a whole route is a separate setting and it is off until you switch it on, and while it is on those trails are kept for thirty days. The two arrival stamps on a visit are the part that does not expire, because a customer can still ask months later whether somebody was actually there and when. Nothing is recorded when a technician finishes a job, and the server refuses to file a location against a finish tap at all.

No, and this is a deliberate limit rather than a bug. A technician's working hours have to end after they start, so an overnight shift cannot be entered and route planning works one calendar day at a time. A night shop can run Dispatch by treating each night as its own day, but the optimizer will not plan across midnight.

The board shows a day or a week. Planning a month of contract work happens on the jobs list instead, which is the better shape for that job anyway. If you want a month view on the board, the source is yours and it is an honest afternoon of work.

The dispatcher's own computer. The board and the booking windows it suggests use whatever timezone that browser is set to, which is right whenever the person dispatching sits in the shop's timezone and drifts when they do not. Worth knowing if you dispatch for a shop in another timezone, or if the office moves around.

A visit carries a lead technician and one helper, and only the lead can finish the visit. A three-person job needs a second visit on the same job. Worth knowing before you build a crew workflow around it.

Yes. Monthly consolidated billing closes a route at once, which is how a nightly janitorial contract or a maintenance round is actually invoiced. Anything that could not be priced appears under held for review with a reason rather than billing at zero. The one limit: a single location runs one billing rhythm, so monthly consolidated and multi-part deposit billing cannot both be switched on for the same location. Different locations can run different rhythms.

Field payments and paid estimates run on the CRM's Stripe connection, and the customer texts run on its SMS connection, because Dispatch has no payment or messaging system of its own. It hands every message to the CRM, which is also what enforces do not disturb, STOP opt-outs and consent. Two defaults worth knowing before you judge it on day one. Every customer message is off until you turn it on, so a shop that skips that step sends nothing. And on-site billing is off until someone with invoice permissions turns it on, which is what makes the present-estimate button appear for a technician.

No, it feeds it. Dispatch writes into the estimates and invoices your CRM already has rather than keeping a second ledger, which is why the money side does not drift from the office. Estimates presented on site come from the same templates your office quotes from.

ServiceTitan is built for shops running twenty or more technicians and it prices per technician on a quote, with no public pricing at all. Its own feature index lists eight separate paid add-on suites on top of the base platform. Reviewers consistently raise three things: implementation measured in months, an app that is slow on the older phones the field actually carries, and limited offline capability for technicians in basements and rural areas. Seedly Dispatch is a one-time purchase with everything in the box, and you can read the price before you talk to anyone.

Jobber is the most usable of the three and it publishes its prices, which is more than ServiceTitan does. Its team plans are capped by user count, so growth moves you up a tier rather than costing nothing. The complaints that come up most are reporting and a lack of flexibility for non-standard schedules. Seedly handles every second week, every third week and the nth weekday of the month as ordinary schedules, and adding your ninth technician does not move you anywhere.

Housecall Pro is the closest fit to the same buyer and it does the core job well. Its most common complaint by a distance is add-on pricing: sales proposals, vehicle GPS and the price book are each sold separately on top of a per-user subscription. Dispatchers also report needing more than one window open to see available times and available technicians at once. Seedly puts availability and assignment in the same view, and there is no add-on tier because you bought the source.

The technician app keeps working. Offline is the single most common complaint about field software, because the work happens in basements, crawl spaces and on rural routes where a tool that needs a connection stops being a tool. The day is cached and the shell holds up through the dead spots.

An afternoon, not a quarter. Pick your trade and the settings that shape that trade's day are written for you, then you import your customers with the CRM's own contact importer and Dispatch turns the ones with an address into service locations, a hundred to a click. Fair warning on that last step, it reads your oldest thousand contacts and the window does not move, so a big existing book needs its newer customers added by hand or from the booking screen. Enterprise field software is routinely reported as taking months to implement, and some contractors have paid for a year before being fully onboarded. That is not the shape of this.

Yes. You own the source and there is no seat or technician metering, so you can run it for every home-service client in your book from the same install, white-labeled to each brand, the same way you run the rest of the CRM.

There is nothing to stop paying. You bought the source once and it runs on infrastructure you control, so there is no renewal that can hold your job history hostage and no export deadline if you change your mind about the vendor.