Skip to main content
In this quickstart you’ll build a small Sales Triage flow with three AI agents: a Triage agent that figures out what the user wants, then hands off to a Product Specialist or a Pricing Specialist. The exact flow used as the running example in the rest of these docs.

​
Before you start

  • A CogniAgent workspace. If you don’t have one, sign up.
  • About 10 minutes.
You don’t need to connect any integrations or set up a knowledge base for this quickstart. The flow runs end-to-end on the built-in model.

​
1. Create the flow

1

Open Conversations

From the sidebar, click Conversations. You land on the flow list.
Empty conversation flows list
2

Click New Flow

A blank flow opens straight away — no modal, no questions. You start on a canvas with a single Start node and an “Add Actor” button.
Empty canvas with Start node
3

Rename the flow

Double-click the Untitled Flow title at the top and rename it to Sales Triage. Press Enter.

​
2. Set the global context

Global context is shared knowledge every agent inherits — your company name, product names, tone of voice. Setting it once means you don’t have to repeat it on every agent.
1

Open Flow settings

Click the gear icon (Flow settings) in the bottom-right toolbar.
2

Paste a short context block

Under Global Context, paste:
Flow settings with global context filled in
3

Save and close

Click Save Changes, then close the panel.

​
3. Add the Triage agent

1

Click Add Actor

In the bottom toolbar, click Add Actor. Type Triage as the name and click Create.
Add Actor popover
The Triage agent appears on the canvas, automatically connected from the Start node.
2

Open its config

Click the Triage agent. The config panel opens on the right.
3

Fill in Context, Instructions, and Definition of Done

Triage actor config filled in
Click Save Changes.

​
4. Add two specialist agents

Repeat the Add Actor flow twice — once for each specialist.
After both are created, your canvas has four nodes. They’re auto-wired from the Start node — we’ll fix the routing next.

​
5. Wire the routing edges

You want this topology: Start → Triage → (Product Specialist or Pricing Specialist), with Triage deciding which specialist takes over.
1

Delete the wrong edges

Click the line connecting Start to Product Specialist. Press Delete (or use the delete affordance). Do the same for Start → Pricing Specialist.
2

Draw Triage → Product Specialist

Hover over the Triage node’s bottom edge. A handle appears. Drag from the handle onto the Product Specialist node. An edge appears.
3

Add the activation prompt

Click the new edge. The Activation Condition panel opens. Paste:
When the user asks about product features, integrations, capabilities, security, the roadmap, or how something works in the product.
Edge activation panel
Click Save. A short label appears on the edge — generated by AI from your prompt.
4

Repeat for Pricing Specialist

Draw an edge Triage → Pricing Specialist, click it, paste:
When the user asks about price, plans, seats, discounts, free trial, or wants a quote for an Enterprise contract.
Save.
Your canvas now looks like this:
Sales Triage flow on canvas

The finished Sales Triage flow.

​
6. Test it

Click Test in the bottom toolbar. A drawer opens with a chat input.
1

Send a pricing question

Type how much does Acme Pro cost? and press Enter.Within a couple of seconds, the Pricing Specialist replies with the pricing details from your global context. Below the reply, a debug panel shows the routing trace:
  • [global] routeToActor → Triage (the global router picked Triage)
  • [branch] routeToChild → Pricing Specialist (Triage handed off to Pricing because the activation prompt matched)
Test drawer showing routing trace
2

Try a product question

Type actually, does it support SSO? and watch how routing handles a topic change mid-conversation.
Multi-turn test session
Every test message is logged in Conversations (bottom toolbar) with the full transcript, routing decisions, and any tool calls — useful for debugging later.

​
What’s next

You have a working multi-agent flow. From here you can:

Connect a channel

Wire the flow to a Widget, Gmail, Slack, Teams, or Phone — so real users can talk to it.

Add capabilities

Give your agents access to knowledge bases, integration actions, and custom tools.

Deploy it

Take it live so it can handle real inbound messages or outbound campaigns.

Learn the concepts

Understand actors, edges, context inheritance, and focus modes in depth.