> 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/meetings.md).

# Meetings

The Meetings module allows you to easily schedule, manage, and track meetings related to leads, ensuring smooth communication and timely follow-ups. Each meeting is saved as a record, which includes details such as the scheduled time, meeting type, mode (in-person or virtual), status, and customer feedback. This helps keep track of interactions and feedback, supporting better engagement and follow-up strategies. Meeting module has association with leads module and this association allows users to view the details of the lead with whom the meeting is scheduled directly from the Meetings module, without needing to switch to the Leads module.

<figure><img src="/files/TWaUSvJhvHlMls3SDJAG" alt=""><figcaption></figcaption></figure>

The above image shows a sample record view of a Meetings module.

**Associated Module:** Leads

The Leads module is associated with the Deal module through a lookup field. When adding a meeting in the module, you need to select the corresponding lead for the meeting. Additionally, you can view the lead record directly by clicking on the lead lookup field

### Filter View

The Meeting module is configured with 4 filter views as shown in the image below.&#x20;

<figure><img src="/files/dv9l5o1gvFDLN7GCURhi" alt=""><figcaption></figcaption></figure>

### **Type of Meetings**

Meetings can be conducted in various modes, including both online and offline. Online meetings are held through apps such as Zoom, Google Meet, and Microsoft Teams, while offline meetings involve in-person interactions or phone calls. Direct in person meetings are held at desired locations and time. The meeting mode is chosen based on the lead’s preference to ensure a personalized experience.

### **Customers Not attended the meeting**

If a customer misses a scheduled meeting, the meeting status is updated to "No Show," triggering the workflow "**Message to No Show**." This sends both WhatsApp messages and an email to the lead, informing them about the missed meeting and allowing for rescheduling.

### Meeting Feedbacks

Once a meeting is marked as "Completed" in the CRM, it triggers the **Meeting Feedback Chatbot** via a workflow called **Trigger Meeting Feedback Chatbot**, which collects and saves feedback from the lead in the Meetings module. Afterward, the meeting outcome and summary are also saved in the CRM module, helping to enhance follow-ups and increase the likelihood of closing deals.

### Meeting Reminder

Meeting reminder messages are sent to customers two days before the scheduled meeting via the "**Meeting Reminder**" Connector, which is scheduled using the platform's Schedulers. This ensures timely notifications for upcoming meetings.


---

# 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://help.pickyassist.com/setting-up-guide/working-with-prebuilt-crm-modules/modules/meetings.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.
