How to Design a Bot: Phases 3 & 4 / Final Design and Launch
Written by Susan Dileep
Updated on June 23rd, 2022
- Getting Started
- Bot Building
- Conversation Design
-
Developer Guides
Code Step Integration Static Step Integration Shopify Integration SETU Integration Exotel Integration CIBIL integration Freshdesk KMS Integration PayU Integration Zendesk Guide Integration Twilio Integration Razorpay Integration LeadSquared Integration USU(Unymira) Integration Helo(VivaConnect) Integration Salesforce KMS Integration Stripe Integration PayPal Integration CleverTap Integration Fynd Integration HubSpot Integration Magento Integration WooCommerce Integration Microsoft Dynamics 365 Integration
- Deployment
- Agent Setup
- Analytics & Reporting
- Proactive Messaging
- Commerce Plus
- Troubleshooting Guides
- Release Notes
Final Design and Launch
Step 4: Architecture Discussion
- At this stage, the V3 of the design has been approved and you can move on to the next step – architecture discussion.
- An architecture discussion would involve the team lead or Program Manager taking the analysts, and engineers on the team through the detailed V3 flow. This step is done to ensure the design is technically feasible.
- The team has to ensure that the APIs they have or have received from the business match the design outcomes.
Tip: Any discrepancy in the API information should be raised with the team or business at this stage.
Step 5: Development
- Once the bot development is complete, the conversation designer should test the bot to provide feedback.
- The team lead or Program Manager will use the V3 of the design as a guide to building the IVA.
- The PM will also refer to the V3 of the design before UAT to ensure core design decisions are not missed out. In case of any deviations needed as per the business, the V3 of the design should be updated in consultation with the conversation designer.
Step 6: User Acceptance Testing or UAT
- UAT or User Acceptance Testing is the final stage of bot development. At this stage, the bot is tested by the end-user or business before being approved for release.
- A QA tests all the scenarios in a use case to ensure that the bot is functional in a real-world scenario. If you are a Conversation Designer, you could conduct your own UAT to test how the conversation plays out with users.
- UAT also allows QAs to raise bugs which can then be addressed by the development team or even the CD if it pertains to content.
Tip: Set up a focus group of internal stakeholders or prospective users to gather user feedback or issues and understand how they navigate the chatbot. This is one way to ensure the bot is usable. You could also use the Wizard of Oz technique to test your bot and understand its limitations or where the bot fails to answer a user.
Step 7: Launch and UX Retro
The testing on the bot is now complete and you are ready to launch your bot to all your users. Ensure you have access to the analytics dashboard on the bot building platform to track user behavior, user questions, and other such data that will help you improve the bot experience.
Once the bot is launched, it is important to conduct a bot retrospective or bot retro to understand the functionality of the bot and what needs to be improved upon. You can achieve this by mining through data in the analytics dashboard and making minor changes in the design or the content of the bot.
Watch: A summary of how to design a bot and the project lifecycle.
