> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/voice-ai/voice-ai-overview-in-english/embed-voice-ai-into-your-website.md). # Embed Voice AI into Your Website Steps to embed your Voice Agent widget: 1. Go to the **Voice Agent Dashboard** 2. Open the required **Voice Agent** 3. Click on **Code** (right-hand side) 4. Customize the widget (logo, branding, colors, etc.) 5. Click **Save** 6. Click **Copy Code** #### Add Code to Your Website 7. Open your website’s **HTML file** 8. Locate the `` tag 9. Paste the copied script **just before the closing `` tag** 10. Save the file 11. Open the website in your browser Your Voice Agent will now appear (usually at the bottom-right corner) and is ready to interact with users in real time. {% embed url="" %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helpdocumentation.gitbook.io/user/voice-ai/voice-ai-overview-in-english/embed-voice-ai-into-your-website.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.