返回提示词目录第 1390 页

编写语音交互代理系统提示词

围绕通话目标生成系统提示词与测试场景,覆盖听辨纠错、工具调用和人工转接流程。

完整提示词

<context>
A voice agent fails in ways a chat assistant does not. Its words are turned into speech, so Markdown, lists, links and long answers become noise; the caller cannot scroll back; speech recognition mishears names, numbers and email addresses; callers interrupt, go silent or talk over the agent; tool calls create dead air; and there is no visual way to show options. A good voice prompt keeps turns short, asks one thing at a time, reads back every detail that matters, recovers from errors in a fixed number of tries, says what it is doing while it waits, never makes up policy, and hands off to a person cleanly, with a summary so the caller does not repeat themselves.

Channel: {{channel}}
Languages: {{languages}}

<purpose>
{{purpose}}
</purpose>

<handoff_rules>
{{handoff_rules}}
</handoff_rules>
{{#tools}}
<tools>
{{tools}}
</tools>
{{/tools}}
</context>

<task>
1. If the purpose or handoff rules are too vague to write safe behaviour (for example no scope, or no answer to "what happens when no human is available"), ask up to three questions and stop.
2. List the assumptions you are making and the facts you still need.
3. Write the system prompt with these parts:
   - Identity and scope: who the agent is, what it handles, what it does not, and that it says it is an automated assistant at the start of the conversation and whenever asked.
   - Speaking style: plain spoken sentences, no visual formatting or symbols, one question per turn, short turns, numbers, dates, times and prices said the way people say them, options offered two or three at a time.
   - Conversation flow: greeting, finding the caller's goal, collecting the details each task needs, reading key details back for a yes before acting, and a clear close that says what happens next.
   - Recognition problems: when unsure what was said, ask again in a different way; for names and emails, ask for spelling letter by letter; after two failed tries on the same item, offer another route or a handoff. Rules for silence (prompt once, then once more, then end politely or hand off) and for interruptions (stop and listen).
   - Tools: when to call each one, what to say while waiting, never reading raw tool output aloud, and what to say when a tool fails. If no tools are given, the agent can only answer and hand off.
   - Handoff: every trigger from the handoff rules, plus a caller asking for a person, repeated failure, distress or anger, emergencies and anything out of scope; what to say to the caller; and the short summary passed to the human (goal, details collected, what was tried).
   - Safety and privacy: emergencies go straight to the emergency number or the handoff the rules give; verify identity only as the rules describe; never read back full card numbers, passwords or one-time codes; never state prices, policies, medical or legal advice beyond the facts given in the purpose.
   - Other languages: what to do when the caller speaks a language not listed.
4. List every placeholder left in the prompt for facts the purpose did not give.
5. Write test calls that exercise the hard parts: a happy path, a misheard name or number, a caller who goes silent, an interruption, a tool failure, a request for a human, an out-of-scope question, an upset caller, and an attempt to make the agent ignore its instructions.
</task>

<constraints>
- Never invent business facts, prices, policies or opening hours; use clearly marked placeholders such as [OPENING HOURS] and list them.
- Do not use vendor-specific speech markup unless the user names the platform; describe pacing in plain instructions.
- Keep the prompt model-agnostic and as short as the behaviour allows; put the most important rules first.
- Note in one line that rules on announcing automated calls, recording and consent vary by country and must be checked locally.
</constraints>

<output_format>
## Assumptions and open questions
Bullets.
## System prompt
One fenced block, ready to paste, organised with short headings.
## Placeholders to fill
Bullets: placeholder and what it needs.
## Test calls
Table: Scenario | What the caller says | What a pass sounds like.
</output_format>

可替换内容

  • {{channel}}
  • {{languages}}
  • {{purpose}}
  • {{handoff_rules}}
  • {{#tools}}
  • {{tools}}
  • {{/tools}}
  • [OPENING HOURS]

分类与标签

编程开发、语音代理开发、系统提示词、人工转接、通话测试

前往 AI 图片创作