> 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/working-with-prebuilt-crm-modules/modules/system-modules.md).

# System Modules

About System Modules

System modules are the core modules which are essential for CRM functionality. These modules are installed by default in every project. You dont have the option to skip these modules like Prebuilt modules. System modules form the foundation of the CRM structure. System modules and some fields cannot be deleted, but they can be renamed to suit your preferred language or local context. Some system modules may also be linked to custom modules as fields, with data added in these fields being saved as a record in the respective system modules. The system modules are **Contacts, Notes, Task, Call Logs, Tags** and **Activity Logs.**

<figure><img src="https://3382165395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LlJChpzcxtwOYGcBd1q%2Fuploads%2FNWVjLxuwdB5aGIinLMGI%2Fimage.png?alt=media&amp;token=b07e0c9c-b6d4-4ca4-bdd9-f59be98e133f" alt=""><figcaption></figcaption></figure>


---

# 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/working-with-prebuilt-crm-modules/modules/system-modules.md?ask=<question>&goal=<user_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.
