Hiver vs. Salesforce Service Cloud

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.

Incentivized

I think Service Cloud is best suited for medium to large operations that require both proactive and reactive service. It’s a great fit for post-sales support. However, I wouldn’t recommend it for very small companies because it can be quite costly, and many of the features may go unused. Salesforce also performs best when you have a capable team managing it, so it’s important to consider your organization’s size and readiness before starting. Once you do, I recommend exploring other parts of the Salesforce ecosystem—Service Cloud works even better when integrated with Sales Cloud, since it allows better visibility across teams.

Incentivized

• automation through rules
• tagging emails, anaylics behind them
• support, chat always responds right away

Incentivized

• Email to case is an interesting piece of it. The threading is very strong, sometimes too strong, but it does very well at handling the incoming emails.
• The omnichannel routing, using skill-based routing is really effective.
• Pathing. So making the workflow and helping the team understand what it is that they're trying to do, what they have to accomplish, those step-by-step pieces. That's really helpful.

Incentivized

• It could be considered expensive, but ultimately worth every penny for those who use shared inboxes/groups to run their business.

Incentivized

• We had a principle initially to try and use Omni as much as we can from the user experience perspective, but have found that fairly restrictive. It was very difficult to actually get the right customer experience and customer engagement going. So we're actually on a journey at the moment to replace all of our Omni with Lightning web components that gives us that flexibility. That's probably one area where we've had some challenges in terms of how we've used the product out of the box.

Incentivized

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.

Easy to use

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.

Incentivized

Working on an application that caters to customer needs requires a platform that acts as a mediator between the actual person and the client. This mediator handles the customer and resolves many of their doubts, helps them map through the entire process, and automates the processes. Such a platform is Salesforce Service Cloud. For queries that cannot be serviced by the platform, it creates a separate ServiceNow ticket for us, and it is assigned.

Incentivized

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

Incentivized

Support is there, can be slow at times.

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.

Incentivized

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.

Incentivized

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

Incentivized

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.

Incentivized

We selected this product because we already had some competencies in Salesforce. We own a Salesforce partner with expertise in this area, and on top of that, Salesforce purchased it — it was originally called Velocity. When Salesforce decided to acquire it, that finalized the decision for us.

Incentivized

The product has scaled up with our company growth just fine. No issues here other than slowness in clicking around and running reports

Incentivized

• 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

Incentivized

• We have cut our service team in half over the past 5 years due to the efficiency of the tool
• The amount of direct inquiries to our technical team is less than 10% compared to the number support tickets that get entered in the system for them to work in a more organized manner
• Responses are 100% more timely because tickets can be responded to by any individual in the queue or on the team, as opposed to direct emails to just one person

Incentivized