The Vitally AI Meeting Recorder is designed to bring call recordings and transcripts directly into Vitally, unlocking the full potential of our AI Copilot and post-call automation. It’s a CS-specific feature aimed at boosting productivity with automatic task creation, churn analysis, and more.

After the meeting:

Vitally detects the primary language spoken in the meeting transcript and uses it for AI-generated meeting content. The summary, key points, and risk assessment in the meeting brief are written in that language, along with the names and descriptions of suggested tasks. For meetings that mix languages, the brief and suggested tasks follow the primary language.

To receive Slack notifications:

Note: Summary, tasks, and risks are not yet sent to channels.

What are the requirements to use the AI Meeting Recorder?

How does this compare to the Gong integration?

Can I use both Gong and Vitally’s AI Meeting Recorder?

Yes. Both can record meetings simultaneously. You may receive duplicate task alerts in Vitally when both are active.

Can I bring in transcripts from a recorder Vitally doesn't support?

Yes, through the REST API. If you already know the Vitally Meeting id, post the transcript to that Meeting directly. If you don't, POST /resources/meetings/transcript matches the recording to a Meeting using hints such as the calendar event id, scheduled start time, or participant emails, then creates or replaces the transcript on the match. POST /resources/meetings/find runs the same matching without writing anything, so you can confirm the match first. See REST API: Meetings for the full request format.

What meeting platforms are supported?

What if the Meeting Bot doesn't join or leave as expected?

There are a few known edge cases—like when meeting ownership is transferred, meetings are deleted, or calendars are disconnected—that may prevent the AI Meeting Recorder from properly joining or leaving a meeting.

The most common reason a meeting never gets recorded is that the meeting never synced into Vitally in the first place. A meeting syncs when at least one participant is a Vitally team member with a connected calendar, and at least one other participant is a tracked User whose email matches the calendar invite exactly. If those emails don't match—even by one character, which often happens when the Vitally email was set from a CRM like Salesforce—the meeting won't sync and the recorder won't join it. To fix this, correct the User's email in the source system (e.g. Salesforce) so it matches the invite, and confirm the change syncs to Vitally. Meetings with that attendee going forward will then sync and record.

How far in advance does a meeting need to be scheduled to be recorded?

For Google Calendar and Outlook, create the meeting at least 35 minutes before it starts. New events can take up to around 30 minutes to sync into Vitally, and the recorder checks for meetings to join every 5 minutes. Meetings booked with less notice may still be recorded, but this isn't guaranteed.

Avoid changing the meeting's start time or meeting link in the 7 minutes before it starts, as the recorder may not pick up the change.

I changed the Meeting Bot name, why is the old name still joining my meetings?

A new Meeting Bot name only applies to recorders created after the change. Vitally creates a recorder once a meeting is within roughly 7 days (one week) of taking place, so meetings further out will use the new name automatically. Recorders already created when you changed the name keep the previous name. Editing a meeting's time or link doesn't update it.

To apply the new name to a meeting that already has a recorder:

For recurring meetings, make the change on each upcoming occurrence, not the series. Make the change well before the meeting starts, as the recorder needs a buffer to pick up changes.

How does the Vitally Meeting Recorder do domain exclusion?
You can configure this in settings > security > domain exclusion. Just add the domains you want to exclude (this also stops syncing meetings and conversations).