Conversational ERP CRM Layer
Purpose
Design how Dataverse-based ERP and CRM processes can be operated through natural language instead of classic forms, ribbons, menus, and table navigation.
Use this skill for:
- Dynamics or Dataverse command experiences
- CRM pipeline actions by conversation
- service and operations workflows by chat
- process-first app modernization
- natural-language alternatives to form-heavy workflows
V1 Boundary
This skill provides design and implementation guidance only. It does not control Dynamics, Power Apps, or Dataverse at runtime.
Workflow
- Identify the business process that should become conversational.
- Replace screen navigation with user intents, commands, confirmations, and generated task views.
- Map each conversational action to Dataverse records, business process flows, cloud flows, approvals, and reports.
- Define how the user sees state: summary, next action, blockers, approvals, and audit evidence.
- Preserve enterprise controls: permissions, approvals, DLP, logging, and rollback paths.
Output Format
Return:
Conversational process: process name, users, and target outcomes.Intent catalog: user utterances and supported commands.Dataverse mapping: tables, processes, flows, and reports involved.Interaction model: questions, confirmations, generated views, and status responses.Enterprise controls: security, audit, approvals, and failure handling.
1---2name: conversational-erp-crm-layer3description: Use when designing a dialog-first ERP or CRM operating layer over Dataverse, Dynamics, or Power Platform apps. Produces architecture and interaction guidance only; it does not replace or control live applications.4---56# Conversational ERP CRM Layer78## Purpose9Design how Dataverse-based ERP and CRM processes can be operated through natural language instead of classic forms, ribbons, menus, and table navigation.1011Use this skill for:12- Dynamics or Dataverse command experiences13- CRM pipeline actions by conversation14- service and operations workflows by chat15- process-first app modernization16- natural-language alternatives to form-heavy workflows1718## V1 Boundary19This skill provides design and implementation guidance only. It does not control Dynamics, Power Apps, or Dataverse at runtime.2021## Workflow221. Identify the business process that should become conversational.232. Replace screen navigation with user intents, commands, confirmations, and generated task views.243. Map each conversational action to Dataverse records, business process flows, cloud flows, approvals, and reports.254. Define how the user sees state: summary, next action, blockers, approvals, and audit evidence.265. Preserve enterprise controls: permissions, approvals, DLP, logging, and rollback paths.2728## Output Format29Return:30- `Conversational process`: process name, users, and target outcomes.31- `Intent catalog`: user utterances and supported commands.32- `Dataverse mapping`: tables, processes, flows, and reports involved.33- `Interaction model`: questions, confirmations, generated views, and status responses.34- `Enterprise controls`: security, audit, approvals, and failure handling.35
rweisssieker-xp