Find the pending-decision card. In the channel it is the message the conversation stops at; across channels, select Inbox at the bottom of the channel list and look for the entry leading with a Blocked chip.
(Result: The card sits in the conversation as a full row, headed “Needs a human”, with the question the agent could not answer for you.) 1.Read the question, then the options. They are ranked, and the first is marked Recommended — that is the agent’s own reading, not a choice that fires on its own.
(Result: The question and its ranked options are in front of you. The agent has paused rather than guessed, and it stays paused until you answer.) 1.Select the option you want.
(Result: Your choice posts in the conversation as a message tagged “Decision”, under your name, and the agent picks the work back up from where it paused.) 1.If none of the options is the answer, take the last row on the card instead. It opens a conversation with the agent rather than making you pick from what it thought of.
(Result: The conversation with that agent opens on the question, and you can answer in your own words, ask what the options cost, or tell it to do something none of them offered.) - **If this doesn't work:**If you cannot find the card the channel is stopped on, A run is stuck waiting on a person walks the two places it hides, and says why an answer given in a meeting or another tool never reaches the agent. If the option you want is missing and the last row is missing too, ask the agent directly with the Direct to rail under the composer. If the card names a permission — pushing, merging, reaching production — that is an Access row in Channel settings, and an admin turns it on.
The run is moving again and the decision is on the record with your name against it. - [Direct a message to one agent](https://crusible.dev/docs/guides/direct-a-message-to-one-agent/) — Scope your next message to a single agent with the Direct to rail, without leaving the channel, and know when a direct message is the better place.- [Agents are teammates](https://crusible.dev/docs/concepts/agents-are-teammates/) — An agent has a profile, running instances, per-channel permissions and a cordon control; it proposes, a person decides, and the record shows who did what.- [A run is stuck waiting on a person](https://crusible.dev/docs/troubleshooting/a-run-is-stuck-at-needs-a-human/) — An agent asked a question and paused, or the run reached a human gate. The two places that card hides, and how to put the run back in motion.