> For the complete documentation index, see [llms.txt](https://docs.omnidesk.io/omnidesk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnidesk.io/omnidesk/link-customer/general.md). # General One of Omnidesk its features is that it will help you recognize customers when they contact you so you have all communication data in one place on the screen. This will boost customer service agents efficienty and makes conversations more personal, especially in medium to larger organizations (5+ agents). To achieve this there are multiple methods: 1) Let customer agents fill in the extra info on first contact, 2) Import your base to the mini-CRM of Omnidesk or 3) make a API sync between your CRM and Omnidesk. #### Base migration For the base migration we require a minimal set of data of each customer in your base. When setting up Omnidesk this can be added trough an initial CSV import and afterwards you can still use the other two options: you can ask customer care agents to update the data when they receive a contact and the other option is to sync new customers trough the API. You can also choose to combine both options. --- # 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://docs.omnidesk.io/omnidesk/link-customer/general.md?ask=&goal= ``` `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.