Front Desk ROI 作者分享免費 AI Voice Agent Prompt Builder 的架構設計

I Built a Free Generator That Writes AI Receptionist Prompts — Here's the Architecture It Uses

Most voice-agent demos fail in the same place, and it isn't the model, the latency, or the voice. It's the system prompt — usually three vague sentences pasted into a dashboard ("You are a helpful receptionist, answer questions and book appointments") and then vibes.

I kept seeing this while building Front Desk ROI, a set of free tools for local service businesses — plumbers, HVAC shops, electricians — businesses that live or die by the phone. In CallRail's 2025 survey of 1,000 US consumers, 82% said they will call a competitor if a business doesn't answer. But an AI receptionist with a sloppy prompt is barely better than voicemail: it books appointments with no address, invents prices, and has no idea what to do with an angry caller at 2am.

So I built a small generator that turns a short form — business name, trade, services, hours, tone, facts, escalation rules, booking method — into a structured, copy-paste system prompt for platforms like Retell, Vapi, or GoHighLevel's voice AI. It's free and runs entirely in the browser. This post is about the prompt architecture it uses — the useful part, whether you use the generator or write yours by hand.

The core idea: a prompt is a job description

A receptionist prompt works best when you stop thinking "instructions for an AI" and start thinking "job description for a very literal-minded employee with perfect memory and zero common sense." A human receptionist gets a role, a greeting script, a task list, a fact sheet, escalation rules, and a way to end calls. The generated prompt has the same bones — eight short sections, in ALL-CAPS headers, in the order a call actually happens:

1. ROLE — who the agent is
2. GREETING — the exact first sentence
3. YOUR TASKS — numbered, in call order
4. SERVICES — what the business does
5. HOURS — when the business is open, and what changes outside those hours
6. KNOWLEDGE — the closed list of facts the agent may state
7. ESCALATION — when a human takes over
8. CLOSING — how every call ends

Here's an excerpt of a generated prompt for a fictional plumbing company:

ROLE
You are the AI receptionist for Rapid Flow Plumbing, a plumbing company.
Your tone is friendly and professional. You answer every call, 24/7.
If asked, politely confirm you are an AI assistant and that a human can
call back on request.

GREETING
Answer with: "Thanks for calling Rapid Flow Plumbing, how can I help you today?"

YOUR TASKS
1. Identify what the caller needs.
2. Book, reschedule or cancel appointments: Offer the next two available
   slots from the connected calendar.
3. Answer questions using only the KNOWLEDGE below. If you do not know,
   say so and offer a callback — never guess a price or a policy.
4. Take a complete message: name, phone number, address if relevant,
   and a one-line summary.

KNOWLEDGE (only facts you may state)
- We serve the Austin metro area
- Call-out fee is $49, waived with repair
- All work is guaranteed for 12 months

ESCALATION — transfer or promise an urgent human callback when:
The caller is distressed or angry, describes an emergency such as
flooding or a burst pipe, or asks for a manager.

CLOSING
Summarise what will happen next and by when, confirm the caller's number,
thank them for calling Rapid Flow Plumbing, and end the call politely.

Two sections were trimmed from that excerpt (SERVICES and HOURS), but the shape is the whole point. Now the reasoning per section, because the defaults are where the design decisions live.

Identity, greeting, and the disclosure line

ROLE does three jobs in four sentences: names the business, sets the tone (four presets — friendly and professional, warm and reassuring, brisk and efficient, formal), and states coverage: "You answer every call, 24/7." Coverage is the point of the product — ServiceTitan's data says 18% of home-service calls go unanswered on weekdays and 41% on weekends, exactly when the humans aren't there.

The last ROLE sentence is the one I'd defend hardest: "If asked, politely confirm you are an AI assistant and that a human can call back on request." Disclosure rules vary by jurisdiction and some platforms require it outright, but even where they don't, an agent that denies being an AI when asked directly will eventually do it on a recorded call to exactly the wrong person. The line also defuses the question — callers who ask usually just want to know a human is reachable, and the prompt promises them one.

