Reflektive vs. ServiceMax

Reflektive is well suited for medium to large organizations where cross-functional work is a regular occurrence. It isn't meant to be used for employee reviews, self-reviews, or take the place of a corporate communications platform; rather, it is meant to do one thing - serve as a public soapbox and repository for giving and receiving employee gratitude.

Incentivized

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.

Incentivized

• In larger organizations, it is difficult to communicate and share news with everyone without sending all-agency emails. Reflektive lets you provide that feedback or recognition for everyone to see, but saves your inbox from unnecessary emails.
• The weekly roundup email highlights a few of the most recent recognitions. It’s nice to see a brief highlight, without having to get notifications for each post.
• Reflektive let’s you tag multiple people in a post, so you can thank a whole team in one post.

Incentivized

• As it's built on Salesforce, the reporting tools are fairly robust
• The service flow managers can be setup to easily lead technicians to entering data in the right place

Incentivized

• Reflektive often didn't do the best job informing users about the product changes we could expect to see.
• Oftentimes, it was hard to know exactly who would see what in the system. We had to go to our customer service rep for a lot of questions that we wished were more thoroughly explained in the help center.

Incentivized

• Dispatch console seems slow and the data is more of a pull than a push into the database.
• It seems to be a Ferrari and takes a lot of labor hours to configure.
• Still does not integrate with Apple's products very well.

Incentivized

Reflektive is great with support. From the beginning, when it comes to training materials for those new to Reflektive, to clearly rolling out updates in the interface or releasing new features, everything is very clear and communicated solidly. Support is always available when needed, and answers are easy to find when support is not available.

Incentivized

Engaged account management. Support is based worldwide but handoffs have not been too painful.

Incentivized

Reflektive stacks up really well against its competitors because it's in all in one solution. It provides performance management tools, engagement surveys, and analytics. The majority of Reflektive's competitors only provide one of these features at most. Therefore Reflektive's competitors have to purchase multiple tools and HR teams have to use multiple tools for their employees. This creates more work not only for HR teams but for users as well.

Incentivized

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.

Incentivized

• (+) improved company review process.
• (+) improved company goal tracking and visibility!
• (+) evolving product offering with a responsive team
• (-) Functionality to send rewards/gift cards
• (-) More format options in text boxes
• (-) Integration of GIFs to make feedback more fun / personable

Incentivized

• 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.

Incentivized