Iam building a workflow for my agent. From the Start, I route to a new subagent called User Intent | ElevenLabs | Page 1

AI-generated Answer for trinhthiquynhanh

Short answer: there’s nothing in the official docs that says LLM-condition routing ignores the user’s first message. Edges with Transition type = LLM Condition are evaluated “in real time to determine the appropriate path,” and the label text is not parsed by the LLM. So if your agent isn’t leaving “User Intent Classification,” it’s almost certainly a configuration issue with the edge(s), not a first‑message quirk. See Edges and flow control and the note about Label vs LLM Condition. (elevenlabs.io)

What to check (fast):

On the path out of “User Intent Classification,” confirm Transition type is set to LLM Condition and the condition text is in the LLM Condition field; the Label is human-readable only. (elevenlabs.io)
Make sure you created a forward edge from “User Intent Classification” to “Collect Booking Details.” (elevenlabs.io)
Temporarily remove or disable any other outgoing edges from the node to rule out conflicting routing. The docs don’t specify tie‑breaking, so keep conditions mutually exclusive as a best practice. (elevenlabs.io)
Use Simulate Conversations to send exactly: “Hi, I want to book a new appointment for today.” and verify the transition happens; this is the recommended way to validate routing logic outside of live calls. (elevenlabs.io)

If it still doesn’t route, capture a short simulation or dashboard test showing the edge configuration (Transition type + LLM Condition text) and contact support; include the agent ID and conversation ID to speed triage. (help.elevenlabs.io)

#Iam building a workflow for my agent. From the Start, I route to a new subagent called User Intent