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.
This program is used by the nonprofit organization where I work to keep track of and follow up with individuals who are curious about what we do. It's really straightforward to use once you know what functions are available. I spend the entire day on and off OctopusPro, and occasionally I have to train my teammates on its use. When someone new enters your pipeline, the automations make it simple to get in touch with your network. That relieves me of one task while maintaining a personal touch with the recipient of the email or text.
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.
OctopusPro is a cloud-based service management software with everything you need to run a mobile business. We’ve been able to track leads, manage invoices, and streamline communication between our dispatch team and mobile cleaners. It's helped reduce admin costs and boost repeat business. The support team has been responsive, and onboarding was relatively smooth.
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.
