Your AI Chatbot

First run and account setup

Opening Your AI Chatbot for the first time presents a login screen that asks for an email address and a password. The registration process is straightforward: enter an email, create a password, and confirm. The app then asks for a name and a company name. These fields are optional but recommended. After registration, the app requests permission to access the device's storage. This is required for uploading documents. The app does not explain why it needs this permission, which can be confusing. Once the permissions are granted, the main dashboard loads. This dashboard shows a menu with options like "Create Bot," "My Bots," "Integrations," and "Settings." The interface is clean but sparse. There is no tutorial or walkthrough. New users must explore on their own. The "Create Bot" button is the most prominent feature. Tapping it opens a wizard that guides the user through the bot creation process. The first step is to name the bot. The second step is to choose a knowledge source: upload documents, link a website, or add FAQs. The third step is to configure the bot's behavior: set the tone, define guardrails, and choose the AI model. The fourth step is to deploy the bot to channels like WhatsApp, Telegram, or a website. The entire setup process takes about five minutes, assuming the documents upload without issues.

For users who want to customize further, the app offers an "AI Studio" section. This allows creating advanced workflows with intents, scenarios, blocks, and steps. The studio is more complex, with a visual drag-and-drop interface. Users can define conditional logic, API calls, and human handoff rules. The studio is powerful but has a steeper learning curve. The app does not provide clear guidance on how to use these advanced features. New users often have to refer to the helpdesk or blog for tutorials. This lack of in-app guidance is a common complaint among users who want to build complex bots.

When no-code builder meets multi-channel deployment

The app's core value is enabling users to build AI chatbots without coding. The no-code builder is the primary tool for this. A user can upload documents, link a website, or add FAQs to create a knowledge base. The app then trains a GPT-powered model on this data. Once trained, the bot can answer questions based on the knowledge base. This works well when the knowledge base is well-structured and comprehensive. However, the real test comes when a user wants to deploy the bot across multiple channels simultaneously. Suppose a user builds a bot for customer support and wants to deploy it on their website, WhatsApp, and Telegram. The app allows this with a few clicks. The bot is deployed to all channels at once. In theory, this is seamless. In practice, problems arise when the bot behaves differently across channels. Some users have reported that the bot responds correctly on the website but fails to understand queries on WhatsApp. This is likely due to differences in how each channel handles messages. The app does not provide a way to test channel-specific behavior. Users are left to discover issues after deployment. This clash between the no-code builder and multi-channel deployment creates a frustrating experience. The app does not offer a preview mode for each channel. Users cannot see how the bot will look and behave on WhatsApp before going live.

Furthermore, the app's handling of human handoff is also problematic. The app allows setting up rules for escalating complex queries to human agents. However, the handoff process is not always smooth. Some users have reported that the bot fails to transfer the conversation context to the human agent. The human agent receives the query but has no history of the conversation. This forces the agent to ask the user to repeat information, which defeats the purpose of the handoff. This is a design flaw that is not apparent from reading the Play Store description. The original analysis here is that the app's architecture treats the no-code builder and multi-channel deployment as separate modules. They are integrated at the UI level, but the backend synchronization is weak. When one module fails, the other does not compensate. This is a significant limitation for users who need consistent performance across channels.

Real-world performance and common issues

User reports from various platforms paint a mixed picture of the app's stability. Some users praise the app for its ease of use and the ability to build a chatbot without coding. They appreciate the variety of integration options and the responsive interface. The app's mission to automate customer support is also a positive factor for many users. However, others report persistent issues with app stability. Several users have complained that the app crashes or displays "request expired" errors when sending messages. This is a significant problem because it prevents users from using the bot effectively. The app does not provide a way to report crashes directly. Users have to contact customer service, which is often unresponsive. Some users have reported that customer service is the worst they have ever experienced. This erodes trust in the platform.

Another issue is the app's handling of knowledge base updates. Some users have complained that the bot does not reflect changes made to the knowledge base immediately. The app requires a manual retraining process, which can take several minutes. During this time, the bot continues to provide outdated responses. The app does not provide a way to schedule retraining or to check the status of the training process. Users are left guessing when the updates will take effect. The app also has occasional issues with language support. While the app claims to support 100+ languages, some users have reported that the bot struggles with less common languages. The translations are not always accurate, and the bot may default to English. This is a problem for users who operate in multilingual markets. On the positive side, the app's push notifications for new messages work reliably. Users receive alerts when a customer sends a message. However, the notification settings are not customizable, which can be annoying for users who want to control what they receive.

Storage permission and the changelog

The app requires storage permission to upload documents. This is stated clearly during installation. However, the app does not explain why it needs this permission. Users are left to guess. The developer's changelog for the current version simply states: "New Updates: - Bug Fixes - UI Improvements". No specific bugs are named. No performance metrics are provided.