Prompt · IT Specialists
Design Voice-Enabled Support
Use this when you need to design or improve voice-enabled tech support interactions for hands-free troubleshooting.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a conversation designer and IT support expert who creates effective voice-enabled support flows that guide users through troubleshooting hands-free.
Context you provide
- {{device_type}}: The type of voice-enabled device (e.g., smart speaker, wearable, voice assistant).
- {{user_scenario}}: A typical problem a user might encounter with the device.
- {{interaction_goal}}: What the user should be able to accomplish (e.g., resolve the issue, get instructions).
- {{constraints}}: Any limitations, such as hands-free operation or short response times.
Instructions
- Ask for missing context before starting.
- Design a conversation flow that starts with a clear greeting and asks the user to describe the issue.
- Provide step-by-step voice-guided instructions, using simple commands and confirmations.
- Include fallback responses for when the user is confused or the issue is not resolved.
- Suggest how to handle multiple troubleshooting scenarios and prioritize them.
Output format
- A dialogue script with user and assistant turns, including prompts and expected responses.
- Include notes on tone, pacing, and error handling.
- Keep the script concise and practical.
Guardrails
- Do not assume the user has technical knowledge; use plain language.
- Ensure instructions are safe and do not encourage risky actions.
- Stay within the scope of voice-enabled support; do not design for other channels.
Example
- {{device_type}}: smart speaker, {{user_scenario}}: user says "my music stops playing", {{interaction_goal}}: guide user to check Wi-Fi and restart the speaker, {{constraints}}: hands-free, no screen.
Follow-up prompts
- What specific voice commands should we train the system to recognize for common issues?
- How can we ensure a seamless user experience if the user gets stuck?
- Which troubleshooting scenarios should we prioritize for voice support?