> ## Documentation Index > Fetch the complete documentation index at: https://docs.threetone.in/llms.txt > Use this file to discover all available pages before exploring further. # Create your first agent > Create a blank agent in the dashboard, prepare its behavior, and understand how to preserve a configuration draft. 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. ## Before you begin Sign in to the [Threetone dashboard](https://threetone.in/app/agents) 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](/agents-platform/overview#current-availability) before planning a live demonstration. ## Create and configure 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. 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](/agents-platform/configure/agent-behavior/prompting) to separate instructions, knowledge, and actions. Start without tools or knowledge attachments so you can review the basic behavior clearly. 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](/agents-platform/configure/voice-and-language/overview). These choices can be stored in a server draft, but compatible speech settings do not unblock voice publication. 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](/api-reference/agents-platform/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](/agents-platform/guides/chat-mode) and the [publication workflow](/agents-platform/deploy/versioning). Read the selected branch and draft through [Get agent](/api-reference/agents-platform/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 | Problem | What to check | | - | - | | Agent creation is unavailable | Confirm the active workspace and your permission to create agents. | | A speech or language choice did not save | Those dashboard controls are previews. Use the voice and language API workflow, then read the saved branch back. | | Voice or custom-model Publish fails | These publication paths remain unavailable. Preserve a server draft; use a compatible managed text-only configuration for publication. | | A newer version exists | Review the latest published configuration and reconcile the local working copy before publishing. | ## Continue Prepare source documents and inspect their dependencies. Understand branches, drafts, and configuration publication. Create an agent configuration from a server-side integration. 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](/agents-platform/overview#current-availability) before planning a live test. Those dashboard controls are previews. Use the [voice and language authoring workflow](/agents-platform/configure/voice-and-language/overview), then confirm the saved server draft. Voice publication remains unavailable. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.