Audience
- Operators iterating on call behavior and tone
- Admins maintaining quality across multiple agents
Prerequisites
- Access to prompt tools in workspace
- Existing agent prompt draft
- Test scenario for validation
Plan and role requirements
- Prompt tooling availability may depend on plan.
- Editing production prompts should be limited to trusted roles.
Steps
1) Draft or import prompt
- Open prompt tools.
- Paste or draft your prompt content.
- Define desired behavior outcomes.
Already have a custom prompt? When you sync an agent whose prompt wasn’t built in Prompt Studio, it’s rewritten into Voqo’s standard format — only your call-handling flows carry over; bespoke wording, tone, and special instructions are not retained. Prompt Studio shows a warning when this applies. Your previous prompt is kept in version history (you can roll back), and you can review the full result in the Advanced tab before you save.
2) Refine with prompt assistant
- Run refinement suggestions.
- Apply improvements for clarity and constraints.
- Save refined output for test.
3) Test in writing
- Open the Test tab. Your agent opens the conversation with its greeting first — just like a real call, where it speaks before the caller does. Type a caller message to continue.
- Compare output to expected behaviour.
- Iterate until response quality is stable.
4) Deploy to agent
- Update the target agent prompt.
- Run controlled call test.
- Verify no regression in key workflows.
When to use prompts vs skills
- Use prompts for language, behavior, and instruction quality.
- Use skills for reusable structured capabilities and tool-like functions.
Troubleshooting
Prompt quality regresses after update
- Roll back to known stable prompt version.
- Re-test with same scenario set.
- Apply smaller incremental changes.
Tool output differs from call behavior
- Confirm deployed prompt matches tested prompt.
- Check skills/functions attached to agent that may alter behavior.

