HubSpot Service Hub aims to bring customer service data and channels together in one place, and helps scale support through automation and self-service. According to the vendor, Service Hub provides more time for proactive service that delights, retains, and grows your customer base.
$50
per month
ServiceNow IT Service Management
Score 8.5 out of 10
N/A
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.
I can only speak to our use case - in which HubSpot Service Hub is used as our Support Desk ticketing system. It is well suited to intake and log support issues, it makes communication with clients easy, and allows us to track and move tickets through custom statuses. HubSpot Service Hub also allows us to integrate with JIRA when we need to escalate and assign tickets to our development team so that we can continue to track status. It is well suited to automate communications, routing of tickets to different queues, and customizing ticket statuses.
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.
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.
The app is a bit confusing and does not seem to have all of the features that the online browser does
A bit expensive. I do think it is worth it because of the simpleness but it is a very pricy software
Sometimes when you reach out to HubSpot Service Hub support, they send you a link to public articles instead of helping. But sometimes they do jump in and look
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!
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.
although it has room for improvements, this is still a very robust service hub for any type of software. An internal comment I often heard was, that if we were to make this as good as for example zendesk, it shouldn't have to feel like we must have external systems integrated to the HubSpot Service Hub (in zendesk, most things happen within the same system). I suppose this is more a matter of preference, because just like all other hubs, we see way more benefits of allowing our service working in the same way as the other departments (which won't happen if you have an external service system).
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.
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.
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.
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.
HubSpot [Service Hub] had many integrations we needed to connect to our CRM, and the cost was just right from them VS the others. We had to look at all the features, and HubSpot CRM just had way more than the others and more bang for your buck. So the Service Hub was just a bonus with their CRM tools.
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.
Sales targets are visible; any changes made can be easily tracked and accounted for
Overall lead lifecycle management has improved and the way data moves to other apps makes life easier for the other business functions to keep track on the new and old deals
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.