With the Vitally MCP server (currently in Beta), you can now connect your Vitally instance to your MCP-compatible AI tool of choice, and fight churn without ever leaving ChatGPT.

Search and analyze your customer data, surface key insights into risk and opportunity, and take action to create Notes, Tasks, and more directly from any LLM. Visit our documentation to learn how to set up the Vitally MCP and see what tools are available. Read more about best practices for optimizing Vitally for MCP ->

For Vitally customers with the Custom Surveys add-on, you can now add conditional logic to display or hide survey questions based on previous responses. This allows you to create more dynamic, personalized surveys that build off the actual answers a user is giving to your questions and improve response rates.

We’ve made a series of improvements to the AI Copilot experience in Vitally:

You can now configure Slack channel notifications for Key Role changes and for new Custom Object records. When a Key Role on an Account changes, Vitally sends a notification to the Slack channel you've set up, keeping your team in the loop when ownership or responsibility shifts on an account. Instead of finding out about a reassignment after the fact, the right people see it in Slack the moment it happens, so handoffs and coverage stay clear.

Admins can also choose specific Custom Objects to watch and can apply Custom Object filters so Slack messages are sent only for matching records — a cleaner way to monitor activity like risk or request records.

Conversation summaries are now easier to revisit in long threads. The summary stays open when you first load a thread, collapses automatically once you start scrolling, and a compact floating button near the reply footer lets you jump back to it without triggering extra pagination.

You can now move a Project to a different parent Account, both directly inside Vitally and through the REST API. The Project header includes a new action to change the parent, and because reparenting moves all of the Project's Tasks along with it, making it easy to fix a mis-filed Project without recreating it from scratch. REST API endpoints support the same move for bulk reorganizations.

Trigger a backfill of your Gmail or Outlook emails directly from Vitally, without opening a support ticket. Pull in missing emails once per day, so gaps in your synced conversation history are easy to resolve on your own.

You can now click any branch in the Playbook editor to open Run History pre-filtered to the enrollees who took that path — including "otherwise" branches that immediately terminate. You can combine branch filters with status tabs, search for specific branches, and export the filtered runs to a CSV, making it far easier to debug and audit Playbook behavior.

Admins and Leaders can now view and edit a teammate's Job Title from the “Manage Team” area in Settings. AI Copilot uses “Job Title” as part of its default context, so keeping it up-to-date helps produce more relevant and accurate results.

Tasks generated from a Vitally Meeting Recorder transcript are now always assigned to someone who attended the Meeting, ensuring the right person takes action following a call.

You can now clear the “Permanently Bounced” flag directly from the User 360, or with a new bulk action for multiple Users at once from a User Table View. This makes it faster to correct bounced email statuses after you've resolved the underlying delivery issue.

The Description field now appears on any Custom Object instance with a parent Account, including objects created by integrations. You can document handoff notes, risks, and other context directly in the Custom Object slideout. This value is not synced back to Salesforce or other integrations.

Trait settings now show an integration icon next to integration-linked Trait names, making it easy to tell them apart from Custom Traits. This is useful when configuring Custom Objects that mix Formula Traits, integration Traits, and Custom Traits.

Admins can now configure which Intercom contact field Vitally uses as the User external ID, including custom attributes, matching the existing capability for Intercom Companies. This helps you avoid duplicates and match existing records.

The REST API now supports retrieving a specific Admin by UUID through GET /admins/:id. Integrations that already store Admin IDs can fetch a single record directly, without paging through results or relying on email-based lookup.

Public REST API admin responses now include team member roles, giving integration partners the role context they need directly from the API.

You can now add a source parameter (e.g., salesforce) when querying Custom Object Instances, just like with Notes and Tasks. When you do, each record's externalId is populated, removing the need to register with a feature flag to expose it.