> For the complete documentation index, see [llms.txt](https://support.kea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.kea.ai/kea-ai-customer-faqs/does-the-ai-get-smoother-with-use.md).

# Does the AI get smoother with use?

**Yes! Your Kea AI Voice Agent gets smarter and faster with every call and order.**

That’s why we highly emphasize placing as many [**Test Calls**](https://support.kea.ai/kea-brand-portal-setup/kea-order-view-and-placing-test-ai-orders) as possible during Onboarding — it helps train the AI on your specific menu setup.

For example, you may notice that during your **first test call**, the AI takes a bit longer to confirm the menu item or locate the correct modifier group. This is completely normal. That first call is essentially the AI’s first time “reading” your menu and learning how your items are structured.

If you have a pizza called *The Honey Pot*, for instance, that’s the AI’s first time learning that *The Honey Pot* refers to a pizza — and that it comes in different sizes. The more test calls you place, the faster and more accurate your AI will become.


---

# 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://support.kea.ai/kea-ai-customer-faqs/does-the-ai-get-smoother-with-use.md?ask=<question>&goal=<endgoal>
```

`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.