Make system status visible in conversation
Design conversational status messages that reduce uncertainty during multi-step tasks.
The move: treat invisible backend work as a user-facing state. A chat interface can make teams forget that users are still navigating a system. They press buttons, upload files, wait for checks, and need to know whether their action landed. Visibility of system status prevents the user from filling silence with anxiety. Write status turns in three parts: receipt, work, and expectation. Receipt confirms the user's action. Work names what the assistant is doing in user language. Expectation says what will happen next or when the user can intervene. This is especially important when the assistant calls APIs, waits on…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in