### Answer Here are several strategies to improve price retrieval accuracy from your Knowledge Base: ## Markdown Structure Best Practices Use clear, descriptive headings and keep each

##

section focused and reasonably short. If a

##

becomes long, split it into multiple `##`/`###` sections. [(1) ]() Write short paragraphs and lists to separate concepts; avoid walls of text. For tabular or image-heavy content, retrieval may be less reliable; consider adding explanatory text so related information stays in the same chunk. ## Specific Recommendations for Pricing Data Group related information within the same section so chunks remain cohesive and relevant. Avoid ambiguity and use specificity in references. Include names, dates, units, and avoid ambiguous pronouns like

it

or

this

, because prior chunks may not be present. For your services menu, try structuring each service as a self-contained block with the price explicitly tied to the service name—for example:

## Service Name: Deep Tissue Massage
- Duration: 60 minutes
- Description: Full body therapeutic massage
- Price: $120

## Alternative Approach If tabular pricing continues to cause issues, consider building a custom function/tool to look up answers instead of relying on free-text search. [(2) ]() ## Adjust Retrieval Settings You can also configure KB settings by adjusting "Chunks to retrieve" (range 1-10, default 3) and "Similarity Threshold" (default 0.6) . A higher similarity threshold gives fewer but more similar matches. [(1) ]()

​ To learn more, see the sources I considered: [[1] Knowledge Base](https://docs.retellai.com/build/knowledge-base) [[2] Using knowledge base not how I wanted](https://discord.com/channels/1186424376300679209/1357009953247727808) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.