Using the Chat Window
A walkthrough of everything you can see and click when a workflow pauses and asks you to respond via the chat window.
The Window
When a workflow needs your input, the chat window appears as a panel — by default, a floating panel anchored to the bottom-right of the screen, though the app you're using may dock it into a sidebar or another fixed spot instead. The header shows the request's title and, if the request has a response deadline, a countdown timer. Once the deadline passes, the composer is disabled and no further replies can be sent for that request.
Message Bubbles
Below the header is the conversation itself — a scrollable list of message bubbles, oldest at the top, newest at the bottom. The window automatically scrolls to the latest message as new ones arrive.
| Bubble | Meaning |
|---|---|
| Left-aligned, marked S | A message from the workflow/system — the prompt or question you're being asked to respond to. |
| Right-aligned, marked U | Your own reply, shown immediately after you send it. |
Before the first message arrives, the window shows an empty state ("No messages yet.") rather than a blank panel.
Replying with Text
Type your reply into the text box at the bottom and press Enter to send it, or Shift+Enter to add a new line without sending. The text box only appears when the current turn is a plain conversational one — if the workflow instead wants a decision or a filled-in form, see the sections below.
Quick-Reply Chips
Some requests come with a row of suggested replies — short buttons like "Yes," "No," or "Tell me more" shown just above the text box. Clicking one either sends that reply immediately or fills it into the text box for you to edit first, depending on how the app you're using has configured the window. The chips shown are decided by the request itself, not fixed in the window — a different request may show different (or no) chips.
Action Buttons
Below the composer, an action bar may show buttons such as Approve, Reject, or Escalate — the same decision actions available in every other HIL presentation type. Sending a plain chat message and clicking a decision action are both ways of responding; which ones are offered depends on what the workflow is asking for.
Inline Forms
If the workflow needs structured information rather than free text — several fields, not just a sentence — that turn renders as an actual form inside its own bubble, in the same conversation, instead of popping up a separate window. Fill it in and use the action bar to submit it; the filled values become your reply for that turn. Once a form bubble has been submitted, it becomes read-only — you can't go back and edit an answer you've already sent for that step.
If a Message Fails to Send
If sending a reply fails (for example, a network problem), that message's bubble shows "Failed to send." with a Retry button, instead of failing the entire conversation silently. Click Retry to attempt sending that same message again.
What You Can't Do Yet
Once you've responded and the workflow moves on, that particular chat session is done — you can't continue chatting back-and-forth with the workflow beyond the single request you were asked to answer. If the workflow needs more from you later, it will open a new request. See FAQ & Limitations for details.