Design status messages that keep chatbot users oriented during delay, lookup, and handoff.
Status turns hidden work into visible progress. In a chatbot, the user cannot inspect the machinery. They only see messages, pauses, and outcomes. Name the operation Avoid generic fillers like "processing." Say what the bot is checking, generating, searching, validating, or sending. The more consequential the task, the more explicit the status should be. Set expectation If timing is predictable, say it. If timing is not predictable, say what happens next. This is especially important for payments, access, health, legal, HR, and support contexts where users may start a duplicate channel if they feel abandoned. Preserve control Let the user…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in