# Using the Meeting Bot

## **The Bot Manager**

The [**Bot Manager**](https://app.salescaling.com/bot-manager?isPast=false) is the control center for monitoring and managing the schedule of Salescaling's AI assistant. While the organization's general rules decide which meetings the bot will join by default, the Bot Manager gives the user final control, allowing manual adjustments for specific meetings.

Its main goal is to give you flexibility and full control over your privacy and which conversations are recorded.

<figure><img src="/files/5c6cd095fb09980bd31c92b55c1376226ea5b5d2" alt=""><figcaption></figcaption></figure>

Key Features:

### **1. Review the Bot's Schedule**

The main screen acts like a calendar, showing in the **Upcoming** tab all future meetings the bot is scheduled to join. This provides full visibility and allows you to anticipate which conversations will be analyzed. In the **Past** tab you can view the history of meetings it has already attended.

### **2. Manage Attendance Meeting by Meeting (Manual Control)**

This is the most important function of the Bot Manager. For each upcoming meeting, a toggle switch is displayed **(ON/OFF)**.

<figure><img src="/files/7d85f0ef90adfa6773de4e8aa38ab976600d2269" alt=""><figcaption></figcaption></figure>

* This control is especially useful for personal meetings, interviews, or any conversation that should not be recorded. By turning off the switch, the bot will not attempt to join that specific meeting. This action is a manual veto that provides granular control without needing to contact an administrator to change the general rules.

### **3. Audit Changes (Activity Log)**

Through the three-dot menu (...) at the end of each meeting row, you can access the **Activity Log** (Activity Record).

* This window shows a detailed history of the bot's states for that meeting, offering full transparency. If there is a question about why a bot did not join a call, the Activity Log will indicate whether it was turned off manually or if another event occurred.

  <figure><img src="/files/a0732fada570a37edd763e68f2bb65ac7f6ce5dc" alt="" width="283"><figcaption></figcaption></figure>

  Below is the meaning of each state that may appear on the timeline:

  * **Ready:** The system has recognized the meeting and has prepared the bot to join at the scheduled time.
  * **Joining Call:** The bot is actively attempting to enter the video call.
  * **In Waiting Room:** The bot has arrived at the meeting but is waiting for the host to admit it manually.
  * **In Call Not Recording:** The bot has been admitted, but has not yet started recording, usually while waiting for recording permissions.
  * **In Call Recording:** The bot is in the meeting and actively recording.
  * **Call Ended:** The bot's participation has ended. A reason may appear below (e.g., "Bot Kicked From Waiting Room" if it was removed, or "Timeout Exceeded" if all participants left).
  * **Recording Done:** The recording file has been processed and saved.
  * **Done:** The bot's process for this meeting has concluded.

#### Frequently Asked Questions (FAQ)

<details>

<summary>I see a meeting in my Bot Manager schedule that I don't want the bot to join. What do I do?</summary>

Simply find that meeting in the list **Upcoming** and click the green switch to put it in the off (OFF) position. The bot will no longer attempt to join that meeting.

</details>

<details>

<summary>I turned the bot off for a meeting by mistake. Can I turn it back on?</summary>

Yes. As long as the meeting has not passed, you can return to the Bot Manager at any time and click the switch again to put it in the on (ON) position.

</details>


---

# Agent Instructions: 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:

```
GET https://docs.salescaling.com/en/practical-guides/uso-bot-reuniones.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
