Voice-First Enterprise Operations
Purpose
Design Dataverse actions that can be safely started, reviewed, confirmed, and explained through voice.
Use this skill for:
- voice-created records
- spoken workflow starts
- voice report retrieval
- voice approvals
- Teams call action capture
- mobile and headset-first enterprise workflows
V1 Boundary
This skill creates voice interaction designs only. It does not capture audio, transcribe speech, call Teams, or execute Dataverse operations.
Workflow
- Define the voice channel, user context, environmental constraints, and supported commands.
- Design speech-friendly confirmations for record creation, updates, approvals, and bulk operations.
- Require read-back for critical fields, high-risk changes, amounts, dates, names, and selected records.
- Define fallback to visual UI when ambiguity, risk, or data density is too high for voice.
- Define audit evidence: transcript, confirmation phrase, timestamp, user identity, and action summary.
Output Format
Return:
Voice scenario: user, channel, and business task.Voice command model: supported utterances and slots.Confirmation flow: read-back, clarification, and approval prompts.Fallback rules: when to switch to visual review.Audit evidence: what must be logged for compliance.
1---2name: voice-first-enterprise-operations3description: Use when designing voice-first Dataverse and Power Platform operations for mobile, Teams calls, headsets, or Copilot-style interfaces. Produces interaction and safety guidance only.4---56# Voice-First Enterprise Operations78## Purpose9Design Dataverse actions that can be safely started, reviewed, confirmed, and explained through voice.1011Use this skill for:12- voice-created records13- spoken workflow starts14- voice report retrieval15- voice approvals16- Teams call action capture17- mobile and headset-first enterprise workflows1819## V1 Boundary20This skill creates voice interaction designs only. It does not capture audio, transcribe speech, call Teams, or execute Dataverse operations.2122## Workflow231. Define the voice channel, user context, environmental constraints, and supported commands.242. Design speech-friendly confirmations for record creation, updates, approvals, and bulk operations.253. Require read-back for critical fields, high-risk changes, amounts, dates, names, and selected records.264. Define fallback to visual UI when ambiguity, risk, or data density is too high for voice.275. Define audit evidence: transcript, confirmation phrase, timestamp, user identity, and action summary.2829## Output Format30Return:31- `Voice scenario`: user, channel, and business task.32- `Voice command model`: supported utterances and slots.33- `Confirmation flow`: read-back, clarification, and approval prompts.34- `Fallback rules`: when to switch to visual review.35- `Audit evidence`: what must be logged for compliance.36
rweisssieker-xp