In brief
A conversational interface lets someone complete a task through a sequence of messages or speech. Its design depends on context, turn-taking, and recovery as much as wording.

Common tools
- Figma
- Browser tools
- Spreadsheet
Skills in play
- Research
- Accessibility
- User testing
What it is
A conversational interface uses turns of speech or text to help someone complete a task. It may appear in a voice assistant, a support chat, or a product flow that asks questions one at a time. The design is more than a friendly script. It determines what the system understands, when it asks for detail, how it confirms an action, and what happens when the conversation goes wrong.
Voice and chat share a dialogue structure, but they are not interchangeable. A chat can show a list that a user scans; a voice response must be understood in time, without rereading. Amazon’s voice guidance recommends writing for the ear and testing prompts spoken aloud. Google likewise emphasises relevant, concise turns that move the user’s task forward.
Decide when conversation helps
Start with the task. Conversation can be useful when a user can state a goal naturally, when a small number of details need to be collected, or when hands and eyes are occupied. It is less useful when someone needs to compare many options, inspect dense data, or navigate a complex structure. A visual screen, search result, or form may serve those tasks better. The interaction design should choose the mode that makes the next action clear.
Write a task map showing the user’s goal, the minimum information needed, the system’s available actions, and the point at which the task is complete. Include privacy-sensitive details and any action that requires explicit confirmation. Do not imply the system can help beyond its actual scope.
Script the ordinary path and the difficult paths
Sketch a sample dialogue in plain language. For every question, ask whether the user knows what kind of answer is expected. For every response, ask whether it gives useful progress or merely fills time. Then add interruptions: an unclear answer, a correction, silence, a change of mind, an unavailable result, and a request to stop.
Keep context between turns so the person does not repeat information unnecessarily. If they ask to change a detail, show what was changed and what remains. A helpful error prompt identifies the missing piece and suggests a next step; βI didn’t understandβ alone sends the user back into the same failure.
Make the interface legible across modes
For a screen-based conversation, distinguish system messages, user messages, status, and actions through more than colour. Use readable type, clear focus order, and persistent access to important controls. For voice, make turn-taking explicit through timing and a short question. Provide a way to repeat, slow down, or receive information in another mode where the product supports it.
Do not make a spoken interface the only path to an essential task when speech, hearing, privacy, language, or environment may prevent its use. Test a keyboard and screen-reader path for chat, and a usable visual or text alternative for voice where possible. Accessibility and inclusive interface design applies to the whole journey, including failures.
Keep personality subordinate to clarity
Choose a consistent tone that fits the service, but let the task determine the length of a response. A light joke repeated during every error becomes an obstacle. A confirmation about a consequential action should be unambiguous. Read the dialogue aloud, then cut phrases that sound natural on a page but slow the spoken interaction.
Prototype and review
Test with realistic requests, accents, interruptions, long names, and unexpected phrasing. Watch whether users know when to speak, whether they can correct the system, and whether they can finish without learning a secret command. Record cases the system cannot handle and design an honest handoff to search, a person, or another interface.
Practical checks
- Does conversation genuinely shorten or clarify the task?
- Can a user correct, cancel, repeat, and recover without starting over?
- Are prompts brief enough to hear once and understand?
- Is there a usable alternative for people who cannot or do not want to speak?
Common mistake
Writing only the ideal dialogue. The quality of a conversational interface is most visible when the user says something unexpected.
People and practice






