# Turn a Telecaller Script into an AI Agent Prompt

> How to turn a telecaller script into an AI voice agent prompt: role, style, steps, branches, rules and closing, with a before-and-after example.

Source: https://edesy.in/blog/telecaller-script-to-ai-voice-agent-prompt-2026

**A telecaller script is a good starting point for an AI voice agent, but it isn't a prompt.** A human
telecaller fills gaps with judgement; an AI agent needs its role, speaking style, steps, branches for
common replies, hard rules and an explicit closing written down. In real deployments, the jump from
"original" to "improved" prompt was mostly adding what the telecaller knew implicitly: how to sound, what
never to say, and when the call is really over. Here's how to convert a script, with a before-and-after.

> **Paste your script and test it:** [Try Edesy free](https://voice-agent.edesy.in/?utm_source=edesy.in&utm_medium=blog&utm_campaign=telecaller-script-to-ai-voice-agent-prompt-2026) — Rs 50 free credit, no demo needed.

## Before: a typical telecaller script

> Greet the customer. Introduce company. Ask if they are interested in our products. If yes, ask product,
> quantity and location. Take their details. Thank them.

A person can run with this. An AI agent will improvise the greeting, guess prices, ask for details it
already has, and hang up on the first "thank you".

## After: the same script as an AI prompt

**1. Role and objective**
> You are a friendly female voice from {{company}}, calling people who enquired on our website. Your goal
> is to find out whether they want to buy, and capture product, quantity and location.

**2. Speaking style**
> Speak natural Hinglish, one short line per turn, then stop and listen. Rotate acknowledgements
> ("achha", "theek hai", "samajh gayi"). Never repeat the greeting.

**3. Pronunciation**
> Say numbers the Indian way (ek lakh). Spell out these abbreviations letter by letter: M-O-Q, G-S-T.

**4. Steps**
> Step 1: confirm you're speaking to {{name}}. Step 2: say why you're calling in one sentence.
> Step 3: ask if they want to buy, or something else. Step 4 (buyer): ask product, then quantity, then
> location, one at a time.

**5. Branches**
> If busy or driving: offer a callback time. If wrong person: ask who handles purchases. If job seeker:
> take role and experience, say HR will call.

**6. Hard rules**
> Never quote prices, minimum quantities or delivery dates; say the sales team will share them on
> WhatsApp. Never read placeholders or brackets aloud. Never ask for something you already know.

**7. Closing**
> Only end when all questions are done, you've asked "anything else?", they said no, and you've said
> goodbye. "Thank you" mid-call is not goodbye.

## Why each section exists

| Section | Problem it prevents |
|---|---|
| Role and objective | Agent drifting off-task |
| Speaking style | Long monologues, robotic repetition |
| Pronunciation | "One hundred thousand", mangled acronyms ([guide](https://edesy.in/blog/ai-voice-agent-pronunciation-numbers-acronyms-india-2026)) |
| Steps | Skipped or reordered questions |
| Branches | Awkward handling of busy, wrong person, off-topic |
| Hard rules | Invented prices, read-out placeholders ([names guide](https://edesy.in/blog/ai-voice-agent-caller-name-capture-india-2026)) |
| Closing | Early hang-ups ([guide](https://edesy.in/blog/why-ai-voice-agent-hangs-up-too-early-fix-2026)) |

For fixed-step calls, consider building the steps as a flow instead of prose; see
[AI Flow vs prompt agent](https://edesy.in/blog/ai-flow-vs-prompt-voice-agent-when-to-use-2026).

## Improve it after launch

1. Listen to 20-30 calls.
2. Write down every wrong behaviour.
3. Add **one rule per problem**, in plain language.
4. Retest; repeat daily in the first week ([first-week routine](https://edesy.in/blog/first-week-new-ai-voice-agent-monitoring-2026)).

The full set of rules we apply everywhere: [10 prompt rules from real deployments](https://edesy.in/blog/ai-voice-agent-prompt-rules-real-deployments-2026).

## Try it

[Create a free account](https://voice-agent.edesy.in/?utm_source=edesy.in&utm_medium=blog&utm_campaign=telecaller-script-to-ai-voice-agent-prompt-2026),
paste your script into the seven sections above, and call yourself as a difficult customer. Want a
review of your prompt? [Talk to us](https://edesy.in/contact).

## Frequently Asked Questions

### Can I use my telecaller script as the AI agent's prompt?

It's a good starting point, but not as-is. Telecaller scripts assume a person who improvises; an AI agent needs its role, speaking style, steps, branches for common replies, rules for what never to say, and an explicit closing added.

### What sections should an AI voice agent prompt have?

Role and objective, speaking style, pronunciation rules, step-by-step flow, branches for common replies, hard rules (never quote prices, never read placeholders), handling busy or wrong-person callers, and the exact closing.

### How long should the prompt be?

As long as needed to cover real situations, but every line should be something the agent actually needs. Long rambling prompts can slow responses and confuse the agent.

### What usually goes wrong with a first prompt?

Calls end too early on 'thank you', the agent repeats greetings, asks for details it already has, reads placeholders or long lists aloud, invents prices, and mispronounces numbers and acronyms.

### How do I improve the prompt after launch?

Listen to 20-30 calls, list every wrong behaviour, add one rule per problem, and test again. Most prompts reach a stable version within the first week.