GREETING is a literal string, not a style suggestion. The first five seconds of a call set the caller's patience budget for everything that follows, and "say something friendly" produces a different opener on every call.

Tasks and data capture: where agents quietly lose jobs

YOUR TASKS is numbered because call flow is sequential: identify the need, handle booking, answer questions, or capture a message. The booking line is user-supplied (e.g. "offer the next two available slots from the connected calendar"), because booking is half prompt, half platform — the prompt tells the agent how to offer booking, but only a calendar integration lets it actually book.

Task 4 is the least glamorous and the most important: a complete message is defined as name, phone number, address if relevant, and a one-line summary. Underspecified "take a message" instructions are how you end up with a transcript that says "someone called about a leak" and no way to call them back. If you steal one thing from this architecture, steal explicit completeness criteria for every data-capture task.

Knowledge: a closed world, with an escape hatch

KNOWLEDGE is headed "(only facts you may state)" and the header is load-bearing. The user's facts go in as a verbatim bullet list — prices, service areas, policies — and task 3 supplies the other half of the contract: if you do not know, say so and offer a callback — never guess a price or a policy.

Language models would rather produce a plausible answer than admit a gap unless explicitly instructed otherwise, and a voice agent has no "I'm not sure" body language. An invented call-out fee becomes the real price in the customer's mind, whatever your invoice says later. The say-so-and-callback rule converts hallucination risk into a slightly-less-convenient phone message — the right trade for a business phone line.

HOURS gets a similar treatment. The section states the hours, then appends a fixed behaviour for outside them: explain when the team returns, and still take a full message. Without that sentence, agents improvise after-hours behaviour — usually some version of "we're closed, goodbye," which is a voicemail with extra steps.

Escalation and closing: the two sections everyone skips

ESCALATION is phrased as "transfer or promise an urgent human callback when:" — the "or" matters, because many small setups have no live transfer target at 2am. The conditions come from the user (angry callers, flooding emergencies, anyone asking for a manager); if they leave the field blank, the generator inserts a sane default — distressed or angry caller, an emergency, a request outside the agent's knowledge — rather than shipping an empty section. That rule applies to every field: a prompt with a blank KNOWLEDGE heading is worse than one with an honest placeholder, because the model will fill the vacuum itself.

CLOSING is a fixed script: summarise what happens next and by when, confirm the caller's number, thank them by business name. The "by when" and the number confirmation kill the two most common post-call failures — a customer who isn't sure anything was booked, and a callback number that was misheard and never checked.

Honest limitations

This is a template generator, not an agent framework, and I want to be precise about what it can't do:

• No runtime behaviour. The prompt doesn't give your agent tools, state, or memory. Booking, transfers, and SMS follow-ups are platform features; the prompt only governs what the agent says about them.
• The knowledge section goes stale. Prices and hours drift, and the prompt will keep stating last year's call-out fee with total confidence. It needs the same maintenance as a staff handbook.
• Four tone presets is coarse. Real brands need finer control; the presets are starting points you'd edit.
• It won't rescue a bad test loop. The generator produces a first draft. The agents that work are the ones whose owners made test calls — a routine booking, a price question the agent must not invent an answer to, an out-of-hours emergency, and one weird request outside the services list — and fixed what failed by editing the relevant section.

That last point is the main thing building this taught me: prompt quality is a loop, not a draft. Almost every failure traced back to one missing or vague section, and the fix was almost never "add more instructions" — it was "make this section's rule explicit." Vague prompts produce vague agents; specific sections produce specific behaviour.

Try it

The generator is free and needs no signup: AI Voice Agent Prompt Builder. Generate one for your business (or your test business), paste it into Retell/Vapi/your platform of choice, and make the four test calls.

And if you're pricing the setup, the companion tool models what the calls will cost across the main vendors: AI Receptionist Cost Calculator.

If you've built receptionist or phone-agent prompts, I'd genuinely like to hear which sections you ended up adding — my bet is everyone converges on escalation and closing the hard way.