> 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/menus-and-voice-ai/fixing-modifier-prompts-in-your-menu.md).

# Fixing Modifier Prompts in Your Menu

So you've started to place some Test Calls and you've found that the AI is not asking you what selection you would like attached to the menu item. The AI reads your menu exactly how you have it set up and prompts the customers based off what modifier groups are required to make a selection. 

For this example, we will use ranch or bleu cheese preference with an order of wings. If the AI isn’t asking customers which dipping sauce they’d like, it’s likely due to how your menu item’s “min/max” selection settings are configured.

Follow these steps to update them:

1. **Open your menu settings**\
   Go to the item where dipping sauces are listed (for example, wings, tenders, or combo meals).
2. **Locate the sauce modifier group**\
   Find the section where your sauces (e.g., Ranch, Bleu Cheese, No Sauce) are listed as options.
3. **Check the “Min/Max” settings**
   * The *Min* value is the **minimum number of sauces required**.
   * The *Max* value is the **maximum number of sauces a customer can choose**.
4. **Adjust the values**
   * If your settings currently say **1–0**, this prevents any sauce from being selected or prompted (since “0 max” means no selections allowed).
   * Update the range to **1–5**. This setting means:
     * The customer must pick **at least one** sauce (the AI will always ask).
     * They can pick **up to five** sauces if they want extras.
5. **Save your changes**\
   Once saved, the AI will correctly prompt customers to choose a dipping sauce—like Ranch, Bleu Cheese, or “No Sauce”—and allow optional extras.


---

# 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/menus-and-voice-ai/fixing-modifier-prompts-in-your-menu.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.