To manage multiple bots in a single account, you can follow these steps:

1. Create custom fields: Create a custom field in your chatbot account that allows you to store the "current bot" or "current brain" being used. This will allow you to easily switch between the different bots.

2. Set the current bot: When the user enters, set the value of the "current bot" custom field according to the bot the user wants to use. You can do this through an action in your conversation flow.

3. Condition the bot logic: In your conversation flow, use conditionals to check the value of the "current bot" field and redirect the user to the logic corresponding to each bot.

4. Provide a way to switch bots: Add options or actions that allow the user to easily switch between the different available bots. This can be through buttons, dropdown menus, or even text commands.

5. Maintain consistency: Ensure you use consistent naming and organization for your different bots, so that it is easy for you and your users to navigate between them.

6. Consider the user experience: Think about how you can make the transition between bots as smooth and natural as possible for your users. Avoid making the process confusing or frustrating.

7. Test and refine: Thoroughly test your solution to ensure that the switching between bots works correctly. Adjust and refine the process as needed.

Tags are a valid and functional way to manage multiple bots or demos within a single chatbot. Some of their advantages are:

• Tangibility: Tags are something concrete that can be easily visualized and assigned, which facilitates mental organization.
• Simplicity: For chatbots with few demos (2-5), tags can be a simple and effective solution.

However, they also have some disadvantages:

• Scalability: As more demos are added, managing tags can become laborious and unmanageable.
• Exclusivity: A user can only have one tag assigned at a time, which can cause problems if they want to access multiple demos.
• Maintenance: Care must be taken to remove tags when the user exits a demo, to avoid them getting "stuck" in a specific demo.

In general, tags are a good option for chatbots with few demos, but as complexity increases, they can present limitations. Other alternatives, such as the use of custom fields, may be more scalable and flexible for managing multiple bots or demos within a single chatbot.

To handle multiple bots within a single membership, you can use the custom fields functionality in Openi. This allows you to dynamically switch between different "brains" or demos of the chatbot without having to manually switch between them.

The strategy consists of:

1. Creating a custom field called "current demo" or "current brain" to store the value of the demo or brain being used at that moment.

2. Using conditionals in the main chatbot flow to redirect the user to the corresponding demo based on the value of the custom field.

3. Adding actions to set the value of the custom field when the user requests to change the demo.

4. Optionally, using entry point links to allow the user to directly access a specific demo.

In this way, you can have a default response that detects the current demo and redirects the user to the corresponding flow, without having to manually switch between them. This facilitates the management of multiple demos or brains within a single chatbot.

To switch between different bots or "brains" within a single chatbot, you can use the "entry point links" functionality in Openi.

These are the steps to follow:

1. Create a new "entry point link" in the "Settings" > "Integrations" > "AI Triggers or Functions" section.

2. Assign a descriptive name to the link, for example "Car Demo".

3. In the description, explain that this link allows the user to try the chatbot demo for car agencies or vehicles.

4. In the action, select "Set custom field" and assign the value "cars" to the "current demo" field. This will save the context of the demo the user wants to try.

5. Save the entry point link.

6. Now, when the user wants to try the car demo, you can share the generated link with them. By clicking on it, the value "cars" will be assigned to the "current demo" field and redirect to the default chatbot flow.

7. Within the default flow, you can add a condition that checks the value of "current demo" and redirect the user to the corresponding flow for the car demo.

8. Repeat the process to create entry point links for other demos you want to offer, such as a cafe demo.

In this way, you can easily switch between the different "brains" or demos of your chatbot without having to manually modify the value of the "current demo" field.

It is important to avoid the use of keywords to switch between different bots or "brains" within the same chatbot. Some reasons why the use of keywords is not recommended:

1. Lack of flexibility: When using a specific keyword to activate a bot, the user is limited to that form of interaction. This can result in a less natural experience and limit the chatbot's ability to understand the user's context and intentions.

2. Ambiguity issues: There may be situations where a keyword is used naturally in the conversation, without the intention of changing bots. This can cause confusion and errors in the chatbot's logic.

3. Complicated maintenance: As more bots or "brains" are added to the chatbot, maintaining a list of keywords becomes increasingly complex and prone to errors.

Instead, it is recommended to use more flexible and scalable approaches, such as:

1. Custom fields: Using custom fields to track the current "brain" or "demo" of the chatbot. This allows programmatic switching between different bots without relying on keywords.

2. Menus and buttons: Providing the user with clear and visible options to select the bot or "brain" they want to use, instead of depending on keywords.

3. Conditional logic: Implementing conditional logic in the chatbot flow to determine which "brain" or "demo" should be activated based on the context of the conversation.

These more structured and programmatic approaches allow for a smoother user experience and easier maintenance as the chatbot grows and becomes more complex.

In summary, we have learned to create a multi-demo chatbot using different approaches:

1. Tags: Using tags to identify each demo and redirect the user to the corresponding demo. This works well for a limited number of demos, but can become complicated as more are added.

2. Custom fields: Using custom fields to store the current demo. This allows for more flexible and scalable management of multiple demos, as the custom field will always have the most recent value.

3. Entry point links: Using entry point links to directly redirect the user to the desired demo. This enables a smoother transition between demos and avoids the need to keep track of the current demo.

4. Functions and triggers: Implementing functions and triggers to automate the demo switching and custom field updates. This helps keep the chatbot logic organized and easy to maintain.

The choice of approach will depend on the specific needs of your project, the number of demos you want to offer, and the complexity of the interaction. It is important to find a balance between ease of use, scalability, and flexibility.

Remember that as a chatbot builder, you should maintain consistency in your concepts and language to facilitate maintenance and understanding of your chatbot. Additionally, consider the preferences and capabilities of your end users when designing the experience.