> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/edit-your-guideflow/voiceover/human-voiceover.md).

# Human voiceover

Record your own voice to deliver personalized guideflows that feel like one-on-one demos—letting users hear a familiar, trusted voice.

### How to add a human voiceover

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/lpx6j0wu4p>" %}

* Go to Voiceover and click **Add Voiceover**.
* Click **Record** and select your recording device.
* Start recording, then click the timer to stop.
* Reposition the voiceover launcher as needed and preview your audio.
* Enable autoplay to start voiceover automatically.
* Enable subtitles and generate them with AI.
* Review, edit, and save your AI-generated subtitles.
* Go to Preview to test your voiceover—it will autoplay or require clicking the launcher.
* Your voiceover now enhances the interactive demo with synchronized subtitles.


---

# 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.guideflow.com/help/edit-your-guideflow/voiceover/human-voiceover.md?ask=<question>&goal=<user_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.
