> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/es/faq/c150/c154/q477.md).

# ¿Puedo usar voz a texto para añadir comentarios o descripciones a mis informes?

La mayoría de los teclados de dispositivos móviles admiten voz a texto. Tenga en cuenta que la funcionalidad de voz a texto es proporcionada por un proveedor de servicios externo y puede requerir una conexión a Internet para transcribir su voz de forma remota.

El portal web no ofrece una opción de transcripción por el momento, pero la función de voz a texto es compatible en [Windows](https://support.microsoft.com/en-us/accessibility/windows/use-voice-typing-to-talk-instead-of-type-on-your-pc) y [Mac OS](https://support.apple.com/en-au/guide/mac-help/mh40584/mac).

## Relacionado

* [FAQ: ¿Cómo añado explicaciones de audio a fotos o uso otros formatos de audio con la aplicación?](https://docs.reportandrun.com/manual/es/faq/c150/c153/q471.md)
* [FAQ: ¿Puedo revisar la ortografía de mi informe una vez completado?](https://docs.reportandrun.com/manual/es/faq/c160/c166/q554.md)
* [Preguntas frecuentes: ¿Cómo agrego texto, notas o párrafos a mis informes?](https://docs.reportandrun.com/manual/es/faq/c150/c153/q456.md)
* [FAQ: ¿Cómo guardo texto de uso frecuente para no tener que escribirlo cada vez?](https://docs.reportandrun.com/manual/es/faq/c150/c155/q488.md)


---

# 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.reportandrun.com/manual/es/faq/c150/c154/q477.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.
