Write a good agent script
Updated
Quick answer
A Vyora script has an Intro Message, which is read out word for word, plus Introduction & Objective, Response Guidelines, Task, FAQ and Sample Conversations. Put the step by step flow in Task, use variables like {{callee_name}} for details from your contact list, and keep the intro short because every connected minute costs credits.
What each section does
Open the agent from Agents and click Edit. The script is on the right of the Setup tab.
| Section | What to put in it |
|---|---|
| Intro Message | The first thing the agent says. It is read out exactly as written. |
| Introduction & Objective | Who the agent is, which business it calls for, and the goal of the call. |
| Response Guidelines | How it should talk: tone, length of replies, what never to say. |
| Task | The conversation step by step: greet, confirm, ask, handle the answer, close. |
| FAQ | Common questions callers ask, with the exact answers. |
| Sample Conversations | Example calls that show the agent how a good call sounds. |
Click Save Changes (or press Ctrl+S) when you are done.
Write the intro message
- Keep it to one or two sentences: who is calling, from which business, and one question.
- Do not leave placeholders such as [Company Name] or "Sir/Ma'am". The intro is read word for word, so the agent says them out loud. Vyora flags these under the script before you save.
- Do not write two options like "Mr/Mrs". The agent reads both.
- New agents keep up to 500 characters of intro.
Use variables for contact details
Variables are filled in before each call from your contact list or the test call form.
- Under Variables, add a name using letters, numbers and _ only, for example
order_id. - In any section, type
@and pick the variable, or type it as{{order_id}}.
Every agent has {{callee_name}} and {{mobile_number}}. Every variable you add becomes a column you must fill in your campaign CSV.
Things to avoid:
- Single braces like
{name}are not a variable. Use{{name}}. - A variable that is not in the Variables list is not filled in.
- A variable for something the caller says during the call, like their preferred date. It is always empty because variables are filled before the call. Ask the question in Task instead.
Length limits and the 1,500 character error
Some older agents showed "String should have at most 1500 characters" when clicking Create Agent. That limit applied to the Task section at creation. Agents are now created with the full script, so you should not see it. If you do, shorten Task, create the agent, then paste the full Task in the editor and save.
"Half my script disappeared after I saved"
Check the message you got when you saved:
- "Saved, except: ... Please save again." Part of the save failed. The sections or settings it names kept their old text. A common cause is a voice that cannot speak the secondary language. Fix what it names and click Save Changes again.
- "Someone else saved this agent..." A teammate saved at the same time. Reload and check the script reads the way you want.
On older agents with a very long script, sections may have been cut when the agent was created. Paste the full text back into the editor and save.
Tips that save credits and work better
- Short calls cost less. Every connected call is charged by the minute, rounded up. A tight intro and a Task that gets to the point keep most calls inside one minute. See How credits are charged.
- Put long product details in a knowledge base, not the script. See Add a knowledge base.
- Use the AI options on selected text. Select text in a section to get Improve writing, Make shorter, Sound natural on a call and Translate to.... Read the result before saving.
- Test after every change with Test call.
Related articles
Still stuck?
Write to us with what you tried. A person on the team reads every message and replies by email.