> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/sales-crms/aircall.md). # Aircall ## **Why syncing my Aircall to** [**Whaly**](https://whaly.io)**?** Syncing your Aircall can be useful for various cases * Analyse when customers are phoning you * Measure your response rate * Report on your team performance and make sure that you get to your calls objectives * Identify any outliers (high call duration, low number of calls, ....) to better train and support your team members * .... ## Which Aircall data is synced by [Whaly](https://whaly.io)? [Whaly](https://whaly.io) 🐳 is currently syncing the following data: * **Calls**: Calls are an essential part of how Aircall users interact with the product. Our mission is to give real-time insights to make the call experience as delightful as possible! * **Number:** Users (Admins) can buy Numbers from the Dashboard. They can then update the call distribution order, upload custom Music & Messages, enable or disable call recording... * **User**: Users can be either Admins or Agents. They are the people working in your business to receive or make calls. They are associated to Numbers. * **Contact**: Contacts are a core part of Aircall experience. Every time Agents are on a call, Aircall fetches their contact information from different sources. [You can find the relationship between all those objects here.](https://docs.google.com/presentation/d/1i5huM9Y51Wz2P8JeGqongeC8zQQGlLfAI4Iazhn6_p0/edit?usp=sharing) {% embed url="" %} --- # 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.whaly.io/connectors/source-catalog/sales-crms/aircall.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.