Avaya Experience Platform vs. Azure Bot Service (Microsoft Bot Framework)

The Avaya Experience Platform is well suited to allow remote working for call center agents. Staff can log in and work from anywhere using Chrome and their user credentials. The technical issues and lack of some features have caused some frustration for our staff and made it difficult to get buy-in for this product across all call center groups. This is difficult because a solution like this is intended to make their work more efficient as opposed to causing frustration.

Incentivized

It is suited for applications like computerizing messages, or any business thought that would require the entrepreneur to robotize their reactions, particularly assuming they are managing a ton of clients and they can't answer to every single one of them. It'd be the most ideal to computerize messages of enormous associations where the reactions measure up to the clients' assumptions. It would be less appropriate in associations where clients' viewpoints matter and every client is interesting and requires the association's consideration, where the specialist organization doesn't need to sum up the clients' interests.

• 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

• Real-time communication.
• Lightweight software protocols.

Incentivized

• One are for improvement for Avaya is the ability to operate behind the VPN. For the virtual employee, this is an issue as we are unable to use it behind the VPN and it must be launched from the remote desktop.
• The color scheme could definitely use some updating. The charcoal gray background of Avaya's windows, coupled with the black font is not very contrasting. I have used Avaya for years and would love to see an update as to its color scheme to better fit the virtual employee.
• Avaya could also improve the way an employee moves within the program by titling the icons seen or expanding the Avaya window to allow for a better understanding of what each con does. For example, the Work History window would go unnoticed, had I not been playing with the software one day. These little items are unknown to many professionals in my industry as they sit in the window with no explanation.

Incentivized

• They have simplified the coding for the bot in Azure, but it would help if the coding was further simplified so that non-IT can operate [and] create it easily.

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

Very Easy to use and Intuitive. Reporting and Graphical user inferface suport the latest browsers and that fact it integrated and complements existing customer experience platform make it easy to bring over into the environment. Finally, the fact it is all in the cloud, no issues running updates, upgrades, or things of that nature that would slow the service.

Incentivized

Azure Bot Service provides an integrated environment for bot development. Microsoft Azure Cloud is fully compatible and its security features. It's more important to pay attention to the logic of business than the specifics of each messenger. We don't have any issues using the bot framework because the implementation is excellent.

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.

Support is helpful when we have a problem, but online documentation is lacking

No, everything was implemented by Avaya Support

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

Microsoft Bot Framework is much better and well more established without a lot of proprietary software/coding language. Lex is very limited with integration with standard hardware and network configurations. Lex has performance issues and was too slow to meet near real-time collaboration requirements. Bot Framework complements many other Microsoft communication products and this was key to implementing without a lot of new training required.

Incentivized

• It does what we need it to do, so we don't heavily invest in this technology but rather into the manufacturing end of our business.
• We believe we have more than achieved the return on our investment for the Avaya phone system and associated equipment.

Incentivized

• Interfaces with the SQL data set, tracks down plans/replies, and tests them with the SDK.
• Utilizing the system is made conceivable by the Bot Dev gateway. We can interface our bot in excess of ten channels, including Twilio Facebook, Twilio, Twilio, and Slack, and that's only the tip of the iceberg.
• It is expensive.