Conversational Component Model: Building Blocks for Voice UI
Think of conversational components as LEGO bricks for dialogue. You assemble standard pieces like questions, confirmations, and apologies to build a natural flow for voice assistants or chatbots.
Why it exists
To create scalable, consistent, and natural-sounding conversations for digital assistants and chatbots. Without a formal model, every dialogue path would be custom-scripted from scratch, leading to an inconsistent brand personality, high maintenance costs, and a brittle user experience that breaks easily.
The mental model
Think of conversational components as the standard parts of a human conversation, formalized for a machine. Just as people use common phrases for greeting, confirming, or apologizing, a voice UI uses these components to construct its side of the dialogue. It's about assembling a conversation from a kit of parts, not writing a novel from scratch for every user turn.
How it works
The model breaks down a system's turn in a conversation (a "prompt") into smaller, reusable pieces. These components include informational statements, questions, confirmations ("Are you sure?"), apologies ("Sorry, I didn't get that"), and acknowledgements ("Got it."). These are combined to form a complete spoken or displayed prompt. The model also includes "chips"—suggested replies the user can tap or say to guide the conversation forward or pivot to a new topic.
When to use it
Use this model when designing any conversational interface, especially for voice assistants (like Google Assistant or Alexa) or sophisticated chatbots. It's essential for creating a consistent persona and ensuring the user experience is predictable and helpful. The design process starts with writing sample dialogs for a voice-only context to get the flow right before considering any visual elements.
When not to use it
This model is overkill for simple, one-shot commands or non-interactive systems. If the user interaction is just a single command-and-response with no follow-up (e.g., a basic CLI tool), there's no "conversation" to design. It's also less relevant for purely graphical interfaces that lack a conversational element.
One canonical example
A user asks a food delivery app, "What are my recent orders?" The system's response is built from components. First, an INFORMATIONAL STATEMENT: "You have three recent orders." Second, a QUESTION: "Which one would you like details on?" Finally, SUGGESTION CHIPS are displayed: ["Last order"], ["Order from Tuesday"], ["All orders"]. This combines multiple components into one smooth conversational turn. The voice-first design principle means this spoken flow is perfected before designing how the chips look on a screen.
Interview question
For which application is the Conversational Component Model most advantageous?
- a.A mobile game with only touch-based controls and no dialogue
- b.A voice-controlled smart home assistant handling multi-step requestsCorrect
- c.A website's static FAQ page with no interactive elements
- d.A utility script that accepts a single command-line argument
Why? this is the answer
The model is designed for voice assistants and sophisticated chatbots to create consistent, natural, and scalable multi-turn conversations. It is explicitly stated as overkill for simple, one-shot commands or purely graphical/non-interactive systems.
Just read this? Test yourself on what you have been reading.
Read the original → developers.google.com
- #design systems
- #ux
- #voice ui
- #chatbots
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on design systems — each one lists the topics its interview covers.
See open roles