Skip to main content
Start with a small, specific task, such as answering questions about a support process. This guide ends with a saved agent configuration you can inspect and revise.
Recording pending for Create your first agent. No playable video is available yet.

Recording pending: Create your first agent. Follow the written guide below.

​
Before you begin

Sign in to the Threetone dashboard and select the intended workspace. You need permission to create and edit agents. Blank-agent creation stores an initial configuration; it does not establish an execution-ready version.
This walkthrough covers configuration authoring. Voice and custom-model publication are currently unavailable, as are signed-token session initiation, outbound calling, traffic deployment, and automated response-test execution. See current availability before planning a live demonstration.

​
Create and configure

1

Create a blank agent

Open Agents, select Create Agent, then choose Blank Agent. Enter an Agent Name that describes its purpose, such as Support process guide, and select Create Agent.The dashboard opens the new agent’s workspace. Keep its identifier when connecting the configuration to an integration.
2

Write a focused prompt

Define the agent’s task, the information it can use, and what it should do when an answer is missing. Write a short first message that tells the user what help the agent provides.Use the prompting guide to separate instructions, knowledge, and actions. Start without tools or knowledge attachments so you can review the basic behavior clearly.
3

Choose the response model and prepare speech settings

Use the LLM section to select an available response model. The dashboard’s Voices, Language, and ASR controls are previews whose changes are not saved.For voice configurations, prepare the base language, ASR and TTS models, and a compatible saved voice using the voice and language authoring guide. These choices can be stored in a server draft, but compatible speech settings do not unblock voice publication.
4

Preserve and review the draft

Review the editor’s pending changes and selected branch. The dashboard working copy is local; it is not automatically a saved server draft. Use Create agent draft with a complete snapshot and an explicit branch to preserve work through the API.The default blank agent is a voice configuration, so Publish cannot complete in the current implementation. For a managed text-only configuration, follow Chat mode and the publication workflow.
5

Read the saved version back

Read the selected branch and draft through Get agent, using the reference’s supported read options. Distinguish the initial version, saved server draft, and unsaved editor values.Retain the agent, branch, and initial version IDs. Saving a draft does not create a newly published version or start a conversation.

​
What you should have

You should have an agent in the intended workspace and a reviewed authoring plan. If you used the server-draft workflow, confirm that the draft was stored. Record resource IDs rather than relying on display names, and do not describe pending editor changes as published.

​
Troubleshooting

​
Continue

Add knowledge

Prepare source documents and inspect their dependencies.

Review versions

Understand branches, drafts, and configuration publication.

API quickstart

Create an agent configuration from a server-side integration.

Configure an agent

Understand the configuration fields and ownership boundaries.

​
Frequently asked questions

No. Publication saves a reviewed configuration version on the selected branch. Starting a session or deploying traffic uses a separate execution path. Check current availability before planning a live test.
Those dashboard controls are previews. Use the voice and language authoring workflow, then confirm the saved server draft. Voice publication remains unavailable.