> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/connecting-channels/call-blaze-v2/working-with-crm.md).
# Working with CRM
All calls synchronized through CallBlaze are automatically stored as records in the **Call Logs** module.
Call Logs is a System Module, so its standard fields cannot be removed or modified.
The module provides a centralized view of calls made or received by connected agents, including key call information such as
* Phone number
* Agent Name
* Call direction (Incoming/Outgoing)
* Call status
* Call duration
* SIM used
* Call start and end date and time
### Accessing Call Logs
* Admins can view call records of all connected agents.
* Agents can access Call Logs based on the module [permissions](https://help.pickyassist.com/setting-up-guide/setting-up-modular-crm/create-and-manage-data-modules#roles-and-permissions) assigned to their Role by the admin.
{% hint style="warning" %}
Agents can view call logs in the mobile app only if the admin has enabled the Call Log module **view** [permission](https://help.pickyassist.com/setting-up-guide/setting-up-modular-crm/create-and-manage-data-modules#roles-and-permissions) for the agent's role.
{% endhint %}
### Calling from CRM Modules
Agents can call specific numbers directly from the CRM by clicking on the call icon over any number in the logs, This can be worked along with CRM Quick actions in the Callblaze app.
It works across **all CRM modules**, including system modules such as **Leads, Contacts, and Call Logs**, as well as **custom modules** with a Mobile Number field.
---
# 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.pickyassist.com/setting-up-guide/connecting-channels/call-blaze-v2/working-with-crm.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.
