Build an agent by describing it: a walkthrough of Composer
Composer is the assistant inside the Vaakyo console. Describe the agent you need in plain words; it writes the prompt, picks a voice, adds tools and tests it with you.
The Vaakyo team2 min read
- Composer
- Getting started
Writing a good voice agent prompt, choosing a voice and setting up analytics fields takes time the first few times. Composer does that first draft for you from a description, and you stay in control of every change.
Start with a sentence or two
Open Composer in the console and describe the agent the way you'd brief a new colleague:
Create an agent that confirms cash-on-delivery orders in Hindi. It should read back the order and amount, confirm the address and ask if they'd like to pay online instead.
Composer asks a question if something important is missing (which language, which store name), then gets to work.
What it does
Composer works through its helpers and shows each step:
- Builder lists suitable voices, writes the prompt in a structure that works on calls, creates the agent and adds analytics fields for the answers you care about.
- Tester runs simulated conversations against the new agent and reports what went wrong.
- Debugger reads calls, transcripts and logs when something isn't working.
- Analyst looks at your call analytics and usage.
You can read the prompt it wrote and every setting it chose before you use the agent.
You approve what matters
Composer asks before it does anything you'd want to check. You choose how much it may do on its own in each conversation, and some actions always need your approval in every mode: placing a real call, starting a campaign, connecting a phone number to an agent, and creating or changing a webhook.
Keep going in the same conversation
Composer remembers the conversation, so you can refine:
Make it more polite with older customers, and if they mention a wrong address twice, transfer to our support line.
Every change it makes is in the agent's version history and in the audit log as "you via Composer", so you can see and undo what changed.
Good habits
- Describe the outcome and the edge cases, not the wording.
- Always test the agent yourself in the browser before attaching a number.
- Ask Composer to explain a call that went wrong: paste the call or ask about "the last failed call".