Reading the team diagram

The canvas in the Builder is an accurate map of who answers, who helps, and how calls arrive.

Nodes are agents

Each box is one agent. Badges mark the kind: the main agent is where inbound calls land first, voice agents speak to callers, and text agents work silently as quiet helpers. Tapping a node opens that agent's editor drawer.

Four kinds of line

• Solid teal — transfers. The caller moves from one voice agent to another, mid-call.
• Dashed amber — subagents. An agent quietly asks a colleague for help and gets the result back; the caller stays put and hears nothing.
• Dashed muted — inbound lines. The rail on the left shows every way real calls reach the team: each connected phone number and SIP registration, pointing at the agent that answers. Browser test sessions are throwaway and never drawn here.
• Dotted claret — hand-backs. Where a transfer to a human lets the human key the caller back to an agent, the line is labelled with the key the human presses.

The graph follows the conversation

When a change lands, the new or changed node gets a halo and the camera flies to it. While the assistant is mid-edit the canvas softens under an assistant is editing — provisional chip — what is drawn may still move until the change lands.

Getting around

Drag pans, scroll zooms. The −, fit and + buttons float at the canvas's top right — fit is the quick way home — and a quiet caption at the bottom left keeps count: agents and zoom. For a full-width graph, hide the chat with the ✦ button at the top left; the same button floats in place to bring it back.

The connected to draft tag

Endpoints that were already connected keep answering the live version while a draft is edited. An endpoint deliberately connected while drafting carries a NEW tag on the canvas — it answers the draft right away, and stays connected after Go live. That tag is the sign a real number is pointed at unfinished work — usually exactly what is wanted while testing. The full story is in Drafts, versions & going live.