Gainsight’s customer-centric technology aims to drive the future of customer success. The company’s Customer Cloud offers a set of solutions focused on customer success, product experience, revenue optimization, customer experience, and customer data, that together are designed to enable businesses to put the customer at the center of everything they do. The vendor states that companies that use Gainsight grow net retention by up to 33 percent. Learn how leading companies like Okta, SAP Concur,…
$2,500
Per Company Per Month
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
While features vary across the platform - Gainsight is the easier one to look at every day...appearance wise. It's very well laid out and easy to follow.
Well suited for: consolidated and organized note taking tracking stakeholders contact information if properly configured - identifying and categorizing risk categories less appropriate setting up customer journey takes quite a bit of work to implement and make use of - want best practices baked into the product - "customer journey wizard" reporting is robust but clunky to set up reports and get meaningful data
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Gainsight's Data Designer is a powerful tool that allows you to create new tables/data sets from different sources (Create a new table by merging Snowflake, SFDC and Gainsight data that you can use for reporting or be the engine of calls to actions)
The health score is great! with good data and the right workflows in place, you can easily create automated health scores by your desired segmentation
Journey Orchestrator is the best 1:M outreach tool I have seen from any CSP. Very flexible and comprehensive. Can also support surveys! JO can be used for all segments, not just your digital segments!
Gmail/Outlook integration - Our CSMs love that you can send an email and attach it to the gainsight account. You can also create a meeting note in Gainsight and email it to your customers!
Calls to Action/Playbooks are very customizable, interoperable with SFDC and a great way for CSMs to keep on top of their work and also a great tool for reporting outcomes and CSMs work throughout the year
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
Sometimes tying Salesforce Data into Gainsight objects can be challenging. (I don't believe this is a true Gainsight limitation)
I would love to see the ability to create a dashboard directly from JO Analytics, to help save time recreating measure the program analytics already provide. (Since the JO program analytics aren't extensible to everyone, a dashboard needs to be created )
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
Gainsight offers a level of support that I've not experience before. They will work with you to come up with a solution to a problem - or help match you with another client that has a similar setup as you to get their feedback. Also the functionality that we have built within the software works for us. It's 'easy' to use (once you get the hang of it) and our users rather enjoy working in the software.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
I give it this score based on the implementation at my current employer. I don't know if it could be higher based on if the implementation went better, or if there is something on the vendor side that could help. If this were asked at my previous employer, I would have given it a score of 9 or 10.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
There are some times when it can take almost a minute to load some of our reports or the rules engine. Within a rule it can also take time to load the actions as they each load one at a time when scrolling. The ability to scroll without waiting would be ideal
The CSMs are very hands-on and helpful, both Elaine and Lane have provided a lot of guidance and value over the years. Support is responsive and will jump on things as needed. The thought leadership and community is probably the most valuable part of our support from Gainsight.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
The online videos are very good for basic tasks in the platform, but it isn't very descriptive or helpful trying to make your own specific variables fit the simple example that is typically used. Typically, I'll watch a video, try on my own and still have to get help from support or Customer Success team
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
I was not part of the implantation (I took over later). However, based on what was passed to me, the tool was not well implemented at our org. I think this had to do with complexity, wrong person assigned in our org, and org buy-in. I think it would have been very successful if we had a better assignment process internally.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
Our Salesforce admin is constantly pushing us to adopt more of the features of Salesforce. However, we find that Gainsight is a stronger tool for customization and enhanced interdepartmental communications. Timeline makes it easy to understand where we stand in a customer lifecycle, which is far superior to reviewing an activity history related list in Salesforce.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
We increase account coverage by more than 20% through the tools within Gainsight CS to generate actions for our CSMs to prioritize accounts.
Now that we are using Success Plans, we are seeing 65-75% of customer outcomes realized within a 12-month period. This was something we weren't able to track before.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
