Parature was a self-service customer support platform providing a self-service knowledge base to connect with customers across multiple channels. The company was acquired by Microsoft in January 2014 and reached EOL in 2017.
N/A
Salesforce Service Cloud
Score 8.4 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.
Before choosing Parature we reviewed many of the currently available solutions before building our short list of Parature, SugarCRM, Zendesk, Salesforce, and NetSuite. In the end, the licensing models for Salesforce and Netsuite eliminated them from consideration. The SugarCRM …
Parature comes in at just the right blend between ticketing solutions like Ceridian and Remedy. Ceridian is a little too cut-down/simple while Remedy can be mired by its complexity. Parature shares the same features as quite a few other ticketing solutions, but hits strongly in …
I'm currently using Solarwinds Web Help Desk and I think the 2 are very comparable. I didn't select either product but I'd rate Parature at the same level as WHD or better.
Salesforce is so much more intuitive and the layout is so much better. I never had any training nor did I need it with SF and with Parature it was a constant battle to understand its issues. I don't like to feel I have to resort to a manual every time I use the product.
Between SolarWinds and Altiris, I like the advantage that Parature gives. The auto reply is a huge assistance when dealing with people outside of my organization.
I honestly prefer Zendesk to Salesforce Service Cloud. I find that Zendesk is easier to manage both on the support ticket side, as well as the knowledge center side. It looks and feels easier to use than Salesforce Service Cloud. Salesforce Service Cloud is fine, but it is …
Zoho is not very real-time, it has limited integration capabilities, and the UI is not very satisfactory for any incoming customer. The performance is slow and impacts the overall customer journey. The data stored in the backend is slightly scattered and needs to be cleaned …
Salesforce is a really great case management tool. Made things a lot easier for our team. Wanted something fairly simple that had a variety of capabilities we could customize.
We used Salesforce for years, Left for Hubspot, and then came back to Salesforce (SF). As they say, don't fix it if it's not broken. Salesforce and customizing were better for us.
Salesforce Service Cloud offers deep integration with our current and expanding CRM data, along with numerous pre-built features that didn't exist in Kayako when we used it. (We used to use an instance Kayako installed in a private cloud environment.) Salesforce Service Cloud …
Zendesk has it's own challenges in terms of Administrator difficulties and a completely different back-end than Salesforce Service Cloud. I would recommend Salesforce Service Cloud if you need a clean database of Companies and Contacts. Zendesk does not excel in overall CRM …
I'm not at the level where I would be part of the decision making process for choosing a vendor or product for the organization. Every position I've held, I've come into a company that has already implemented or is in the process of implementing Salesforce. Honestly I would not …
All of the software's are well established and good, but what gave the edge to us its easy integration capability with other systems, experience cloud integration and Einstein analytics which made us move forward Salesforce. Salesforce also have better service and industry …
The major value proposition is that service cloud offers integrated services. That covers a multitude of lacking features. All of our agents preferred Freshdesk. Salesforce service cloud was lacking so many basic features compared to it that it was frustrating to switch. Simple …
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 …
We were after a robust and very scalable solution, which could be rapidly implemented. Salesforce Service Cloud not only fitted the bill, but it was much easier to source skills and find on-line learning to help achieve our goals. Although the other technologies could have …
Salesforce allows a lot more visibility and allows us to build better reporting. It is initially trickier to set up and learn, however, comprehensive training and processes have lead to increased customer satisfaction and retention.
Salesforce is lightyears behind Zendesk. You have to be trained as a Salesforce admin to do anything, while Zendesk takes minutes to set up and is actually customer friendly. There are not native telephony options within Salesforce and the tools you use to integrate are …
We previously used a home grown, proprietary system for our needs. This started to get costly and clunky as our database grew. We ended up going with Salesforce because they are purely cloud based. They also have a large footprint and very robust solution so they help us …
Customer Success Support Specialist, EF Corporate Solutions
Chose Salesforce Service Cloud
Well, I worked with SAP in the past when I was in other companies. It was way more complex and not user-friendly. You had to take a lot of steps in order to accomplish simple tasks and not everyone could work at the same time in the same program. I would 100% recommend …
Zendesk changed their agreements making us unable to continue with them due to our agreements with our customers. SalesForce allowed us to maintain our customer agreements.
I used other products in another company as a database and can say that Salesforce Service Cloud is much more user friendly for customer service needs and makes work faster to process than the named program before. Integration between departments is more clear and simple to …
Parature earns a "7" on my rating scale because it fits the bill for a ticketing solution. While it is not the most powerful utility I have come across, it is fairly user friendly and gets the job done. There is quite a bit of room for customizing the interface, but it comes with a learning curve. A score of "7" reflects what I would tell anyone who is looking for feedback on this application; it's better than a majority of the market share, but still has room to grow!
This cloud is a good option for attracting large numbers of customers for mid-scale and large-scale organizations. However, it’s not suitable for small companies or startups due to its high cost. For use cases where real-time input from customers is taken and then processed on the cloud to give them output, this platform is a must.
We left Parature for Salesforce Service Cloud. While Parature was functional, as our business matured we needed better support, more stability, and a lot more features. In addition, it integrated with our sales, marketing, and finance department, allowing us to all use a single solution and be able to share information across departments.
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.
It was bulky, cumbersome, and didn't allow us to handle the volume of cases we received on a daily basis. Many of our issues were highly technical in nature and we would often need to work on 2 or 3 at once. The poor design choices prevented this, which was unfortunate.
I love that the Salesforce Service cloud provides all of the functionality that I need when implementing business processes for our customer support representatives. It even has enough functions and features that allow us to customize and expand upon our current processes, giving us the ability to go above and beyond what we've thought we could ever do. Using cases coupled with Salesforce's automation tools help ease the workload and keeps our data integrity intact.
They recently had one very extended outage. It was a data center issue - but they were not diversified enough so in the end the system was down for almost 8 hours. There are also periods of time where for no reason the system simply doesn't respond. This small outages are usually short (just a few minutes), and have in fact been occurring less often, so it appears some corrective actions have been taken.
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.
Load times can be slow, but this is also based on how much customization you have done. We added a lot of custom fields which could cause additional slowness in loading. This was never anything that affected our overall efficiency. I did not notice that Service Cloud slowed down any of the systems we had it integrated with
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
Before choosing Parature we reviewed many of the currently available solutions before building our short list of Parature, SugarCRM, Zendesk, Salesforce, and NetSuite. In the end, the licensing models for Salesforce and Netsuite eliminated them from consideration. The SugarCRM solution was our current solution, and didn't appear to be a key area of focus for Sugar (though we continue to use SugarCRM for everything except the Ticketing feature). Zendesk lacked the Download Module feature which is a critical element of our deployment. In the end, it was Parature that addressed all of the needs we identified and did so in a single, hosted solution. It was also one of the least expensive to deploy and maintain.
I honestly prefer Zendesk to Salesforce Service Cloud. I find that Zendesk is easier to manage both on the support ticket side, as well as the knowledge center side. It looks and feels easier to use than Salesforce Service Cloud. Salesforce Service Cloud is fine, but it is expensive as well.
Positive: everything is housed in one place, we are paperless and we are efficient.
Negative: the bugs of this product make the above equally as frustrating. Also, some people don't use it correctly and going back and fixing their mistake is time-consuming. The reporting feature are also pretty flawed.
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