Avaya Contact Center vs. MindTouch

I would say well-suited for the everyday user, with the ability to use the products. I think it's really user-friendly in that way. The lack of education for the end users, maybe through some of our companies, makes it difficult. And the turnover.

Incentivized

If a company doesn't want to make their knowledge base public-facing, you lose a lot of the value of using MindTouch in a closed environment. MindTouch is not ideal for extremely structured content management scenarios that are strong DITA advocates. Companies that require localization might not be good fits either.

Incentivized

• The app and the ability to use the "office" phone while on the road.
• There's an easy implementation and training process to get everyone on board quickly.
• Flexibility of transferring calls to different mediums - I can switch a phone call to a conference or patch in other parties with ease.

Incentivized

• MindTouch helps to easily organize our help articles to ensure that our end user is receiving the proper information.
• The MindTouch platform is extremely easy to navigate which reduces the turnaround time for our team to publish new material.
• The editor tools supplied through MindTouch make styling our documentation a breeze.
• The contextual help tool allows our customers to consume documentation based on the page they are viewing in our platform.

Incentivized

• Calls are automatically terminated at an agent and do not allow for the agent to "manually" answer the incoming call. This is very problematic as agents are not able to prepare properly for incoming calls. In addition, agents have stepped away from their desks and forgotten to put themselves in an away status, and calls have been directed to them, and they just sit there with no agent present. This is a very undesirable feature of the system.
• Password resets are extremely problematic and continuously cause problems for users. Agents are prompted to change their password upon expiry, and when they follow the instructions as outlined, it rarely works and ends up needing a full reset. The challenge questions are useless and do not work at all.
• Support can be a bit challenging as there are definite language barriers that have made both explaining the problem and understanding the recommended solution difficult.
• The system is sometimes unreliable and will randomly log agents out with no explanation. Agents are then advised by support to log out, clear cache, and log back in. This is not feasible in a busy call center.

Incentivized

• When we do have a support issue, we frequently need to go through multiple people, contacts, ways of explaining things, etc,. before someone on their end actually understands our problem. It's rare that the first person we talk to understands the big picture or appreciates our use case.
• The draft functionality is a promising start but lacks some key features that cause us regular frustration. For example, you can only create one draft of a page at a time. This is fine if changes come to you in perfect sequential order, but it makes it impossible for us to update a live page while a draft exists. More specifically, if we're working on updating content on a page for a new feature being released next month, but then we notice a typo today, we can't fix the typo in production without first deleting the draft or doing some hacky workaround of temporarily copying/pasting the source HTML of the draft page and saving it someplace else.
• Existence of, or integration with, true source control would be a huge win, but it's something currently lacking in the product. MindTouch's content reuse feature is helpful in the right situations, but it's not robust enough to scale well for lots of content.
• Version history of page changes is not 100% reliable. Sometimes items don't show up at all or there is a delay before the diff is visible. Also, creating a draft does not register at all in the page version history.
• In-site search is poor, unless you know the *exact* title of what you're looking for. We tell our customers to use Google, not the MindTouch search. Google is excellent at searching our MindTouch site.

Incentivized

I am really not the decision maker on this subject but given the cost of the investment in Avaya, I do not see the company not renewing the use of Avaya. The new licensing model no longer requires expensive upgrades to stay current with new features added to the system and really helps with the cost of investment.

Incentivized

We've put lots and lots of content into the MindTouch system, of course, so that makes it harder to opt out, but we're also very pleased with their rate of development and weekly pushing of improvements, as well as their response and solutions to our questions and input All in all, a winning combination.

Incentivized

Avaya has versatility in calling, receiving, and configuring. Being able to have notion of location, exchange of messages. we could see supplier information and configure it to our liking. as it is practicality for configuration and manual handling. Interactive and easy to learn screen. Being able to generate call reports for analysis of service in others

Incentivized

