In our previous setup, we used a role-based bot to manage different conversation flows and automation rules across your BusinessChat workspace. With the Beta launch of the AI Chatbot, we’ve introduced a smarter, more dynamic conversation experience — but not all components of the role-based bot are replaced just yet. This article explains what’s changing, what stays the same, and how your existing custom flows will continue to work during the Beta period.
Previous Role-Based Bot Features
The role-based bot managed several key areas of automated conversations:
Bot Flow – The main automated conversation logic for handling customer queries.
Operator – The chatbot operator for routing and escalation.
Custom Flow Handling – Automated replies and actions for specific triggers:
Responses to specific campaigns based on quick replies.
Handling welcome series messages.
Responding to satisfaction survey submissions.
Custom replies to Cash on Delivery (COD) confirmations.
Custom replies triggered by Webhook automations.
Opt-out of campaigns by sending the unsubscribe message.
What Changes in Beta
With the Beta release of the AI Chatbot:
The AI Chatbot replaces the Bot Flow — all general customer queries will now be handled by AI, providing more natural and dynamic responses.
The AI Chatbot will not replace the Operator or Custom Flows — these will continue to function as they did before.
What Stays the Same
Operator rules for routing and escalation will continue to work without changes.
Custom Flows tied to campaigns, surveys, COD confirmations, or webhook triggers will keep functioning exactly as they did with the role-based bot.
Your existing automation setup remains intact — only the main Bot Flow is replaced by the AI Chatbot.
What This Means for You
You can continue using your existing custom flows while benefiting from the improved AI-driven conversation handling for general inquiries.
No action is required to maintain your Operator rules or custom automation — they remain active during the Beta.