@rin-cooperaudio-voice-risk-governance-reviewएकल टेक्स्टसार्वजनिक14 जून 2026 को अपडेट किया गया

Audio Voice prompt that reviews a workflow for operational, privacy, and safety risk and returns risk register, severity ranking, controls, and verification checklist.

AI Workflow Audio Conversation Support Voice

46Star0Fork115कॉपी

Prompt

पूर्वावलोकन

Claude में खोलें

# Role
You are a voice product designer who turns conversational moments into usable, testable experiences. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Review a workflow for operational, privacy, and safety risk for AI-assisted voice agents, realtime audio UX, script writing, and conversation QA.

# Inputs
- Project context: a realtime voice support agent for onboarding new SaaS customers
- Target audience: voice UX teams, support ops, media producers, accessibility teams
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: call analytics, voice model, conversation simulator, QA rubric
- Constraints: low-latency phrasing; clear repair paths; accessible language; explicit handoff
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- call transcripts
- voice personas
- fallback logs
- latency metrics

# Known risks to control
- uncanny tone
- long turns
- unsafe escalation
- misheard user intent

# Method
1. Trace data and permissions
2. Rank risk by likelihood and impact
3. Map every high risk to a concrete control
4. Identify who must approve residual risk

# Required output sections
1. System boundary
2. Data sensitivity
3. Risk register
4. Controls
5. Residual risk
6. Verification checklist

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

आउटपुट

1 आउटपुट

Example Output: Audio Voice Risk Governance Review

Inputs used

Project context: a realtime voice support agent for onboarding new SaaS customers
Target audience: voice UX teams, support ops, media producers, accessibility teams
Success metric: activation, quality, and risk reduction
Available tools and data: call analytics, voice model, conversation simulator, QA rubric
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

risk register, severity ranking, controls, and verification checklist

System boundary

Use call transcripts as evidence, apply the constraint "low-latency phrasing", and explicitly note how the plan reduces uncanny tone. The output should be ready for a practitioner to act on without a follow-up explanation.

Data sensitivity

Treat long turns as a launch blocker until there is a control that can be verified. The minimum control is: clear repair paths, plus reviewer sign-off for ambiguous outputs.

Risk register

Treat unsafe escalation as a launch blocker until there is a control that can be verified. The minimum control is: accessible language, plus reviewer sign-off for ambiguous outputs.

Controls

Treat misheard user intent as a launch blocker until there is a control that can be verified. The minimum control is: explicit handoff, plus reviewer sign-off for ambiguous outputs.

Residual risk

Treat uncanny tone as a launch blocker until there is a control that can be verified. The minimum control is: low-latency phrasing, plus reviewer sign-off for ambiguous outputs.

Verification checklist

Use voice personas as evidence, apply the constraint "clear repair paths", and explicitly note how the plan reduces long turns. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on call transcripts and voice personas. Treat uncanny tone as the primary launch blocker. The first milestone should prove that the workflow produces a usable conversation script, fallback matrix, and voice QA checklist with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to AI-assisted voice agents, realtime audio UX, script writing, and conversation QA.
It includes the required sections: System boundary, Data sensitivity, Risk register, Controls, Residual risk, Verification checklist.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: uncanny tone.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

Audio Voice: Risk Governance Review

Use this prompt when you need risk register, severity ranking, controls, and verification checklist for AI-assisted voice agents, realtime audio UX, script writing, and conversation QA.

Best for

voice UX teams, support ops, media producers, accessibility teams
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.