> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.3/getting-started/faqs/search-faqs.md). # Search FAQs Explore Search FAQs to learn how AI-driven search adapts over time, supports synonyms, and enables user feedback for smarter analytics. #### **Does the search AI learn (i.e., get better over time) through crowd-sourced interaction and feedback?** In addition to displaying suggestions for the entire search query, Tellius displays suggestions for the current word being typed and the next word to be typed. The suggestions are provided based on multiple sophisticated algorithms. Tellius also displays the history of questions, trending questions, top questions, most frequently asked questions, questions based on users/frequency etc. #### **Is there an easy way for me to “teach” Tellius if the answer returned is good/bad?** Tellius' Search can learn from a user's language and dictionary. During data preparation, multiple synonyms can be added to a column, and those words can be used in search query instead of the actual column. Check out [this section](https://help.tellius.com/article/t079cqyb64-metadata-view#synonyms) for more details. In addition, for any search query, users can tag various words/phrases and teach Tellius the meaning for each phrase. Next time when the phrase is used, it will train Tellius to display the intended results. #### **What does 'last date' used in search queries represent?** By default, the last date refers to the current date. However, it can be customized in the admin interface. --- # 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://help.tellius.com/tellius-6.3/getting-started/faqs/search-faqs.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.