Livefyre was acquired in 2016 and became part of the Adobe Experience Manager suite of products. The product has since been discontinued, and is no longer available for sale.
N/A
Salesforce Agentforce Service
Score 8.6 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
Livefyre (discontinued)
Salesforce Agentforce Service
Editions & Modules
No answers on this topic
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
Livefyre (discontinued)
Salesforce Agentforce Service
Free Trial
No
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Livefyre (discontinued)
Salesforce Agentforce Service
Features
Livefyre (discontinued)
Salesforce Agentforce Service
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Livefyre (discontinued)
-
Ratings
Salesforce Agentforce Service
8.2
81 Ratings
0% below category average
Organize and prioritize service tickets
00 Ratings
8.579 Ratings
Expert directory
00 Ratings
8.057 Ratings
Subscription-based notifications
00 Ratings
8.467 Ratings
ITSM collaboration and documentation
00 Ratings
7.462 Ratings
Ticket creation and submission
00 Ratings
8.879 Ratings
Ticket response
00 Ratings
8.278 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
Livefyre (discontinued)
-
Ratings
Salesforce Agentforce Service
8.7
76 Ratings
8% above category average
External knowledge base
00 Ratings
8.567 Ratings
Internal knowledge base
00 Ratings
8.874 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
I was strictly the implementor of Livefyre (for my company only). That task alone was at least 3 weeks worth of work. From a user standpoint, Livefyre is a good product which is why this review is strictly about how difficult it was to implement. Therefore, if a colleague was to ask me if I recommend Livefyre, it's not a straight answer. Questions like, 'how fast do you need it?', 'how centralized is your user database?', 'do you want social login?', all come into question and were details that made my job not easy (hence, my review of 5/10 for suggesting it to others). Once implemented, Livefyre is a great product (notice my overall review is higher), but based on my experience with implementation, it certainly requires a senior developer's dedicated time and patience to set up exactly as desired. For smaller companies with small/simple user bases and websites, the process may be more straightforward, but from my experience, it wasn't out-of-the-box at all.
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.
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.
Implementation was not easy. Although flexible, I personally wrote at least 1,400 lines of code to get this implemented over a few week's time.
The social login aspect is cool, but again, hard to implement. They did not write any of those modules, although they could have. This required senior-level developmental skills and a knowledge of how social media is interfaced with programmatically. Lots of questions arose from this and it was difficult to implement with virtually no help from Livefyre, other than to provide the hooks into their system for when users were validated. I had to write at least 2 separate login/redirection scripts to accomplish this flow.
CSS tweaking was tricky. We could override lots of common CSS classes, but to get things just the way we wanted it, I ended up writing LOTS of jQuery listeners and functions to transform the output into exactly what we wanted. This was a surprise since the software was sold to us as being 'fully customizable'.
Documentation was sufficient, but not great. Getting the flow of the callbacks that are fired wasn't clear at first, and sometimes did not work as expected.
It should be noted that, after this review was published, Livefyre contacted me stating they now have better documentation and process for implementation (for version V3, specifically) and urged me to revise this review. However, I can only write of my experience with V2, and it WAS difficult to implement over 3 weeks of dedicated time. Another developer on my team implemented version V3 and his evaluation is very similar to mine, claiming much difficulty with the CSS customization.
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.
We feel we have a real partnership with Livefyre and we both make each other better. Their customer service has been phenomenal even during a time of rapid growth.
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.
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.
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
We felt Livefyre was more innovative and better at SEO. It felt like we were working with a partner for the long haul who was interested in our business and how to improve it.
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.
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