FAQs

BotCore has support for multilingual scenarios. We understand the enterprise needs when it comes to supporting multilingual capability. Hence, we support machine translation, human translation and a hybrid model with human translation content taking the precedence where available. This means that the chatbots use the human translated content as the first priority and if the human translation is not available, we provide machine translation as a fallback mechanism.

BotCore is a middleware platform for building enterprise chatbots. BotCore is a platform built on the top of the cognitive service providers (not as a replacement).BotCore has a cognitive abstraction layer which allows enterprises to choose the service provider for cognitive services like text, speech, vision etc. Acuvate believes that there is a lot research going on in this space and enterprises should have the capability to be able to plug into different cognitive service providers without any interruption to the chatbot for the end users.

Most of the cognitive service providers provide chatbot features like NLP, bot messaging channels etc which are good for creating chatbots. However they do not provide the enterprise readiness. BotCore as a middleware platform provides the necessary features that enterprise bots namely:

• Authentication and Authorization
• Security
• Context handling
• Integrations with LoB applications

Acuvate has created knowledge bases (called domains) for their ready to deploy bot personas. We will provide this information along with BotCore deployment. BotCore provides administrative interface for customers to be able enhance the knowledge base on their own. There will not be any development effort for the same.

Couldn’t find answers to your questions here? Request for Demo now!

We strongly believe that chatbots evolve to be a stronger as time and usage increases. BotCore provides a comprehensive set of features to ensure that chatbot administrators have a full control over the behavior of the bot. Following are some of the key features around error handling, untrained response handling, adoption measurement.

• Error Logs
• Zero Intent Logs
• Success Dashboards
• Chat Logs

We have 2 options available for the deployment; Cloud and On- Premise. Cloud deployment can be carried out by using Microsoft Azure/ Amazon Web Services (AWS) . On-Premise will be carried out using your private servers.

The detailed description of these features is available here

Yes, you will be getting BotCore along with the ready to deploy Bot personal like IT Helpdesk bot or Intranet bot.
Customer will be able to use BotCore for that respective persona for unlimited users and trainings. However, customer would not be able to use the same BotCore instance for new / other Bots unless there is an explicit agreement to that respect with Acuvate.

Most of the chatbots deployed for our customers have started with a PoC phase where we have worked with the customer closely and created a PoC chatbot. We generally consider this phase as a chatbot trial phase. We offer BotCore as part of the PoC implementation for customer to get the full experience of the BotCore features.

BotCore provides support for a number of conversational channels across text chat, voice and custom channels.

Couldn’t find answers to your questions here? Request for Demo now!

There is no limit to the number of users that can chat with your bot. You have full administrative control to define supported AD domains, users and authorization. However, the license does not allow implementation of new / other bots by default.

No! There is no limit to the number of questions that a user can ask the bot 🙂.

BotCore supports both on-premise deployment as well as cloud deployment.

For the live implementation, we recommend planning and design of the bot for rollout in different phases. Bot implementation should use Agile methodology like Acuvate’s BDLC (Bot Development Lifecycle) Framework.

The execution approach primarily considers sprint based approach. Each sprint duration to be in the range of 4 to 5 weeks. A typical 4-week sprint looks like below: Couldn’t find answers to your questions here ? Request for Demo now!