Skip to main content

September Release Notes

Copilot Calculations, Multilingual Meeting Notes, Upload Call Recorder Transcripts, and more

Written by Rachel Sheldon

Key Releases

Copilot Calculations

Copilot can now calculate totals, averages, and other aggregates the same way Widgets do. When you ask Copilot for a number across a set of records, it uses the same reliable calculation engine that powers your Vitally Dashboards.

That means you can fully trust the figures Copilot reports back. Whether you're checking a rollup mid-call or asking a quick question across all users at an account, the numbers line up with what you'd see in a Widget.

Multilingual AI Meeting Recorder Notes

AI Recorder Meeting briefs and suggested action items now generate in the language your meeting was actually held in. That covers summaries, key points, risk assessments, and action item names and descriptions. For calls that mix languages, the output follows the dominant one.

For multilingual teams, this removes the extra step of translating English or mixed-language output after a call held in French, Polish, or any other language. Meeting briefs and action items land ready to read and act on.

Upload External Call Recorder Transcripts

Two new REST API endpoints allow you to upload a third-party call recorder's transcript to a Vitally Meeting without needing to know the Meeting ID first. The first endpoint returns candidate Meetings with confidence scores, and the second matches it and then uploads the transcript.

This means that teams recording their calls using tools like Granola or Fireflies can now get those transcripts onto the right Meeting in Vitally. Documentation is available in the REST API reference.

Additional Releases

Cc and Bcc From Account Traits in Playbook Conversations

When a Playbook starts a Conversation over Gmail, the Cc and Bcc fields now pull from your Account and Organization Traits, right alongside Key Roles and teammates. Pick a Trait that holds a single email or a list of emails, and everyone in it is copied on the message.

If you store billing, contract, or escalation contacts as Traits, you no longer have to maintain those recipient lists inside each Playbook, or leave those contacts off your automated emails. The right people get looped in automatically, with context that's specific to each Account.

Copilot Access to Configuration Objects

Copilot can now pull configuration objects — such as Project Categories, Task Statuses, Note Tags, and Key Roles — into context and use their IDs when searching and creating records. AI-created Notes and Tasks can be categorized and tagged without manual cleanup, and search results are more accurate.

Improved Context for Custom Objects in Copilot and MCP

When Copilot or the MCP server answer questions about your Custom Objects, they now search for only the specific Custom Object type the question is about — this means you get more relevant answers, quicker, especially for teams with multiple different Custom Object types in their Vitally workspace.

Task Templates in Doc Templates

When building a Doc Template, the "/" Task option now lets you insert one of your Task Templates instead of only typing a Task name. Docs created from the template carry the full Task — category, tags, description, assignee, due date, and custom fields. Typing "/Task" for a quick ad-hoc task still works as the default.

Copilot Directs to Support

When you ask Copilot a question about how Vitally works, it can now show a button that opens our Support chatbot, Viv, with your question pre-filled, helping you get your product questions resolved faster.

Integration Releases

Vitally Email Pause Details

When Vitally Email gets paused, you can now see exactly what triggered it. The integration configuration page shows recipients sent, bounce rate, permanent bounces, the timestamp when sending was paused, and the time it's expected to resume — all in one place.

Admins will also now see a banner when Vitally Email is paused, so you can get to work on resolving errors immediately.

Confirm Before Disabling Salesforce, Jira, or HubSpot

Disabling your Salesforce, Jira, or HubSpot integration now requires typing "DESTROY" to confirm. The extra step makes it clear that turning off one of these integrations is a destructive action, not a routine toggle.

Disabling an integration can cause data loss and lead to painful recovery work. This confirmation gives you a moment to pause before making a change that's hard to undo.

Intercom Is Now Fin

To match Intercom's rebrand to Fin, Vitally now refers to the integration as Fin throughout the app. If you use the integration, you'll see the new name in all the places you'd expect.

Vitally MCP Additional Search Support

Vitally MCP now supports searching completed Tasks, inactive Projects, ended Indicators, deactivated Users, and other non-default views. This lets tools like Claude, ChatGPT, and Cursor retrieve the full set of relevant records, not just each object's default view.

Faster Salesforce Refresh

Salesforce picklist and multi-select picklist option labels now refresh up to every 12 hours instead of once a day, so label changes in Salesforce show up in Vitally sooner.

Did this answer your question?