> For the complete documentation index, see [llms.txt](https://docs.chatlayer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chatlayer.ai/buildabot/tips-and-best-practices/frequently-asked-questions.md). # Connect two bots to each other ## Is it possible to connect two bots to each other? In general, our advice is to try to centralize as much information within one bot, as long as the target audience & broad use case for that bot remains the same. However, if for whichever reason, it is important of having two bots talking to the user within the same conversation, there are a few possibilities for achieving this. * If you use the chatlayer web widget you could send an 'event' to the web application to indicate that the user should be connected to another bot. This is only possible with the Web & Webhook channel. * Option 2 is to use the Webhook channel, however this requires some custom implementation. In this case you could host a proxy service that feeds messages from the different channels to Chatlayer.ai. In this proxy service you can decide per incoming message at which bot you want to ask for an answer. Option 2 is a more advanced use case, and therefore not very common, but there are some bots within our platform that work this way. There is currently no out of the box solution that allows cross-channel switching between bots. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chatlayer.ai/buildabot/tips-and-best-practices/frequently-asked-questions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.