Routing edges

Documentation Index

Fetch the complete documentation index at: https://docs.cogniagent.ai/llms.txt

Use this file to discover all available pages before exploring further.

A routing edge connects one actor to another. The edge carries an activation prompt — a short description of when this route should fire. The platform uses it to decide which actor handles the next turn.

​

Draw an edge

​

Writing good activation prompts

Activation prompts read like instructions to a smart teammate, not configuration. Think of them as the trigger description an account manager would give to their team.

​

Good

When the user reports a billing problem (a charge they don’t recognise, a duplicate, a refund request) and has provided their account email.

Whenever the conversation touches scheduling — picking a time, rescheduling, or asking when something is available.

When the user wants to talk to a real person, expresses frustration, or asks about something outside our published policies.

​

Less useful

intent = billing

if user said pricing

classification: support_tier_2

The platform can route on the precise language; you don’t need to compress to keywords.

​

Multiple edges from the same actor

An actor can have many outgoing edges — one per route it should consider. When the routing layer evaluates the user’s latest turn, it considers all outgoing edges from the current actor and picks the one whose activation prompt fits best.

​

Edge labels

Labels are short — 1 to 3 words. The platform auto-generates them from your activation prompt every time you save the prompt. If the auto-generated label isn’t what you want (e.g. “Sales” when you meant “Outbound Sales”), you can override it in the panel’s label field. The activation prompt is the source of truth for routing — labels are only for canvas readability.

​

What the routing layer actually does

When the user sends a message, the platform evaluates:

1. Is the current actor’s job done? If the actor’s Definition of Done is satisfied — hand off.
2. Should we hand off anyway? Check each outgoing edge’s activation prompt against the conversation. If one fits clearly, route to that target.
3. Otherwise — stay on the current actor.

You don’t write any of this logic. The combination of edges + activation prompts + Definition of Done gives the platform everything it needs.

​

Edge handles (advanced)

Most edges connect from an actor’s default output to the target’s default input — that’s the only case for free-form actors. When you build scripted actor flows with ai-condition steps, edges have handle-specific outputs (true / false). You don’t usually touch this directly — the step builder handles it for you.

​

Delete an edge

Click the edge, then press Delete (or use the delete affordance in the panel).

​

Reusing the Sales Triage flow

The running example throughout these docs uses two edges: The Start → Triage edge needs no activation prompt — it’s the default entry point.

​

Next