Skip to main content
Instructions define what your Agent does, what it represents, how it should handle customer interactions, and which boundaries it must follow. Treat them like an operating guide for a new team member: be specific, resolve conflicting rules, and include representative examples.

Example Prompt

Below is an example Instructions prompt for a restaurant agent.
For best results, give your Agent a clear role and measurable goals. Use the Agent examples as starting points, then adapt the workflow, boundaries, and success criteria to the real business.

Best Practices

  • Be Clear and Specific: Provide detailed instructions to ensure the agent understands how to handle different scenarios.
  • Reflect Your Brand: Make sure the agent’s personality and tone align with your brand identity.
  • Regular Updates: Update the instructions regularly to keep the information current and accurate.
  • Test and Refine: Continuously test the agent’s performance and refine the instructions based on feedback and observations.
Review the instructions whenever the workflow, policy, or connected systems change. Test the hardest expected cases before publishing.

IVR navigation

Outbound Agents can navigate interactive voice response (IVR) menus by sending DTMF keypad tones. Add instructions that explain which person or department to reach and when to send each key.
Use standard speech mode for this workflow. DTMF tags are processed by text-to-speech (TTS); native speech-to-speech output does not use this tag handler.

Send keypad tones

Have the Agent output <DTMF digits="1"/> to press 1. Vida sends the keypad tone and removes the tag from the spoken response. The digits value supports 0–9, *, #, and the DTMF keys A–D. Each comma represents a 0.5-second pause. Without commas, the default gap after a key is 0.5 seconds. Commas immediately after a key set its gap: four commas mean a 2-second gap, replacing the default.

Example instructions

Adapt this prompt to the destination and the goal of the call:
Test a staged outbound call against the destination IVR before publishing. Menu timing varies, so prefer listening for the next prompt over sending a fixed sequence for several menus. Use commas when the destination needs an explicit delay.