Dashboard — start here
Use AI Agents to generate a draft, then work through Assistant Details, Variables, Call Settings, Integrations, Knowledge Base, and Recent Calls. Use Test before switching the agent to Live.
Follow one practical path from a plain-language idea to a tested agent with clear instructions, a suitable voice, trusted knowledge, safe call behavior, and a measurable result.
Your course progress will appear in a moment.
The Academy teaches one complete workflow: decide what the agent must accomplish, build it in the dashboard, give it facts and a voice, test the cases most likely to fail, send controlled traffic, and improve it from actual call evidence.
Do not begin by writing a giant prompt. Begin with one job and a visible definition of success—for example, “capture a qualified property enquiry and obtain permission for a human follow-up.”
Every lesson has one outcome, exact dashboard actions, a complete example, a practical completion step, and the matching API path. Complete them in order the first time.
A one-page agent brief
A saved agent in Draft
All six builder areas reviewed
A complete, testable prompt
A voice tested for the job
Grounded PDF or website facts
Controlled live traffic
A repeatable improvement loop
The course uses a property-enquiry agent because it demonstrates inputs, outputs, knowledge, human follow-up, and a measurable result without requiring a complex integration.
Both paths create the same kind of agent. The Academy starts with the dashboard because it makes every setting visible; developers can open the linked API equivalents afterward.
Use AI Agents to generate a draft, then work through Assistant Details, Variables, Call Settings, Integrations, Knowledge Base, and Recent Calls. Use Test before switching the agent to Live.
Use POST /agents/generate for an unsaved draft, POST /agents to create it, then attach knowledge, choose a voice, assign a number, or dispatch calls through the public API.
Dashboard generation creates a saved draft and enriches it. The API endpoint POST /agents/generate returns a draft only; your application must review it and call POST /agents to save it.
Each lesson produces something the next lesson needs. Skipping a step usually creates a problem that appears only during a call.
Choose one audience, one call direction, one primary job, a human fallback, and the data that proves success.
Describe the job, choose a template or start from scratch, and keep the new agent in Draft.
Review all six builder areas instead of treating the generated draft as finished.
Write identity, language, sequence, knowledge, guardrails, recovery, and closing sections.
Add input and output variables, a matching voice, approved knowledge, and only the integrations the job needs.
Test the happy path, confusion, correction, silence, refusal, missing knowledge, transfer, and closing.
Switch to Live only after testing, then assign a number or send a small controlled outbound batch.
Read transcripts and outcomes, change one cause at a time, and repeat the same test set.
Having these decisions and source materials ready turns agent creation into a review exercise instead of guesswork.
Continue to the complete build course. It includes the exact builder order, a full prompt, variables, testing, and a safe launch plan.