Conductor is an assistant inside the dashboard, and it is the first thing you see: Home in the sidebar is Conductor. You describe what you want in plain language and it acts on your workspace:
- Build and edit agents. Build a new agent from a short conversation, or propose changes to an existing one as diffs you accept or reject.
- Test. Write simulation test cases for an agent and run them as a batch.
- Investigate calls. Read selected or recent calls and summarise what went wrong.
- Build dashboards. Create an analytics dashboard from a request such as "call volume and latency by agent".
- Guide you. Produce step-by-step walkthroughs, and run them as guided tours that highlight each control on the page.
Needs keys Conductor uses OpenAI. Without a key it runs in mock mode: it picks actions with keyword rules and uses built-in templates, so every feature works for a demo but the content is generic.
Where to find Conductor#
| Entry point | Where | What it does |
|---|---|---|
| Home | First item in the sidebar, and where you land after signing in | Full view: Conductor History, the composer with attachments, model tier and credits, and the quick starts Build a new agent, Edit an agent and Analyze calls. |
| Conductor button | Agent builder header | Opens the edit panel for this agent: "Edits this agent with your approval". |
| Floating button | Right edge of every dashboard page except Home | Opens the Conductor side panel with context attachments and Guided tour. Open full view continues the conversation on Home. |
| Ask Conductor | Call History and Analytics headers | Opens the edit panel with the calls or analytics in view attached as context. |
| Ask Conductor about these calls | Call History selection bar | Opens the side panel with up to 10 selected calls attached. |
Home#
Home greets you by name and asks How can I help?. Type anything into the composer, or start from a quick start:
| Quick start | What happens |
|---|---|
| Build a new agent | Starts a conversation with the build_agent action. Conductor asks which business it is for, what the agent should handle and when to transfer, then builds the agent from your answer and links to it. See Build and refine agents. |
| Edit an agent | Asks Which agent do you want to edit?, then opens the edit panel for the agent you pick. |
| Analyze calls | Runs investigate_calls on your recent calls and summarises what is going wrong. |
Conductor History on the left lists your saved conversations, newest first, with Search chats and New chat. The old /conductor address opens Home.
Two kinds of Conductor conversation#
Conductor has two back ends. They look alike but do different things.
| Agent edit panel | Conductor conversations | |
|---|---|---|
| Opened from | Builder header Conductor, Edit an agent, Ask Conductor buttons | Home, floating button, Ask Conductor about these calls |
| Can change | One agent's configuration (prompt, tools, voice settings, flow) | Creates agents, test cases, batch tests and dashboards |
| Output | Proposed changes with a diff, Accept, Reject and Undo | A reply plus a result (new agent link, findings, tests, dashboard link, walkthrough) |
| Saved | In the browser tab only | As conversations in your workspace |
| Credits | Not charged | Charged per message |
| API | POST /agents/{agent_id}/copilot |
/conductor/... endpoints |
Actions in a Conductor conversation#
Every message runs one action. With auto (the default), Conductor picks it from your message.
| Action | Triggered by messages like | Result |
|---|---|---|
chat |
General questions | An answer from the attached context. |
build_agent |
"Build a receptionist for my physio clinic", or Build a new agent on Home | Asks for the details it needs, then creates the agent (single prompt, Premium voice, an end_call tool) and returns a link to it. |
investigate_calls |
"Why did my recent calls fail?", or any question with calls attached | Per-call issues and the most common patterns. See Call history. |
write_tests |
"Write test cases for this agent and run them" | New simulation test cases, optionally run. See Test and improve. |
run_tests |
"Run the tests" | A batch of the agent's existing test cases. |
build_dashboard |
"Build a dashboard of call volume and latency by agent" | A new analytics dashboard. See Analytics. |
walkthrough |
"Walk me through connecting a phone number" | Numbered steps with links, and a guided tour. |
Attach context#
Conversations can carry up to 10 attachments in total:
| Type | What Conductor reads |
|---|---|
agent |
Name, latest version and the first 1,500 characters of the prompt. |
call |
Status, duration, disconnection reason, sentiment and summary. |
dashboard |
Name and chart titles. |
qa_cohort |
Name, number of scored calls and average score. |
contact |
Name or number, number of calls and contact memory. |
node |
A conversation flow node (instruction and edges) or a multi-prompt state (prompt). |
file |
A text file (.txt, .md, .csv, .json) up to 200 KB; the first 8,000 characters are used. |
In the side panel, the paperclip opens Attach context with search tabs for Calls, Dashboards, Cohorts, Contacts, Agents and Nodes. On Home, the + button in the composer opens the same picker, and the paperclip next to it attaches a text file.
Attachments stay on the conversation, so later messages can refer to them.
Guided tours#
The side panel has a Guided tour box. Type a topic ("set up AI QA") and choose Show me, or choose Start guided tour under a walkthrough reply. The tour moves to each step's page and highlights the control, with Back, Next and Done.
Built-in tours cover connecting a phone number, adding a knowledge base, running a batch call, setting up AI QA, creating an alert, receiving webhooks, reviewing calls, building an analytics dashboard and setting up the workspace. Any other topic gets the "Build and launch an agent" tour. With an OpenAI key, Conductor can also write steps for other topics.
Credits#
Each message in a Conductor conversation costs credits by model tier:
| Tier | Credits per message | Model |
|---|---|---|
| Fast | 0.5 | gpt-5.6-terra-mini |
| Default | 1 | gpt-5.6-terra |
| Advanced | 3 | gpt-5.6-terra |
Choose the tier in the composer on Home. The side panel always uses Default.
- Free: 30 credits per user per day and 200 credits per workspace per day. Days reset at midnight UTC. A message is free only if both allowances cover it.
- Pay-as-you-go: after the free credits, $0.30 per credit, up to a monthly limit. Turn it on in Settings, Reliability: Conductor pay-as-you-go and Conductor monthly limit (AUD). It is off by default.
- Out of credits: the API returns
402witherror_codeconductor_credits_exhausted(free credits used, pay-as-you-go off) orconductor_limit_reached(monthly limit reached).
Home shows your free credits left today next to the composer. Get Conductor credits returns the full picture: yours and the workspace's free credits left, and pay-as-you-go spend this month. Each message is charged as free_user, free_workspace or paid, and paid credits appear on the workspace's usage.
API#
| Method and path | Description |
|---|---|
GET /conductor/capabilities |
Actions, tiers, max_attachments (10) and attachment types. |
GET /conductor/credits |
Free credits left today and pay-as-you-go spend this month. |
GET /conductor/ledger?limit=&mine= |
Credit ledger rows (up to 500). |
GET /conductor/walkthrough?topic= |
A built-in walkthrough for a topic. |
POST /conductor/sessions |
Start a conversation. Body: optional title, attachments. |
GET /conductor/sessions |
Your 50 most recent conversations. |
GET /conductor/sessions/{id} |
One conversation with its messages. |
PUT /conductor/sessions/{id}/attachments |
Replace a conversation's attachments. |
DELETE /conductor/sessions/{id} |
Delete a conversation. |
POST /conductor/sessions/{id}/messages |
Send a message. Body: content (up to 8,000 characters), tier (fast, default, advanced), action (default auto), attachments. |
POST /agents/{agent_id}/copilot |
Agent edit panel: messages (1 to 40). Returns reply and proposals. |
POST /generate-agent |
Build an agent from a description (10 to 4,000 characters). |
curl -X POST https://api.tried.com.au/conductor/sessions/$SESSION_ID/messages \
-H "Authorization: Bearer $TRIED_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"content": "Why did my recent calls fail?",
"tier": "default",
"attachments": [{ "type": "call", "id": "call_b734725b6c060c5764b31803" }]
}'{
"reply": "I looked at 1 call. 0 had no problems. The most common issues: not successful (1), negative sentiment (1).",
"action": "investigate_calls",
"result": { "type": "investigation", "calls": [], "patterns": [{ "issue": "not successful", "calls": 1 }] },
"mode": "llm",
"credits": { "charged": 1, "source": "free_user", "cost": 0 },
"credit_status": { "tiers": { "fast": 0.5, "default": 1, "advanced": 3 } }
}mode is llm when OpenAI planned the turn and mock when the rules did (including when the OpenAI call fails). The examples are trimmed.