Dispatch is a field service management platform for brands that use 3rd party contractors to install, repair, support or maintain products for customers. It allows brands to find and hire contractors, and allows contractors to communicate about service details with customers from their mobile phones.
N/A
ServiceMax
Score 7.9 out of 10
N/A
ServiceMax’s mission is to help customers with asset-centric field service management software. ServiceMax’s mobile apps and cloud-based software provide an overview of assets to field service teams. By optimizing field service operations, customers across all industries can better manage the complexities of service, support faster growth and run more profitable, outcome-centric businesses.
$100
per month
Pricing
Dispatch
ServiceMax
Editions & Modules
No answers on this topic
Subscription
$100.00
per month
Offerings
Pricing Offerings
Dispatch
ServiceMax
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
—
More Pricing Information
Community Pulse
Dispatch
ServiceMax
Considered Both Products
Dispatch
No answer on this topic
ServiceMax
Verified User
Manager
Chose ServiceMax
ServiceMax is a more in-depth system created for larger institutions compared to Basecamp 2. Basecamp is a product that is quick to initiate but lacks the reporting power of ServiceMax, but Basecamp 3 is reported to add reporting functionality. ServiceMax reporting can be a …
Dispatch is well suited for teams looking to improve their delivery notification process. The ability to notify customers via automated phone call or text is invaluable and takes the burden away from the drivers and delivery team on the ground, who can be unreliable and inefficient at times depending on the situation.
Small deployments, where you have some specific need for ServiceMax and absolutely need offline capabilities, and are willing to deal with the problems. Otherwise, you may be better off looking at the built-in Work Orders and field service module that Salesforce is now providing. Their app is direct competition for ServiceMax and integrates much better with cases and knowledge articles.
Dispatch has timely customer service and set up support. Unfortunately, they are only able to assist via phone and do not have a chat option. Chatting would be much easier for being able to answer simple questions or software issues instead of having to wait on hold over the phone.
We used Route4Me but surprisingly there are very few alternatives and companies on the market that are well suited for performing this kind of tracking. I am somewhat disappointed that Dispatch is the only option, only because the desktop and mobile applications can be so buggy and, at times, unreliable. But, the other existing options on the market are much worse.
ServiceMax has an offline capability, and also integrates with our Salesforce side of business. At the time, Salesforce did not have a field service application so we could not consider it, but if we could now, we would probably go with that instead. ServiceMax is also expensive. But at the time, ServiceMax was the only offering out there that integrated with Salesforce, had mobile offline capability, and could operate at the scale we needed.
ROI for ServiceMax is mostly dependent on how in depth the organization wants the software. Our ROI is expected within the second year of operation due to the complexity of integration and the initial training requirements for in-house programmers.
Inventory control ROI is expected within year three or four due to the number of technicians and creating the foundation of information to import into ServiceMax. Expectations are the front end programming will be complete and our programmers will be better acquainted with the modules and architecture to make the inventory integration smoother than the initial integration.
Our organization has been working with ServiceMax for ten months and beginning to incorporate the financials to the work orders. This process has not been as seamless as once projected and the root causes are under investigation. It appears the original fields available to track time between employees were not in depth nor segregated sufficiently for granularity.