Skip to main content
TrustRadius
Microsoft Parature (Discontinued)

Microsoft Parature (Discontinued)

Overview

What is Microsoft Parature (Discontinued)?

Parature was a self-service customer support platform providing a self-service knowledge base to connect with customers across multiple channels, including email, the web, chat or social media. The company was acquired by Microsoft in January 2014 and reached EOL in…

Read more
Recent Reviews

Decent but not great.

7 out of 10
August 23, 2014
Incentivized
Parature was used as a sole system of record for all our customer support cases, reviews, and feature requests. We used Parature to build …
Continue reading

Parature - meh!

1 out of 10
August 06, 2014
Incentivized
I was using Parature when I was working at Blackboard Inc. The product was used as a CRM for our internal use and then was being used as a …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Microsoft Parature (Discontinued)?

Parature was a self-service customer support platform providing a self-service knowledge base to connect with customers across multiple channels, including email, the web, chat or social media. The company was acquired by Microsoft in January 2014 and reached EOL in 2017. Former users are…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

Alternatives Pricing

N/A
Unavailable
What is Spiceworks Help Desk?

Spiceworks offers a set of free tools for IT network management and help desk support ticketing. The inventory management system essentially provides comprehensive device information for asset management. The Spiceworks Network Monitor provides information on observed IT for problem tracking and…

What is Salesforce Service Cloud?

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.

Return to navigation

Product Details

What is Microsoft Parature (Discontinued)?

Parature was a self-service customer support platform providing a self-service knowledge base to connect with customers across multiple channels, including email, the web, chat or social media. The company was acquired by Microsoft in January 2014 and reached EOL in 2017. Former users are encouraged to migrate to Microsoft Dynamics 365 Customer Service.

Microsoft Parature (Discontinued) Competitors

Microsoft Parature (Discontinued) Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(13)

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 3 out of 10
Vetted Review
Verified User
Incentivized
We previously used Parature for all our customer-facing support needs. Tickets came in via email or our support portal and were created in Parature. Then, a support engineer would triage and assign those tickets depending on the complexity. Ticket-based support allowed us to support more customers in a far more efficient manner than via phone.
  • It's functional. It does what it needs to do without too many excess frills or features.
  • Uptime was generally good and we were usually notified of any planned outages.
  • Reporting is barebones at best. If you need special reports, we had to go through Parature to have them built.
  • The use of frames on a website is very 1990s. It actually impacts usability of the product, especially when combined with how Parature handled sessions. An engineer could only work one ticket at a time which, honestly, isn't very realistic for a busy support team that is working on several issues at a time.
  • Support was often unresponsive when contacted for unplanned problems.
  • The knowledge base was not very friendly for clients and it provided no real encouragement for it to be used.
  • It took several clicks to do something as simple as edit and assign a ticket or to close a ticket.
If you don't need robust do-it-yourself reporting and if you are running a customer service organization that only works one incident at a time, Parature might be a suitable solution for you. If you're a busy office handling multiple issues at a time and if you want real time information about team performance at your fingertips, there are likely better solutions that integrate with sales, marketing, and finance.
  • Parature wasn't a very efficient use of time. It actually caused some slow performance due to the learning curve and inability to have more than one incident open at any given point in time.
At the time, I believe we chose Parature because of pricing. That decision was made before my tenure with the company.
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.
  • Login was simple to use
  • Assigning tickets required multiple mouse clicks, as did closing tickets
  • Use of frames and sessions did not allow us to have multiple support tickets open at any time
  • It was very hard to get useful reporting data from this application
Yes
It was acceptable for looking at tickets, but I would never have wanted to use it to actually provide support to my customers on any frequent level.
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.
Return to navigation