INTRODUCTION:
Makes chatbot menu options configurable so it can easy to maintain without a dev engineer. So we can add/edit existing menu options.
Status |
| |||||||||
Owner | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Contributors | ||||||||||
Approved |
| |||||||||
DecisionOn this page |
|
PENDING
❓ Problem statement
As a solution owner, I would want to deploy menu options faster without having to depend on a release on both portal and WhatsApp with the following details -
Able to change the text
Able to change the menu options (Add/edit/remove)
Able to create new flows/structure such as introducing new menu options which are not there
Able to change answers to queries
Able to add/edit/remove hyperlinks
Able to analyze the data after changes
💡 Research insights
It takes place for any owner can change the menu-driven flow for the chatbot and its full flex change any time without doing code change in a git repository.
📊 Solution hypothesis
It will help with a faster deployment process.
Quick change based on the requirement and easy to deploy.
Any time/ anyone / any flow/menu text can change quickly.
Add/Edit change the text for Menu options.
🌈 Design options
Solution 1 | Solution 2 | ||||
---|---|---|---|---|---|
Overview | Enable load and execute config from was container for chatbot.
| ||||
Link | |||||
Benefits and risks | Easy to maintain, add and modify any time Menu options and query answers. Now its configurable from outside chatbot so its more easier to deploy. Below requirements will satisfy.
TBA | ||||
Criteria | |||||
✅ Follow up
Keep track of the discussion with the following status and steps.
Decision | Status | Next steps | ||||||
---|---|---|---|---|---|---|---|---|
|
| |||||||