Part of this behaviour depends on an activation AGENEON completes before it goes live for your workspace. The page in your workspace states the current state truthfully.
Check in this order
First, is the conversation with a person? When a conversation is handed off, the Agent stops replying by design until a person resumes it from the Inbox.
Second, is the channel connected? A channel that needs attention or whose permission expired delivers messages that nobody can answer. The Connections page shows the state.
Third, is the workspace within its AI usage boundary? AGENEON bounds AI spend per workspace; when a boundary is reached, new Agent turns are held rather than dispatched. The Help page shows this state.
Fourth, is the workspace suspended or its subscription inactive? Both stop autonomous replies while leaving your data readable.
What the Help page tells you
Open Help and ask. AGENEON reads your workspace's actual state, names what it found with the evidence, and either points you to the fix or escalates to AGENEON support with everything it learned, so you never repeat yourself.
Live delivery
Replies leaving AGENEON to a customer on a provider channel depend on that provider's activation for your workspace. Until a channel is fully activated, the Agent's replies are recorded in the conversation but may not be delivered externally. The Channels page states the activation state truthfully.
Verified against the product at PLC-7