Azure Bot Service (Microsoft Bot Framework) vs. Genesys DX (discontinued)

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 relationship building with the entire team at LMI from Sales, to the Account Manager to our Customer Relationship manager and their product Bold360 was excellent. They were always willing to listen to different ideas and try to make them work for us

Incentivized

• Real-time communication.
• Lightweight software protocols.

Incentivized

• We’ve built our environment to scale globally and currently leveraging the platform in U.S., LATAM, BRAZIL, APAC, and EMEA.
• Email integration with Outlook has helped channel emails to agents by skill set.
• The knowledgebase has shared global articles, which are auto-translated to our fans who engage our brands based on their questions.
• I want to add kudos to the support received from our Customer Success Manager and Technical Account Manager.

• 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.

• Reporting capabilities. I think the dashboard and reporting tool could contain more details in terms of what data is visible and available to the user/administrator.
• Native mobile applications to provide added support.
• Improving the beta testing program to use new features before understanding whether the update can be pushed out without causing issues with the end-user.

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

Day-to-day use of Bold360 AI (chatbot) use (reviewing new questions, adding new responses, tagging, etc.) is fairly simple, but utilizing more advanced features and custom channeling, etc. typically require escalation to developers and may require additional costs if you want help to implement

Incentivized

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

Great customer support management provided by LogMeIn, which gives you a direct line with regular meetings with the company to make sure your implementation is a success. [The] account manager is always readily available as well for engagement. Opportunities though exist in a balance between professional services support and VIP support that can be improved upon more.

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

I used LivePerson in my previous company. It was the same as BoldChat in terms of being a standalone chat application. But when I started using Bold360, for the very first time I felt I'd found a tool that made chat a really good channel for communications.

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.

• Considerable saving on ticket deflection so return on investment
• Saved on extra support engineer recruitment through self service
• Enabled support engineers to concentrate on more complex customer issues as simple and semi-complex issues are generally dealt with through self service--so better quality of service for customers