> For the complete documentation index, see [llms.txt](https://virtualcontact.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://virtualcontact.gitbook.io/docs/welcome-to-virtual-contact/main-modules.md).

# Main modules

Virtual Contact is organised into six core modules that work together as a unified platform:

* **Omnichannel Contact Center** — manage all channels (chat, email, WhatsApp, phone, social) from a single inbox
* **WorkFlow AI** — automate operational flows, routing rules and notifications without coding
* **Chatbot Flow AI** — build and deploy AI chatbots on any channel using natural language prompts
* **CRM** — Lead and Profiling — manage contacts, companies, leads, tickets and the full commercial pipeline
* **Apps and Integrations** — connect Virtual Contact to 200+ external tools and systems
* **Admin and Workspace** — manage users, roles, permissions, departments and platform settings


---

# 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://virtualcontact.gitbook.io/docs/welcome-to-virtual-contact/main-modules.md?ask=<question>&goal=<endgoal>
```

`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.
