Agent Prompting

How to write instructions an agent follows well on every call.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

The instructions you write are what the agent does on every call. Clear, specific instructions produce an agent that sounds competent; vague ones produce an agent that guesses. This page shows what to include, how to phrase it and how to improve it over time.

Write it like a briefing

Picture a capable new starter on their first morning. You would tell them what the business does, how to open a call, what to ask, what to note down, what never to say, and when to fetch a manager. Agent instructions cover exactly the same ground.

What to include every time

Your business

Name the business and say what it does, so the agent can introduce itself and handle basic questions.

You are the reminder assistant for Eastgate Finance, a consumer lender. You call customers a few days before their EMI is due.

The greeting

Give an exact opening line. A clear opening also stops people hanging up because they cannot tell who is calling.

Open with: "Hello {{user_name}}, this is the reminder assistant calling from Eastgate Finance about your upcoming EMI."

Variables such as {{user_name}} are filled in on every call. See Prompt Variables.

What to ask

Say which questions to ask for each reason someone might be on the call.

Ask whether they will be able to pay by the due date. If not, ask which date they can pay and whether it will be the full amount.

What to capture

State the details that must be collected before the call ends, and match them to the agent's captured fields.

Before ending the call, make sure you have the promise to pay date and the amount, and read both back to the customer.

The tone

Be polite, calm and patient. If the customer sounds unsure, slow down and repeat the key information.

When to hand over

If the customer disputes the amount, mentions hardship or asks for a person, hand the call to the collections team straight away.

Tips for instructions that work

  • Be specific. Instead of "be helpful", write "if the caller asks about part payment, explain that the minimum is the interest component and offer a callback from an officer".
  • Write the way you speak. Short sentences. Plain words.
  • Give examples for tricky moments. Show the agent exactly what to say when a caller is upset or confused.
  • Say what not to do. "Never threaten legal action. Never quote a settlement amount."
  • Tell it to wait. "Let the customer finish before you reply." Barge in lets callers cut in; good instructions keep the agent from talking over them.

Common mistakes

  • Too vague: the agent fills the gaps itself, and not always correctly.
  • Contradictions: "always confirm the full address" and "keep calls under a minute" pull in different directions. Pick one, or say which wins.
  • Missing edge cases: an angry caller, a wrong number, a question the agent cannot answer. Write a line for each.
  • Too much at once: start with the core of the call, test it, then add detail based on what you hear.

A full example

A starting point for an EMI reminder agent. Adapt it to your business and your policy.

You are the reminder assistant for Eastgate Finance. You call customers a few days before their EMI is due. Today is {{agent_current_day}}, {{agent_current_date}}.

Open with: "Hello {{user_name}}, this is the reminder assistant from Eastgate Finance, calling about your EMI due on the 5th."

Ask whether they will be able to pay by the due date. If yes, thank them and close the call. If not, ask which date they can pay and whether it will be the full amount. Accept any date up to the 10th. For a later date, say an officer will call them back.

Read the date and amount back and wait for the customer to confirm.

If the customer disputes the amount, mentions hardship or asks for a person, hand the call to the collections team.

Be polite and patient. Never threaten, never quote a settlement figure and never discuss other customers' accounts.

Close by thanking the customer.

Improve it over time

Your first version will not be perfect, and does not need to be.

  1. Listen to recordings and read transcripts of real calls. See Call Recordings.
  2. Find the moments where the agent said something wrong, sounded unnatural or skipped a step.
  3. Change the instructions to cover that situation.
  4. Test again.

Observability also flags off script answers and prompt regressions after a change, so you know quickly if an edit made things worse.

Edit the instructions in the agent's settings in the dashboard at voice.xebit.ai.

Edit the instructions in the agent's settings in the Xebit VoiceKit admin console. How closely an agent follows long instructions also depends on the models your deployment uses, so test after switching models.

Next step

Add the caller's details to your instructions with Prompt Variables.