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.
$25
per month
Pricing
Parature (Discontinued)
Salesforce Service Cloud
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
Parature (Discontinued)
Salesforce Service Cloud
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Parature (Discontinued)
Salesforce Service Cloud
Features
Parature (Discontinued)
Salesforce Service Cloud
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Parature (Discontinued)
-
Ratings
Salesforce Service Cloud
8.8
Ratings
9% above category average
Organize and prioritize service tickets
00 Ratings
9.40 Ratings
Expert directory
00 Ratings
8.50 Ratings
Subscription-based notifications
00 Ratings
8.60 Ratings
ITSM collaboration and documentation
00 Ratings
8.20 Ratings
Ticket creation and submission
00 Ratings
9.30 Ratings
Ticket response
00 Ratings
9.10 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
Parature (Discontinued)
-
Ratings
Salesforce Service Cloud
8.7
Ratings
10% above category average
External knowledge base
00 Ratings
8.40 Ratings
Internal knowledge base
00 Ratings
8.90 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
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