> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-docs-es/agentes-de-voz-ia/configura-tu-agente-de-voz-ia/guia-para-configurar-tu-agente-de-voz/configurar-conversacion-boosted-keywords.md).
# Configurar Conversación - Boosted Keywords
Añade hasta 100 palabras clave potenciadas, separadas por comas, para mejorar la transcripción de tu agente de voz en términos técnicos o poco comunes.
Los sistemas de transcripción automática a menudo tienen dificultades con:
* Palabras específicas, poco comunes o términos de segmento específico
* Terminología técnica de campos especializados (medicina, derecho, ingeniería, etc.)
Para mitigar ello, Dapta brinda la funcionalidad de "Boosted Keywords" (Palabras Clave Potenciadas) que permite:
* Personalizar el vocabulario del sistema según las necesidades específicas
* Mejorar la precisión en dominios especializados de tu agente
Puedes incluir hasta 100 palabras, separadas por comas ","\
\
De esta forma puedes proporcionar listas de términos específicos para mejorar la precisión de transcripción en tus casos de uso particulares.
---
# 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.dapta.ai/dapta-docs-es/agentes-de-voz-ia/configura-tu-agente-de-voz-ia/guia-para-configurar-tu-agente-de-voz/configurar-conversacion-boosted-keywords.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.
