Curtis McCrady

Updated Mar 3, 2026
← Back to Product Log

Blueprint Library

Vitally logoVitallyOctober 2025

Problem Summary

Customer Success teams were spending weeks configuring Vitally from scratch, rebuilding workflows that hundreds of other customers had already perfected. There was no way to leverage the collective wisdom of the CS community or apply proven best practices. Every team started with a blank slate, leading to inconsistent implementations, missed opportunities, and delayed time-to-value.

Opportunity

How might we help CS teams activate proven workflows without building from scratch?

Solutions

Solution Image 1
Redesigned action nodes to include aggregate run data and object creation (e.g. conversations) data. Improved the run history to be filterable by each specific action.
Solution Image 2
Updated the ouput of individual runs to be consice and account for every possible edge case so users are not left in the dark about what happened and why.