AI voice receptionist prompt: a simple starting template

The best AI voice receptionist prompt is not the longest one. It tells the agent who it is, what a successful call looks like, what information it may use, and when a person needs to take over.

Prompt wording is only one layer of a voice receptionist. ElevenLabs describes a system prompt as a blueprint for an agent's behavior, while turn-taking and voice settings live elsewhere. OpenAI's Realtime API exposes an instructions field to guide responses and notes that guidance is not guaranteed. Read the ElevenLabs prompting guide for the platform distinction.

Copy this starting prompt

Replace the bracketed details with information from your business. Keep the instructions short enough for your team to review and update.

1. Role: You are the phone receptionist for [business name]. Your job is to help callers reach the right next step.
2. Goal: Answer common questions from the approved business information. Capture the details needed for [booking, callback, or lead handoff].
3. Voice: Speak in short, natural sentences. Ask one useful question at a time. Do not sound rushed or overly cheerful.
4. Rules: Use only the approved information. Do not invent prices, availability, policies, or promises. Say when you do not know.
5. Flow: Greet the caller. Learn why they called. Answer or ask for the missing detail. Confirm the next step before ending the call.
6. Handoff: Transfer or request a callback when [handoff conditions]. Give the team a short summary so the caller does not have to start over.

This is a framework, not a finished production prompt. Your business facts and handoff rules are what make it useful.

How to fill in the prompt

Start with one job

Choose the first job the receptionist should do well. It might answer service questions, book an appointment, or capture a qualified callback. Do not make the first version responsible for every department.

If you are still deciding what belongs in the role, read our guide to what an AI voice receptionist does. It explains the basic jobs before you write the instructions.

Use approved business facts

Add your hours, service area, core services, booking rules, and escalation details. Keep the source current. A polished prompt cannot fix an outdated answer.

Our guide to setting up an AI voice receptionist covers the phone connection and the business rules that sit behind the prompt.

Make the questions earn their place

Ask for information because the team will use it. A home-service business may need a location and the type of problem. An appointment-based business may need the service and a preferred time.

Use our guide to what an AI receptionist should ask before adding a long intake sequence.

Define the handoff in plain language

State what should trigger a transfer, a callback, or an urgent response. Include what the receptionist should tell the caller while the handoff happens.

The definition of a qualified lead matters here. Our guide to qualified leads for small businesses can help you decide which details belong in the summary.

What to leave out

Do not put every internal document in one giant prompt. Give the receptionist the facts it needs for the first call. Keep detailed policies in an approved knowledge source when the platform supports one.

Avoid a long personality description. “Warm and professional” is enough to start. More useful guidance explains what the agent should do when a caller is vague, frustrated, urgent, or asking for something outside the business.

Do not tell the receptionist to promise a result it cannot control. It should not guarantee a booking, quote, response time, refund, or approval unless your system actually confirms that outcome.

Test the prompt with real call situations

Read the prompt aloud and run a few short scenarios. Try a normal request first. Then change the wording, interrupt the agent, or ask for something outside the approved information.

Check whether the receptionist asks a useful question, gives an approved answer, and explains the next step. If it fails, change one instruction at a time.

Our guide to AI receptionist testing gives you a simple test, fix, and retest loop before real callers depend on it.

The prompt is not the whole system

A voice receptionist also depends on the phone connection, the knowledge source, the booking or CRM integration, and the handoff path. Prompt changes cannot repair a disconnected calendar or an outdated service list.

Cost follows the same logic. Read our guide to AI voice receptionist pricing after you know which call types, minutes, and integrations you need.

Where Leadspa fits

Leadspa can help you turn your business rules into a clear receptionist prompt and test it against the calls your team wants to improve. Start with one workflow. Keep the first version easy to review. Expand only after it handles the basics reliably.