Azure AI Bot Service vs. Workativ Assistant

Azure AI Bot service works well if you need to support multiple channels like MS Teams, Slack, Facebook Messenger, etc., using the same code base. It also provides built-in connectors to LUIS and Azure OpenAI for natural language understanding and intelligence. Scenarios such as a low-cost chatbot without the need for LUIS or AI are the ones where Azure AI bot service might not be most appropriate.

Incentivized

Workativ has saved a lot of time. Their automation offerings are endless and allow us (the IT team) to spend more time on other projects. Workativ was our last piece of the puzzle that allows us to setup new starters to the business without any physical IT setup.

Incentivized

• Assembles conversational AI encounters for our clients
• Adds regular language, discourse, and vision
• Sends to well known channels with insignificant code changes

• Automation
• Connects to many applications
• Save time

Incentivized

• Limited Natural Language Understanding, especially in entertainment contexts where slang, humor
• Works only with Azure platform only not compatible with other platforms
• Complex customization as per organization need

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

Microsoft offers robust support without a high amount of extra cost to add this product on into our existing support contract. No new onsite personnel as required and training sessions and manuals were included. Very fast response and problem resolution were made available. Detailed configuration guidance was provided at no extra cost. Patching was a bit too frequent.

Incentivized

Azure Bot Services is part of Azure subscription so it is ideal to have apps working [on] one platform so as to manage resources effectively.

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

• Saved time which allows IT hours to be used elsewhere

Incentivized