> 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/ai-voice-agents/how-to-set-up-your-ai-voice-agent/voice-agent-settings-guide/configure-conversation-boosted-keywords.md).

# Configure Conversation – Boosted Keywords

Add up to 100 comma-separated domain terms as Boosted Keywords so Dapta's transcription recognizes technical vocabulary and uncommon words accurately.

Automatic transcription systems often struggle with:

* Specific, uncommon words or terms from a particular domain
* Technical terminology from specialized fields (medicine, law, engineering, etc.)<br>

To address this, Dapta provides the “Boosted Keywords” functionality, which allows you to:

* Customize the system’s vocabulary according to specific needs
* Improve accuracy in your agent’s specialized domains

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-b30e07a7088ab951eebf6e72952d81a04c7dd157%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

You can include up to **100 words**, separated by commas ",".

This way, you can provide lists of specific terms to improve transcription accuracy for your particular use cases.


---

# 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/ai-voice-agents/how-to-set-up-your-ai-voice-agent/voice-agent-settings-guide/configure-conversation-boosted-keywords.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.