1. Home
  2. Chatbot Platforms
  3. Azure Bot Service (Microsoft Bot Framework) Reviews
  4. User Review of Azure Bot Service (Microsoft Bot Framework)
Azure Bot Service (Microsoft Bot Framework)
April 21, 2022

Azure Bot Service (Microsoft Bot Framework)

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Azure Bot Service (Microsoft Bot Framework)

It is utilized as a tagging framework, which clients use to depict our items and survey them as well as hold up any objections they have. It helps with Insurance Contract Request Synchronization Flow.
  • Assembles conversational AI encounters for our clients
  • Adds regular language, discourse, and vision
  • Sends to well known channels with insignificant code changes
  • It isn't exceptionally easy to use for individuals who don't know SDK execution
  • Less choices for other structure mix
  • Customization is tedious and somewhat severe
  • 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.
They provide instructional meetings, manuals, and backing staff, in addition to other things. Bugs were handily spotted and fixed, which is one of my annoyances about issues.

Do you think Azure Bot Service (Microsoft Bot Framework) delivers good value for the price?

Yes

Are you happy with Azure Bot Service (Microsoft Bot Framework)'s feature set?

Yes

Did Azure Bot Service (Microsoft Bot Framework) live up to sales and marketing promises?

Yes

Did implementation of Azure Bot Service (Microsoft Bot Framework) go as expected?

Yes

Would you buy Azure Bot Service (Microsoft Bot Framework) again?

Yes

Microsoft Azure Cloud Bot Service is completely viable and has security highlights. Focusing on the rationale of business rather than the points of interest of every messenger is more significant. We have no issues utilizing the bot structure on the grounds that the execution is fantastic.
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.