HubSpot Service Hub

Hubspot has allowed us to save time and reach our customers on a whole new level. Once we implemented Hubspot the possibilities truly became endless. From a sales perspective we have learnt valuable ways to reach our customers through the sales blog, templates and snippet suggestions etc. In addition we have been able to market to our clients using platforms we didn't even know were possible. Created personalized landing pages, calendar links to schedule meetings and calls saving time going back and forth. Not to mention automation and work flows- a time saver!!! Cant rave enough about using Hubspot and cant wait to see waht they come out with next!!!

Honestly, I think thing we like least about the software is that you cant use the social features to post videos to Instagram from the social hub. Other than that there isn't anything we dont like!

I like the built in reports and default properties that minimized set up time.

I'm not able to customize ticket properties seen when creating/viewing tickets per pipeline so I had to set it up to see all needed properties for all 3 pipelines on each ticket. There is no visibility into our chatbot conversations before they are handed off to a human. Contacts are created from each email sent through service hub and also from ticket submission, when we do not want this to occur. I also can't edit the Support Form to have only ticket properties since it connects to the contact properties to create a contact. I get that Hubspot charges based on number of contacts, but they should give customers the option on whether or not certain actions will create a contact or not. It may make sense for sales hub to do that, but not for service hub. We don't want a bunch of contacts in our system that are possibly end users of our product and not customers.

The ease of setup was the best thing about it, and given that it integrated seamlessly with our preexisting HubSpot apps, it was a no-brainer. It allowed us to continue using HubSpot and expand our view of our customer interactions to include support tickets.

The aspect we have made the most use of by far is the Knowledge Base functionality. This is easy to use, clear and customisable. The recent updates to the template editor are welcome and allow us to make our help centre our own. The insights we get on the helpfulness of articles is also useful to see where refinements can be made and where we are lacking.

The ticketing functionality is extremely limited and counter-intuitive to use. You get the sense that the functionality has been half-built and rushed out. For example, you cannot use HubSpot forms to populate custom Ticket properties, which renders them almost useless as a means of collecting information about the customer's problem. The UI for ticketing should have its own 'look', as they are basically indistinguishable from contacts, making it quite difficult to read simple information, like ticket status and description.