Hiver is a customer service platform that brings together communication channels, apps, and data to improve customer support operations. Hiver enables real-time collaboration across every customer communication channel, offering AI and automation to resolve issues and help teams work faster. Hiver states that over 10,000 teams of all shapes and sizes globally from Flexport to Harvard University, Vacasa, and Epic Games rely on Hiver to deliver support that wins and retains customers for…
$24
per month per user
Salesforce Service Cloud
Score 8.5 out of 10
N/A
Service Cloud is a customer service platform that helps businesses manage and resolve customer inquiries and issues. It provides tools for case management, knowledge base, omni-channel support, automation, and analytics, enabling companies to deliver exceptional customer service experiences.
$25
per month
Pricing
Hiver
Salesforce Service Cloud
Editions & Modules
Lite
$24
per month per user
Growth
$34
per month per user
Pro
$59
per month per user
Elite
Contact Sales
Starter Suite
$25
per month
Pro Suite
$100
per month per user
Enterprise
$165
per month per user
Unlimited
$330
per month per user
Agentforce 1
$550
per month per user
Offerings
Pricing Offerings
Hiver
Salesforce Service Cloud
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
20% discount for annual pricing.
—
More Pricing Information
Community Pulse
Hiver
Salesforce Service Cloud
Features
Hiver
Salesforce Service Cloud
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Hiver
9.0
4 Ratings
11% above category average
Salesforce Service Cloud
8.8
77 Ratings
9% above category average
Organize and prioritize service tickets
9.04 Ratings
9.475 Ratings
Ticket creation and submission
9.04 Ratings
9.375 Ratings
Ticket response
9.04 Ratings
9.174 Ratings
Expert directory
00 Ratings
8.553 Ratings
Subscription-based notifications
00 Ratings
8.663 Ratings
ITSM collaboration and documentation
00 Ratings
8.260 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
Hiver
8.0
1 Ratings
2% above category average
Salesforce Service Cloud
8.7
72 Ratings
10% above category average
External knowledge base
8.01 Ratings
8.463 Ratings
Internal knowledge base
8.01 Ratings
8.970 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
One scenario where Hiver works really well is in a shared support or billing inbox or anywhere multiple team members need access to the same messages. For example, when a customer emails about a billing question, we used to reply and manually loop in the billing team or forward the message. That often caused confusion, especially when someone forgot to “reply all” or responded only to the teammate instead of the customer.Now with Hiver, we just assign the conversation to the billing inbox, and whoever is available can respond. Everyone on the team can see the thread, status, and notes, which avoids duplicated efforts and missed replies. We also used to rely on Google Groups, but it wasn’t clear if someone had already replied, and there was no easy way to collaborate behind the scenes. Hiver completely solved that for us.As for situations where Hiver might be less ideal, I’d say if your team isn’t using Gmail or Google Workspace, then it’s probably not a good fit. It’s really designed for teams that live in Gmail so the team doesn't have to learn a new system. I'm sure some businesses will require a more robust ticketing solution but for our use case, this was a perfect option to improve outcomes, client service, and satisfaction.
It is a helpful tool, but it can be a bit cumbersome to manage. It is also a bit expensive, but we already use CRM for Salesforce and it is convenient to be able to immediately tag contacts and accounts when the tickets come into the system and tie them directly to the account. I do know an integration with Jira is possible (we use Jira internally for our engineering team to escalate issues) but it is not configured right now so managing the connection between support tickets and Jira tickets is manual and hard to keep up with
Professional edition works best for a small company with lower call volumes and is very useful but as you grow exponetially I think it has limited ability to do all the things we want to - SLA management, defect, release management to name a few. Reports and dashboards being available in real time.
I had Salesforce experience prior to using Service Cloud which made it a little easier to learn and navigate, but overall my team (some who had no Salesforce experience) caught on very quickly and found Service Cloud to be easy to use.
Salesforce's Trust Center clearly communicates occasional issues to anyone who subscribes, down to an organization's cloud instance. Bundled sandboxes ease updates, and seasonal upgrades are seamless, scheduled well in advance with plenty of information about what's coming. Support agents have noticed intermittent Omni-Channel disconnects due to internet connections, and these are clearly notified.
The Salesforce Service Cloud generally has very good performance, however the overall new Lightning user experience can bring that down. For example, if you have too many tabs open, then it can take a while for the Lightning UI to load. This UI is probably not well equipped to handle loading of all of that information at once, but Users tend to leave their tabs open all day long. It can also be fickle depending on which browser you use, what extensions you have installed, and whether you've cleared your cache. This can be the downfall with any software as a service though, not just Salesforce
Salesforce offers support, although it generally gets routed to overseas support teams first, and once they are unable to help, it gets escalated up the chain to higher tiers. Frequently, the answer back from support is that there is no native solution, and we either have to turn to the AppExchange for some solution provided by another developer, or custom build our own solution.
Our in-person training was provided by our implementation partner and it was quite good. This was in part because we were already working with them and so it naturally leant itself to a good training relationship. And because they were building our customizations and configuring things, they could then provide training on those things naturally.
Trailheads are great but it was often unclear what actually applied to our organization. This made it difficult to get a whole lot out of it. Part of it is that because the basic Salesforce features didn't quite work for us, we had to add customizations, which then nullified a lot of the training.
I would go through an implementation very differently knowing what I know now. It was difficult coming from systems we liked in post-sales service and having to adapt to the clunky and underwhelming feature set in Salesforce. I would trim back our expectations
True ticketing solutions are certainly more robust in that you can typically manage social media channels and phones, etc. But, in my opinion, when you don't have a team solely responsible for managing a ticketing system they can be complicated to implement. With HIVER, we're already all accustomed to managing our own G-Suite inbox, so it was simply a matter of teaching the team how to utilize the solution.
Salesforce service cloud is more configurable than Zendesk and Freshdesk. It has its own inbuilt AI chatbot also which further improves service agent efficiency. Salesforce is more integration agnostic and has pre-built connectors with multiple 3rd party systems. However, in terms of pricing it is priced at a premium compared to the other solutions
The ROI on showing how many emails are being received and addressed in a timely manner are great for KPIs
the ability to search and ensure emails are not being deleted as an automatic report is sent out the following day saying if any emails were deleted by whom
the ability to automate who gets assigned what emails from specific vendors per entity
Because this is a cloud service, the security, implementation framework and feature list is very mature and you don't have to develop these during implementation.
The larger the implementation programme the better the licensing arrangements
Free developer toolkit for proof of concepts or showcasing features