I led design across Voice & Video, Flex and Conversations to help turn conversation data into something teams could understand, configure and act on.
Conversation Intelligence sits at a critical point in the Twilio experience. It takes what is happening in customer conversations and turns it into structured insight that can support better decisions and actions.
The challenge was not simply designing another feature. It was making a sophisticated AI capability feel understandable inside a platform used to build and operate real customer experiences.
As Senior Product Design Manager, I brought together design perspectives across Voice & Video, Flex and Conversations to solve a shared problem around conversational intelligence.
This meant aligning designers, Product and Engineering around a common experience while still respecting the different workflows and technical realities of each product area.
Conversation Intelligence brought together work that crossed the teams I led across Twilio Communications and Conversational AI.
That meant connecting perspectives from Voice & Video, Flex and Conversations, while partnering closely with Product and Engineering across the portfolio.
Rather than treating each surface as an isolated experience, I used Conversation Intelligence as an opportunity to create a more coherent model for how intelligence could move through the wider Twilio platform.
The product needed to do more than surface AI results. Customers had to be able to configure how intelligence was generated, preserve the logic they already had, and understand how those settings affected real conversations.
That meant designing across three connected layers: the intelligence itself, the configuration that drives it, and the conversation experience where the results become useful.
Make the intelligence itself understandable and editable, including customer-authored operators and richer training examples.
Connect intelligence to rules, triggers and actions so the output can drive what happens next.
CINTEL was evolving quickly, including a v2 to v3 migration, new configuration capabilities, editable code, training examples and additional rule triggers. The experience had to evolve without making customers relearn everything.
The walkthrough shows the CINTEL experience in context. The Figma work below shows how the team explored the product model, interaction patterns and migration experience.
The main CINTEL design work, including the product experience and exploration.
A wider journey exploration showing how the experience was worked through across states and interactions.
A second exploration of the CINTEL experience and its relationship to the wider conversational workflow.
The interactive prototype starts at the CINTEL migration experience.
CINTEL was not designed in isolation. I brought together the teams and product perspectives I was leading across Voice & Video, Flex and Conversations to create a coherent experience for conversational intelligence.
The architecture below helped make the relationships between intelligence, conversations, memory, knowledge and communications explicit, while keeping CINTEL itself at the centre of the user problem.
The product context context around Conversation Intelligence, used to understand how the product connected to the wider conversational experience.
I worked through Conversation Intelligence at multiple levels: the product model, configuration experience, migration journey and the interaction patterns needed to make conversational intelligence understandable in the moment it is used.
The CINTEL v3 experience: making configuration, intelligence and action legible inside the platform.
Exploring the experience and the relationships between the core CINTEL workflows.
Working through states, transitions and the broader customer journey.
Extending the exploration across the wider conversational workflow.
Bring intelligence into the conversation viewer so results are encountered in context, rather than in a disconnected reporting surface.
The prototype was where the model was tested as a connected journey, not a collection of isolated screens.
One of the wider design questions was how customers could experience the value of conversational AI before they had invested time configuring it. The Playground work explored a self-serve path from curiosity to an interactive, Sierra-powered experience.
For CINTEL, this reinforced a key principle: the value of intelligence is realised when customers can see how it changes what they can do.
A major part of the work was the v2 to v3 migration. Existing intelligence services had to move into the new model while preserving customer-authored logic and making new capabilities easier to adopt.
The experience evolved around auto-created configurations, migrated operators and a clearer relationship between transcription, conversation and intelligence. Support for multiple training examples became part of the production experience rather than a theoretical future state.
The migration flow preserves the existing customer model while moving users into the v3 configuration experience.
The migration work mapped how transcript, recording, conversation and intelligence configurations relate to each other.
The Voice and Recordings work made the capture layer more explicit. That mattered because CINTEL depends on the data being captured, transcribed and routed correctly before intelligence can be generated.
The strongest design move was not adding more UI. It was making the relationships visible: what is being captured, what is being transcribed, what is being analysed, what configuration drives that analysis and where the resulting intelligence appears.
That gave the teams a shared language for discussing the product and gave customers a clearer path through an increasingly complex platform.
We established recurring design-quality reviews, pattern QA, UAT and cross-functional testing so the quality of the experience could keep pace with the speed of the product.
Conversation Intelligence grew into a significant part of Twilio's Conversational AI offering, with enterprise adoption and measurable commercial growth.
Annual revenue associated with Conversation Intelligence.
Year-over-year growth.
Design organisations brought into the conversation: Voice & Video, Flex and Conversations.
As Senior Product Design Manager, I led 12 designers across the portfolio and partnered with Product and Engineering leadership to align priorities, capacity and design direction.
Conversation Intelligence gave those teams a shared problem to solve: how conversational intelligence should work as part of a connected platform rather than as a collection of separate capabilities.