Azure Bot Service (Microsoft Bot Framework) vs. LiveChat

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.

We needed a mechanism in place to make contact with visitors to our website easier. What we discovered is that it's an excellent tool for creating reports and dashboards that show how soon issues are handled. Our website can now be updated in real-time, and all of our internal teams are really excited to use this fantastic technology. I really recommend [LiveChat] to many friends and past colleagues.

Incentivized

• Real-time communication.
• Lightweight software protocols.

Incentivized

• The most important factor of Livechat is their own chat support, I had many requirement from the Sales Head, Support Head to implement features that I was unsure if the product could do. However, as I did the implementation one by one I constantly used the chat support which helped me step by step all the way.
• The UX of the product is pretty simple and intuitive to use. There are quite a few features that we could easily plug and play. We tried going to the market to find a solution that could help us but they did not have as many out of the box features and simple to use
• Their integration between LiveChat and Chatbot is pretty seamless and since both of them are from the same company, it's works pretty well.

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.

• It has a limited amount of agents, so when you have many customer care employees during one shift it is hard to manage the quantity of active agents.
• When system is overloaded and many customers are waiting in a queue it starts to works slowly (sometimes the program even lags) and you need to refresh the system to write a message.
• Occasionally when you open a new tab, you might lose your current conversation.

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

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

The only issues I have had with LiveChat are the technical glitches within the program. These are not common as in everyday occurrences but when the glitches do happen they tend to have very negative repercussions. This is due to chats with customers being dropped, this may be an internal server issue though and may not happen for everyone.

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

Overall very similar in design, but LiveChat had a better interface, better reporting and analytic tools, better mobile support, and just an easier overall feel. The two products are very much alike in the vast majority of ways, but I ended up preferring this product overall. Price points were similar as well, as well as the allowed number of users.

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.

• We have a small team so the overall impact is that it is easy for one or two employees to handle a large number of tickets without hiring more people. Plus, you can use this software remotely, save a ton on traveling to and from and office.

Incentivized