> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/skills/voice-agents.md). # Voice Agents What Claude can do with your Dapta voice agents once connected: create, configure, and calibrate agents, then review how their calls perform. Once Dapta is connected to Claude, you can manage your voice agents in plain language. Just describe what you want, and Claude handles the voice-agent work in your connected workspace. Claude only ever sees and acts inside that one workspace. {% hint style="info" %} When Claude changes anything (an agent or its prompt), it shows you a preview first and waits for your confirmation before applying it. Reading and reviewing never changes anything. {% endhint %} ## Build and configure Ask Claude to set up a new voice agent and it walks you through a few quick steps: pick a starting template, choose a language, and share your company details. Claude writes the agent's prompt for you and creates it in your workspace, ready for a test call. If you share your website, Claude can pull your company details from it automatically so you type less. **Try saying:** * "I want to create a voice agent for my dental clinic." * "Set up a new outbound cold-call agent in English." * "Build me a receptionist voice agent for my company." Once an agent exists, you can fine-tune how it sounds and behaves. Ask Claude to review the current setup or adjust things like speaking speed, how natural the voice sounds, or how easily the agent lets callers interrupt. Every change is previewed before it goes live. **Try saying:** * "My agent speaks too fast, can you slow it down?" * "What voice settings does my agent use right now?" * "Make my agent's voice sound more natural." You can also improve how the agent actually talks. Claude can look at recent calls, diagnose what is working and what is not, then draft a better prompt (for example, stronger objection handling or clearer pronunciation) and, with your approval, apply it to the live agent. **Try saying:** * "Improve my voice agent's prompt and apply it." * "My agent doesn't handle objections well, fix it." * "Update my agent so it reads phone numbers more clearly." *** ## Calibrate and review performance Beyond setup, Claude can help you understand what each agent captures and how it is doing on real calls. Ask what an agent records or extracts, and Claude explains the details it collects on each call and how often those fields actually get filled. **Try saying:** * "What does this agent capture from calls?" * "Which details are actually getting filled in?" When you want to know how an agent is performing, ask for the numbers. Claude pulls your call totals, connection and success rates, average duration, credits used, sentiment, why calls ended, and how calls break down by outcome, presented the same way as your platform metrics. **Try saying:** * "Analyze my agent and give me a full report." * "How many calls did I get this week and what was the connection rate?" * "Categorize my last 100 calls by outcome." You can dig into the human side too. Claude can summarize the thumbs-up and thumbs-down votes and written comments people leave on calls, show satisfaction over time, and surface the calls that got negative feedback. **Try saying:** * "What's my agent's satisfaction rate?" * "Show me recent negative feedback and comments." To hear what was actually said, ask Claude for your call recordings. It lays out the calls that have a recording in a clean table with the key details and a link you can open to listen back. **Try saying:** * "Show me the recordings from my last 20 calls." * "Let me listen to the calls from February 3rd." Claude can also tell you the best times to reach people. It looks at your call history to find the strongest hours and weekdays to dial, and the windows to avoid, so you can schedule outbound calling when it actually works. **Try saying:** * "What are the best hours to call for my sales agent?" * "Which days of the week get the highest connection rates?" Finally, Claude can find your sales-ready leads. It first works out what "qualified" means for that specific agent, then pulls the matching leads and shows you a simple funnel from total calls to connected to qualified. **Try saying:** * "Find me the qualified leads from my outbound sequence." * "Show me a conversion funnel for my sales agent's calls." {% hint style="success" %} Not sure where to start? Just tell Claude what you are trying to do in your own words. It will pick the right approach and, for anything that makes a change, confirm with you before applying it. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dapta.ai/dapta-mcp/skills/voice-agents.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.