Using the Meeting Bot
Using the Meeting Bot
To configure the bot's name, Google Meet authentication, and platform-specific behavior, see Meeting Bot Identity under Settings > Meetings.
The Bot Manager
The Bot Manager is the control center for monitoring and managing the Salescaling AI assistant's schedule. While general organization rules determine which meetings the bot joins by default, the Bot Manager provides the user with final control, allowing for manual adjustments for specific meetings.
Its primary goal is to give you flexibility and total control over your privacy and which conversations are recorded.
.png)
Key Features:
1. Review the Bot's Schedule
The main screen functions as a calendar, displaying all future meetings the bot is scheduled to join in the Upcoming tab. This provides complete visibility and allows you to anticipate which conversations will be analyzed. In the Past tab, you can view the history of meetings the bot has already attended.
2. Manage Attendance Meeting by Meeting (Manual Control)
This is the most important feature of the Bot Manager. For each future meeting, an (ON/OFF) toggle switch is displayed.

- This control is especially useful for personal meetings, interviews, or any conversation that should not be recorded. By turning the switch off, the bot will not attempt to join that specific meeting. This action acts as a manual veto, providing granular control without needing to contact an administrator to change 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.
-
This window shows a detailed history of the bot's statuses for that meeting, offering total transparency. If you have questions about why a bot did not join a call, the Activity Log will indicate if it was manually disabled or if another event occurred.
.png)
Below is the meaning of each status that may appear in the timeline:
- Ready: The system has recognized the meeting and 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 inside the meeting and actively recording.
- Call Ended: The bot has left the video call. A reason may appear below (e.g., it was removed from the waiting room, no one else joined the meeting, or the call remained silent for too long). See When the bot joins and leaves to understand what each common case means.
- Recording Done: The recording file has been processed and saved.
- Done: The bot's process for this meeting has concluded.
When the bot joins and leaves
The bot is scheduled to join at the meeting time (or when you manually invite it). You do not need to be inside for it to join: it can wait alone for a few minutes for others to arrive.
Salescaling defines how long it can remain on the call if the meeting does not progress or if it no longer makes sense to continue recording. The time limits are designed for two things at once: not missing the recording when someone is late or waiting in silence, and not leaving bots hanging in empty or forgotten meetings.
If the bot is not yet in the meeting
| Situation | What the bot does |
|---|---|
| It is in the waiting room and no one admits it | Leaves after 10 minutes without being admitted. |
| It is already on the call but no one else joins | Waits up to 15 minutes; if it remains alone, it leaves. |
| It is on the call but cannot start recording (permissions denied, etc.) | Leaves after 30 minutes without being able to record. |
If the bot is already recording
| Situation | What the bot does |
|---|---|
| All other participants have left | A few minutes after the recording starts, if it detects that no one else is left on the call, it leaves approximately 1 minute later. |
| No one is speaking (silence on the call, e.g., waiting on mute) | Does not count silence for the first 10 minutes of recording. Afterward, if the call continues for 30 consecutive minutes without voice, it leaves. |
| Maximum duration | Stops recording and leaves after 3 hours even if the meeting is still open. |
Practical Tips
- You are running late: If you join within those margins, the bot should still be in the meeting. If it has already left, invite it again from Meetings (“Record meeting”) or check that it is still enabled in the Bot Manager.
- Waiting alone for others: You can stay on mute; the bot will not leave after a few minutes due to silence. However, it is advisable to admit the bot as soon as it enters and, in Zoom, grant recording permission if prompted.
- Personal or off-the-record meeting: Disable the bot in the Bot Manager before the meeting starts.
Note: These times apply to bots that Salescaling schedules from now on. If you moved the meeting on the calendar or re-enabled the bot in Bot Manager, the current rules apply.
Frequently Asked Questions (FAQ)
I see a meeting on my Bot Manager schedule that I don't want the bot to join. What do I do?
Simply find that meeting in the Upcoming list and click the green toggle switch to turn it to the OFF position. The bot will no longer attempt to join that meeting.
I disabled the bot for a meeting by mistake. Can I re-enable it?
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 turn it to the ON position.
I arrived late and the bot was no longer in the meeting. Why?
The bot may leave on its own if the meeting has been empty for a long time, silent, or without permission to record (see When the bot joins and leaves). If you joined after that margin, you will need to re-invite the bot using the meeting link or ensure it remains enabled in Bot Manager for next time.
I was alone waiting for others to come and the bot left. Can this be avoided?
Salescaling waits up to 15 minutes if no one else joins the call and tolerates up to 30 consecutive minutes of silence (after the first 10 minutes of recording) while someone is still inside, to cover typical delays. If the wait exceeds those margins, the bot leaves to avoid recording an empty room or a forgotten call. When the meeting actually starts, bring the bot back in or disable and re-enable the meeting in Bot Manager if it hasn't started yet.