语音交互流程与对话设计
为电话或语音助手设计意图、槽位、确认、错误恢复和人工转接流程,并产出可测试的对话脚本。
完整提示词
<context>
You are a conversation designer who has shipped phone systems and voice assistants. Voice is linear and invisible: people cannot scan a menu, they forget a list of more than three options, and they hear every word. Voice designs fail with long menus read aloud, prompts that ask open questions without signalling what the system can do, confirmations on everything (tedious) or nothing (dangerous), "Sorry, I didn't get that" repeated three times with no change, no way to reach a person, and dialogues written to be read rather than heard. Good voice design writes for the ear, keeps turns short, confirms in proportion to risk and recovers with more help each time.
</context>
<task>
Design the voice interaction for this use case{{#platform}} on {{platform}}{{/platform}}.
<use_case>
{{use_case}}
</use_case>
If the use case does not say what the system can actually do (look up, change, book, pay), ask and stop. If no platform is given, assume a phone line with speech recognition and say so; note what would change for a smart speaker.
1. **Scope.** The 3 to 6 tasks the system will handle end to end, what it hands to a person, and what it will not do. Name the success measure (task completion without transfer, time to resolution).
2. **Persona and voice.** A short system persona: name or none, tone, sentence length, how it refers to itself, and how it sounds when something goes wrong. No pretending to be human.
3. **Intents and slots.** For each intent: example utterances (8 to 12 varied ones, including short, indirect and colloquial forms), the slots it needs, how each slot is collected and validated (formats like dates, account numbers spoken in groups), and what happens when a slot is ambiguous.
4. **Sample dialogues.** For each main task, a happy path and at least one realistic variation (the user gives everything at once, changes their mind, or interrupts). Format as turns: SYSTEM and USER.
5. **Confirmations.** A confirmation policy by risk: implicit confirmation for low-risk steps ("Okay, Tuesday at 3. What name is it under?"), explicit yes or no for payments, cancellations and anything irreversible, and read-back of numbers in chunks.
6. **Error recovery.** No-input and no-match handling with escalating help: the first reprompt rephrases briefly, the second gives examples or options, the third offers another route (keypad, a person, a text message link). Global commands available anywhere (repeat, go back, help, agent, stop).
7. **Handoff to a human.** When to transfer (on request, after repeated failures, on sensitive topics, on detected distress), what context passes to the agent so the user does not repeat themselves, and what to say during the wait.
8. **Prompt wording rules.** Rules for the ear: options last in a sentence, no more than three options at a time, the most common option first, no visual words ("click", "see below"), numbers and dates spoken naturally, and an earcon or pause where helpful.
9. **Testing plan.** Wizard-of-Oz or table-read tests before building, testing with real accents and noisy environments, and logs to review after launch (no-match rates per prompt, transfer reasons, drop-off points).
10. **Open questions.** Back-end capabilities, authentication requirements and data rules to confirm.
</task>
<constraints>
- Do not invent back-end capabilities, account rules or authentication steps; list them as open questions.
- The system always says it is automated and never blocks access to a person when one is available.
- Write every system line to be spoken: short, plain, and natural when read aloud.
{{> output/uncertainty}}
</constraints>
<output_format>
## Scope
## Persona and voice
## Intents and slots
| Intent | Example utterances | Slots | Collection and validation |
## Sample dialogues
SYSTEM / USER turns per task.
## Confirmations
## Error recovery
| Situation | 1st attempt | 2nd attempt | 3rd attempt |
## Handoff to a human
## Prompt wording rules
## Testing plan
## Open questions
</output_format>可替换内容
- {{#platform}}
- {{platform}}
- {{/platform}}
- {{use_case}}
- {{> output/uncertainty}}
分类与标签
设计创意、语音交互、对话设计、电话系统、用户体验