The site is responsive across multiple devices and screens. It has a clear path to contact support. The articles are searchable. Site users do have trouble navigating the site and finding what they need. That may be due to the architecture of the site, but it'd be nice if MindTouch offered more solutions are this. Our content is organized by product line. And many of those product lines have overlapping training content, so we have extensive duplicate content.

Incentivized

MindTouch is a hosted site, so as a heavy user there are times when I notice that pages are slow to load, or something happens like Amazon Web Services crashing the entire east coast for a few hours, that you do notice even if it isn't actually the fault of the MT tool itself. It's the risk of using a hosted tool, but the benefits are pretty amazing and outweigh these performance issues.

Incentivized

I give it this rating because the support services of Avaya have proven to be reliable when needed. Great feedback for our queries has always been received from the support agents. 24/7 availability of support, which is very essential as our Call Center department also functions this way, therefore, the knowledge and technical support we require is always available to us.

It's good. Pretty solid. We got a lot of input to get up and running, but did a lot of the setup and customization work ourselves, because of our high standards. We've gotten good response and results on specific projects related to customization and our CSM is also pretty responsive. Overall, I think that the jobs of CSMs and support folks would be easier if the product weren't wonky in some ways. They seem to have to do more "workarounds" for basic functionality that should just work out of the box

Incentivized

Written documentation and videos are very good and have helped on numerous occasions when I've had to look up how to accomplish a certain task. The reason I have not given a full score is mainly because there have been some inaccuracies in the documentation because updates to the MindTouch framework have slightly changed the way things work. But this is usually the same type of challenges I face when making documentation for the software solution we develop. So all in all I'm very satisfied with both the personal webinars and the online documentation MindTouch provides for their service.

Incentivized

No, everything was implemented by Avaya Support

Incentivized

Just know that there is so much more involved than adding your content. There are so many pieces to launching your site -- especially if you are moving from another platform. If you are not a person who typically works in the "website" realm, do your homework, ask your web people, engineers, etc., because there's a lot to do that you won't know about until you are unexpectedly smacked in the face with it. Learn from my mistakes! We are very happy now, but it was a long road getting to launch day for us

Incentivized

Switched from Polycom to Avaya, although polycom worked well there were too many reoccuring connectivity issues and the turn around time for solving them was also too long. Avaya has fewer connectivity problems and their support is much better too. Pricing wise they were similar so we didn't have much to lose.

Incentivized

I will be brief. DealerTeam is built upon Salesforce and we try to support native apps. We used Desk.com first for basic Help Ticket management. The product did not satisfy how our customers were looking for information. We upgraded to Service Cloud with Knowledge Base and spent one year writing content and developing our support agency. Again, our customers were upset about submitting help tickets and waiting for answers. They wanted access to self-help while working with a customer. Today we continue to use Service Cloud with MindTouch integration and have found complete success. There is simply no other solution I know of that is a flexible and easy to use as MindTouch when it come to providing customer success and product support

Incentivized

We tried to migrate to MindTouch for 5 months and failed, remained with Zendesk

Incentivized

• Overall from a business objective standpoint, Avaya has to have had a positive impact on our Return on Investment. Its use in day-to-day operations has been beneficial to not only the company, but the business as well.
• Using the Avaya soft phones supplies a business or company a way to limit expenditures on the hard phones by allowing the use of Avaya soft phones. The equipment is no longer needed, save for headsets to be used with the application itself.
• Business objectives have to be just that, objectives. Economics begs for ways for a company to limit expenditures that may see little or no return. Avaya has tackled this issue and won!

Incentivized

• Our operational efficiently has improved significantly. Prior to Mindtouch, we managing duplicate content in two separate authoring solutions. Delivering content predictably and consistently was difficult and stressful for writers. In Mindtouch, we were able to optimize our content (remove redundancies) giving us more time to test, review, and improve content quality.
• Traffic to our knowledge center is increasing monthly.
• Internally, SMEs and customer-facing teams are recognizing the value Mindtouch brings through self-service knowledge. These SMEs want to contribute more to content, either as contributing writers or collaborators with tech writers.

Incentivized