DunwareSolutions
Manage clients with many locations, send crews on routes, onboard new accounts with checklists, and bill recurring contracts, all in one flat-priced system.
A customer can have any number of service locations, each with its own jobs and history.
Reusable plans and per-customer checklists help you start every new account the same way.
Dispatch builds routes and stops, and crews work them from a phone with shift tracking.
Weekly to yearly invoices, with overdue reminders at 1, 3, 7, 14, and 30 days.
A typical new contract for an office building looks like this.
The lead moves through the pipeline and is converted to a customer.
Add each building as a service location, and attach the signed contract in Documents.
Apply a reusable onboarding plan so keys, access, and supplies are handled the same way every time.
Dispatch creates routes and stops for each crew. Crews open the day's route on their phones.
Dispatch messages crews in real time to reroute or send notices.
A recurring plan raises each period's invoice. Overdue reminders go out on schedule, and the client pays through the portal.
| Typical per-seat field service software | Dunware Field Management | |
|---|---|---|
| Many locations per client | Varies by plan | Included |
| Onboarding | Often handled outside the software | Reusable plans and per-customer checklists |
| Crew communication | Often a separate app | Chat with phone alerts included |
| Recurring contracts | Varies by plan | Recurring invoices with overdue reminders |
| Cost as crews grow | Grows with every user | No change |
The middle column describes common pricing and packaging models, not any one vendor.
We state the limits plainly.
Dunware offers shift-based location sharing with a consent screen, and a monitoring policy template is included. It cannot track a phone whose screen has been off for a long time.
No. There are no seat counts anywhere in the model.
Request a demo, or ask about joining the pilot.
Request a Demo