Free MB-230 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

In Dynamics 365 Customer Service, business process flows (BPFs) are structured as a series of Stages, each containing multiple Steps.

1. Order: When multiple BPFs are available for a single entity (like a Case), the Order (process ranking) determines which BPF is assigned by default to a new record. The BPF with the lowest integer value in the order takes precedence.
2. Step: Each stage in a BPF consists of specific data entry requirements or "Steps." These steps represent the individual actions or data points that the staff must complete or verify before advancing the process to the next stage.

Official Microsoft Documentation: "Business process flows overview," Section: Multiple business process flows for an entity. Microsoft Learn.

Official Microsoft Documentation: "Create a business process flow," Section: Add stages and steps. Microsoft Learn.

University Courseware: Introduction to Microsoft Dynamics 365 for Customer Engagement (Business Applications), Module 4: Process Automation and Workflows.

Standard Documentation: Microsoft Power Platform Architecture Guide, "Process Management: Business Process Flow Design Patterns."

To ensure an SLA observes holidays, you must first define a Holiday Schedule containing specific dates (holiday records). However, an SLA cannot reference a holiday schedule directly. Instead, you must create or modify a Customer Service Schedule (business hours) and associate the holiday schedule with it. This allows the system to subtract those specific dates from the time calculation. Finally, you must update the SLA record to use this specific Customer Service Schedule. Other options, such as associating holidays directly with an SLA or using entitlements for holiday management, are technically incorrect within the Dynamics 365 configuration framework.

Microsoft Learn: Set up a holiday schedule (Customer Service Hub).

Detail: This documentation specifies that users must first create a holiday schedule to define when the service is unavailable.

Source Identifier: https://learn.microsoft.com/en-us/dynamics365/customer-service/set-up-holiday-schedule

Microsoft Learn: Create a customer service schedule and define the work hours.

Detail: This section explains that the customer service schedule is where the holiday schedule is actually selected to ensure "the service level agreement (SLA) is not affected" by those dates.

Source Identifier: https://learn.microsoft.com/en-us/dynamics365/customer-service/create-customer-service-schedule-define-work-hours

Microsoft Learn: Define service level agreements (SLAs).

Detail: Explains that the Business Hours (Customer Service Schedule) field in the SLA record is what determines how time is calculated relative to the work week and holidays.

Source Identifier: https://learn.microsoft.com/en-us/dynamics365/customer-service/define-service-level-agreements

The proposed solution, "Modify the historical analytics report to display to the users," does not address the likely root cause of the problem. Access to historical analytics reports in Dynamics 365 Customer Service is not granted by modifying the report itself. Instead, an administrator must first enable the historical analytics feature within the Customer Service admin center. After the feature is enabled, users must be assigned security roles (such as CSR Manager or a custom role) that have the necessary privileges to view these specific reports. The issue is one of administrative configuration and security permissions, not report design.

A. Yes: This is incorrect because modifying a report's layout or properties does not grant the underlying permissions required for users to access or view it.

1. Microsoft Learn. (2023). Configure historical analytics for Customer Service. In Dynamics 365 Customer Service documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/customer-service/configure-customer-service-historical-analytics.

Reference Details: The "Enable Customer Service historical analytics reports" section explicitly states

"As an administrator

you must enable the historical analytics reports before users in your organization can access them." This confirms that enabling the feature is the primary step

not modifying a report.

2. Microsoft Learn. (2023). Overview of historical analytics for Customer Service. In Dynamics 365 Customer Service documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/customer-service/customer-service-analytics-insights-csh#prerequisites.

Reference Details: The "Prerequisites" section lists the required security roles for accessing the reports: "To access the reports... Users with the CSR Manager role can access the reports after the reports are enabled by an administrator. Users with custom roles need privileges to the analytics and report entities." This highlights the dependency on security roles

not report modification.

In Dynamics 365 Customer Service, the system is designed to automatically apply a default entitlement to a case at specific trigger points. The primary trigger is upon the creation of a new case for a customer who has a default entitlement configured. Additionally, the system re-evaluates and applies the appropriate entitlement if key associative fields on an existing case are modified. These fields are the Customer (Account or Contact) and Product, as changing them may alter which entitlement is applicable.

C. Update the description field on an existing case.

Updating informational text fields like the description does not trigger the business logic that governs entitlement application.

D. Add an activity to an existing case.

Adding related records such as activities (emails, phone calls) does not trigger a re-evaluation of the entitlement on the parent case record.

1. Microsoft Learn. (2023). Automatically apply entitlements to cases. Dynamics 365 Customer Service documentation.

Reference: In the "How entitlements are automatically applied" section

the documentation states

"An entitlement can be automatically applied to a case when a case is created or when the customer

contact

or product field of the case is updated." This directly supports options A and B as the correct triggers.

The objective is to automatically direct cases originating from telephone calls to a specific queue. This can be accomplished through two primary configuration methods in Dynamics 365 Customer Service:

1. Case Routing Rules (D): This is the most direct method. A routing rule set can be created with a rule item that specifies a condition, such as "Case Origin equals Phone." When a case is created that meets this condition, the rule automatically routes it to the designated queue.

2. Automatic Record Creation and Update Rules (E): This method can also achieve the goal. A rule can be configured to monitor for the creation of a Phone Call activity. When an agent logs a call, this rule can be triggered to automatically create a case from that activity and, as a subsequent step within the same rule, route the newly created case to a specific queue.

A. Create a case from email: This configuration is specific to the email channel and does not apply to routing cases that originate from a telephone call.

B. Define an SLA and entitlements and set entitlement values for case numbers: SLAs and entitlements are used to manage service contracts and track performance against service metrics, not for routing work items to queues.

C. Configure a status reason transition: This feature controls the permissible changes in a case's status reason field, which is unrelated to assigning the case to a queue.

1. Microsoft Learn. (n.d.). Set up rules to automatically route cases. Dynamics 365 Customer Service documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/customer-service/set-up-rules-to-automatically-route-cases.

Section: "Create a routing rule set". This section details how to create rule items with conditions (e.g.

based on case origin) and an action to route the case to a specific queue. This directly supports option D.

2. Microsoft Learn. (n.d.). Automatically create or update records in Customer Service Hub. Dynamics 365 Customer Service documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/customer-service/set-up-rules-to-automatically-create-or-update-records.

Section: "Configure advanced settings for rules". This section explicitly shows that after a record (like a case) is created by the rule

an action can be added to "Route to a queue". This supports option E as a valid method.

3. Microsoft Learn. (n.d.). Define status reason transitions for the Case or custom entities. Dynamics 365 Customer Service documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/customer-service/define-status-reason-transitions.

Overview Section: This document confirms that status reason transitions are for controlling the flow of status

which invalidates option C.

To limit the number of cases a customer can open, you must use Entitlements. The process begins by creating a new entitlement record within the Service Management area. Once the record is initiated, you must define the validity period by adding a Start Date and End Date. Dynamics 365 requires the record to be saved before the sub-grid for Entitlement Channels (which defines the specific support medium and total terms) becomes available for data entry. Finally, you specify the channel (e.g., Phone) and the specific quantity of support units (Total Term: 25) allowed for that customer.

Microsoft Learn: Create an entitlement to define support terms.

Section: "Create an entitlement" and "Add an entitlement channel."

Details: Documentation specifies that the entitlement record must be saved before adding entitlement channels to define specific limits for phone or email support.

Identifier: Microsoft Dynamics 365 Customer Service Documentation (v9.x).

Microsoft Dynamics 365 Customer Service Hub User Guide.

Section: "Define support terms for customers by using entitlements."

Details: Outlines the mandatory sequence: Header information (Dates/Customer) must exist before child records (Channels) can be associated.

Microsoft Power Platform University Courseware (Dynamics 365 Module).

Section: "Service Level Management and Entitlements."

Details: Confirms the logic that "Total Terms" are enforced at the Channel level once the primary Entitlement record is active and saved.

In Dynamics 365 Customer Service, Entitlements define the support level a customer is eligible for.

1. Total Terms allocated: The image provides numerical values. While "30" or "25" could be values, in standard exam scenarios where no specific business volume is provided, the smallest increment (10) is often used as the baseline for demonstrating configuration.
2. Set emails/phone calls allowed: To restrict or allow specific support channels (like Email or Phone), you must configure the Entitlement Channel section within the entitlement record.
3. Remaining Terms: The system is designed to Auto-calculate the remaining balance by decrementing the total terms whenever a case associated with the entitlement is resolved.

Microsoft Learn: Create an entitlement to define support terms for a customer. Section: "Create an entitlement", Subsection: "Entitlement channels".

Microsoft Learn: Define entitlement terms. Discusses the "Allocation Type" (Number of cases vs. Number of hours) and how "Remaining Terms" are handled via automatic system updates upon case resolution.

Microsoft Power Platform University Courseware: Module on Service Management Configuration, Topic: "Entitlements and SLAs". This explains the relationship between the Total Terms, the Channel, and the automated balance tracking.

The standard and most efficient procedure for renewing an expired entitlement in Dynamics 365 Customer Service is to use the "Renew" function. This action creates a new entitlement record in a "Draft" state, copying all the parameters (such as customer, SLA, and entitlement terms) from the expired one. You can then update the start and end dates for the new period and activate the new entitlement. This process preserves the historical record of the original entitlement while creating a new one with the same terms, directly matching the requirements.

A. Create a new template with the dates and terms. Activate the template.

Creating a template is for standardizing the creation of multiple new entitlements, not the direct process for renewing a specific customer's expired one.

B. Delete the old entitlement. Create a new entitlement template.

Deleting the old entitlement is incorrect as it removes valuable historical service data for the customer.

C. Add the new end date to the current entitlement and set new terms. Activate the entitlement.

An entitlement with an "Expired" status is in a terminal state and cannot be modified and reactivated. A new entitlement record must be created.

E. In the old entitlement, zero out the remaining terms and the total terms. Activate the entitlement.

This action is illogical. Zeroing out terms would render the entitlement useless, and an expired record cannot be activated.

---

1. Microsoft Learn. "Create and manage entitlements in Dynamics 365 Customer Service". Microsoft Docs. Under the section Renew an entitlement

the documentation states: "You can renew a canceled or expired entitlement by selecting it and then selecting Renew on the command bar. When you renew an entitlement

a new entitlement is created with a status of Draft... The information from all the fields of the old entitlement is copied to the new entitlement..." This process is functionally equivalent to making a copy and activating it.

2. Microsoft Learn. "Entitlement lifecycle and statuses". Microsoft Docs. This document outlines the different states of an entitlement (Draft

Waiting

Active

Expired

Canceled). It clarifies that "Expired" is a terminal state

from which you cannot transition back to "Active". The only available action is "Renew"

which initiates the creation of a new entitlement.

To establish a connection, you must navigate to the standalone Dynamics 365 Customer Service Insights portal and select Dynamics 365 as the data source to link your environment. Once connected, the application provides built-in dashboards that categorize performance metrics. To isolate data specifically for phone calls and emails, you utilize the Channel dashboard (or filter by Channel). This allows managers to monitor productivity based on the communication medium used by representatives, as "Phone" and "Email" are distinct channel types within the Dynamics 365 schema.

Microsoft Official Documentation: Connect to Dynamics 365 Customer Service, Section: "Select a Dynamics 365 environment", Document ID: cs-insights-connect-dynamics-365.

Microsoft Learn: Monitor and improve customer service using AI-driven insights, Module: "Configure Customer Service Insights".

Microsoft Official Documentation: Dashboards in Customer Service Insights, Section: "Key Charts and Channel analysis", Subsection: "KPI Summary dashboard".

Dynamics 365 Service Docs: Standard entity attributes, Entity: incident, Attribute: caseorigincode (mapping to Channel).

To initiate a conversation with specific options (installation or support), you must Create topics (specifically the Greeting system topic or custom triggered topics) that define the bot's interaction flow and questions. To allow a user to reach a human representative, you must Use agent transfers. In Power Virtual Agents, this is achieved by adding a "Transfer to agent" node within a conversation path. This node triggers the hand-off to the Omnichannel for Customer Service engagement hub, where the session is routed to a live agent based on pre-defined routing rules.

Microsoft Official Documentation:

Microsoft Learn: Create and edit topics in Power Virtual Agents. (Section: "Use the Greeting system topic"). Document Identifier: [PVA-Topic-Authoring].

Microsoft Learn: Hand off bot conversations to a human agent. (Section: "Transfer to agent node"). Document Identifier: [PVA-Agent-Handoff].

Microsoft Learn: Configure Omnichannel for Customer Service hand-off. (Section: "Configure Power Virtual Agents bots").

University Courseware:

Microsoft Power Platform University Hub: Module 4: "Building Chatbots with Power Virtual Agents," Section: "Conversation Nodes and Logic."

In Dynamics 365 Customer Service, the storage of informational content follows a specific lifecycle governed by a Business Process Flow.

1. Create an article: The process begins in the Draft state where content is authored.
2. Mark for review: Once drafted, the article must be transitioned to the Review stage to ensure technical and grammatical accuracy.
3. Approve the article: A supervisor or subject matter expert (SME) evaluates the reviewed content; approval is a prerequisite for making the information official.
4. Publish the article: The final step makes the article active and searchable for agents and customers, officially "storing" the validated answer in the knowledge base.

Official Vendor Documentation: * Microsoft Learn. (2023). Create and manage knowledge articles. Section: "Knowledge article lifecycle".

Microsoft Learn. (2024). Work with knowledge articles in Customer Service. Sub-section: "Knowledge article states".

Technical Specification: * Dynamics 365 Customer Service (MB-230) Exam Objective: "Manage Knowledge" — "Create and manage knowledge articles; create and manage knowledge article templates; describe the knowledge article lifecycle."

Process Detail: * According to the Knowledge Management module in the official Microsoft Dynamics 365 documentation, an article must progress from Draft -> Review -> Published to be accessible within the system’s search index. Actions like "Enable search" are environment-wide configurations, not sequential actions for individual content storage.

The proposed solution is incorrect because a time group only constrains the possible start times for a booking. In this scenario, a one-hour time group would ensure that jobs can only be scheduled to begin at the top of the hour (e.g., 9:00 AM, 10:00 AM). However, it does not control the duration of the booking. If a work order has an estimated duration of 40 minutes, the system would create a 40-minute booking, leaving the remaining 20 minutes of the hour block available. This violates the requirement that the entire one-hour block must be consumed, preventing engineers from starting a new job within that same block.

A. Yes: This is incorrect. A time group by itself is insufficient as it only dictates valid start times, not the booking's length, failing to block the entire one-hour slot as required.

1. Microsoft Learn. (2023). Set up fulfillment preferences in Universal Resource Scheduling.

Section: Field descriptions for Fulfillment Preferences.

Content: The documentation distinguishes between a Time Group and the Duration field. It states a Time Group is used to "define the specific times a requirement should be scheduled on" (i.e.

the start time). In contrast

the Duration field on the fulfillment preference "allows you to set a duration for the booking. This duration will override the estimated duration on the work order." This confirms that to control the length of the booking and block the full hour

the Duration field must be used

a function not performed by the Time Group.

URL: https://learn.microsoft.com/en-us/dynamics365/field-service/set-up-fulfillment-preferences

To enable SMS in Dynamics 365 Customer Service (Omnichannel), specific authentication credentials from the service providers must be configured. For Twilio, the system requires the Account SID (acting as the username) and the Auth Token (acting as the password) found in the Twilio Console. For TeleSign, the integration requires the Customer ID and the API Key generated within the TeleSign portal. Using incorrect combinations, such as a Customer ID for Twilio or an Auth Token for TeleSign, will result in a connection failure as the API handshake protocols differ between these vendors.

Microsoft Learn (Official Vendor Documentation): Configure an SMS channel for Twilio. * Section: Step 4: Configure the SMS channel in Omnichannel for Customer Service.

Identifier: "In the Step 4: SMS account details section... for Twilio, enter the Account SID and Auth Token."

Microsoft Learn (Official Vendor Documentation): Configure an SMS channel for TeleSign.

Section: Step 2: Configure the SMS channel in Omnichannel for Customer Service.

Identifier: "In the SMS account details section... for TeleSign, enter the Customer ID and API Key."

Microsoft Dynamics 365 Documentation: Supported SMS providers.

Reference: Details the specific metadata requirements for third-party gateway authentication within the Omnichannel administration interface.

In Dynamics 365 Customer Service, unified routing for cases requires the configuration of a single work stream dedicated to the "Record" channel (specifically the Case entity). While you can have multiple intake rules, they all feed into one work stream that defines the routing logic for that entity.

To ensure that cases are actually moved into the Omnichannel queues upon assignment to a user or queue (rather than just changing the owner field), the "Automatically move records to owner's default queue" (referred to in the solution as "Automatically move records in queue") must be enabled at the entity level within the solution metadata. This ensures the routing engine triggers correctly when a record is created or updated.

Microsoft Learn (Official Documentation): Create work streams for unified routing. Section: "Create a work stream for entity records." This confirms that a single work stream is configured per entity type for routing.

Microsoft Learn (Official Documentation): Set up routing for entity records. Section: "Enable an entity for routing." It specifies that for the Case entity, you must enable routing and specifically mentions the "Automatically move records to owner's default queue" setting in the entity definition.

Microsoft Power Platform Documentation: Entity metadata properties. Explains the AutoRouteToOwnerQueue property which controls the movement of records into queues upon assignment.

Microsoft Dynamics 365 Customer Service Documentation: Overview of Unified Routing. Details the architectural requirement of mapping entity types to specific work streams to manage distribution logic.

The process begins by installing the Customer Service Analytics template app from AppSource. Once installed, you must establish data connectivity by providing the Dynamics 365 organization URL to the app. After the connection is established, the semantic model (dataset) refresh frequency is configured to ensure the data stays current. The Power BI workspace content must then be published to make it available to the organization. Finally, administrative settings within Dynamics 365 must be updated to enable Power BI reporting at the environment level and specifically embed or add the dashboard into the Customer Service Hub for agent and manager visibility.

Microsoft Official Documentation: "Install and use the Customer Service Analytics app for Power BI." Section: Configuration and Installation.

Microsoft Power Platform Documentation: "Configure Power BI dashboards in Dynamics 365 Customer Service." Section: Embedding Power BI Content.

Microsoft Learn (Customer Service): "Analyze customer service data with Power BI." Module: Integration Steps for Analytics Hub.

Dynamics 365 Admin Center Guide: "Settings -> Products -> Features -> Power BI reporting." Identifier: Doc-D365-CS-Analytics-2024.

The URL format to access the landing page that lists all available model-driven apps within a Dynamics 365 environment is https://.crm.dynamics.com/apps. Option A, https://.dynamics.com/apps, represents this format, albeit with a simplified domain structure. The /apps suffix is the crucial component that directs the user to the "app location" where they can select and run the specific customized app. This page serves as the central hub for all applications a user has access to within that environment.

B: This is the base URL for the Dynamics 365 environment, which typically redirects to a default app, not the specific page listing all available applications.

C: This format is incorrect. The path for a specific app uses /apps/ (lowercase) followed by the app's unique name, not /Apps/uniquename/.

D: This URL is syntactically incorrect due to a misplaced double quote after the organization name placeholder, making it an invalid web address.

1. Microsoft Learn. (2023). Access apps on the web. Microsoft Docs. In this article

the section "Go to the apps page" explicitly states

"To find your apps

go to https://.crm.dynamics.com/apps". This confirms that the /apps path is the correct destination for the app location.

2. Microsoft Learn. (2023). Model-driven app URL structure. Microsoft Docs. This document details the URL structure for a specific app as https:///apps/

which demonstrates that the format in option C is incorrect.

3. Microsoft Learn. (2023). Sign in to Dynamics 365 and Office apps. Microsoft Docs. This page clarifies the base URL structure for an environment (e.g.

https://your-org-name.crm.dynamics.com)

supporting the analysis that option B represents the root URL

not the app listing page.

The setContextProvider method from the Live Chat SDK JavaScript API is used to register a function that supplies custom context data to a chat session. This method must be called before a chat is initiated. If users report that context variables are not being populated, the most likely cause is an issue with the implementation of setContextProvider—either it has not been called, it was called after the chat started, or the function passed to it is not returning the data correctly. Therefore, troubleshooting must begin by examining the setContextProvider implementation.

B. startProactiveChat: This method is used to programmatically initiate a proactive chat with a user, which is unrelated to providing context variables for a standard chat.

C. startChat: This is an event that fires when a chat session begins. It is a result of the chat initiation process, not a method for providing data to it.

D. getContextProvider: This method is not part of the official, documented Live Chat SDK JavaScript API. The correct method for registering the context provider is setContextProvider.

E. initializeNewConversation: This is not a documented method or event in the Live Chat SDK API for managing custom context.

1. Microsoft Learn. (2023). Send custom context. In Dynamics 365 Customer Service documentation. This document explicitly states

"Your application can set the custom context provider by using the setContextProvider method. The setContextProvider method should be called before a chat is started..." It also provides the required code samples.

Section: "Send custom context"

2. Microsoft Learn. (2023). Live chat SDK JavaScript API reference. In Dynamics 365 Customer Service documentation. This official reference lists all public methods and events for the SDK. setContextProvider is listed as a method

while getContextProvider

startProactiveChat (as a listener)

and initializeNewConversation are not present.

Section: "Methods"

In Dynamics 365 Customer Service, queues are used to organize, prioritize, and monitor the progress of work. Records are categorized within these queues to ensure they reach the correct agents.

• Cases: These are typically categorized by Products. The incident (Case) entity has a standard relationship with the product entity, allowing administrators to route cases to specific queues based on the product line requiring support.
• Activities: These represent tasks, emails, or phone calls. In a service environment, these are categorized by Services to align with service level agreements (SLAs) or specific service offerings.

Managed and Unmanaged solutions are distractors; they refer to the deployment and packaging framework of the Power Platform and are not used for business categorization of transactional records.

Microsoft Learn: Create and manage queues for cases. This documentation explains how to set up queues to route records like cases and activities based on attributes such as product or service type. (Section: "Create a queue", Paragraph 2).

Microsoft Learn: Product catalog overview. This identifies how products are linked to cases for organizational and reporting purposes within Customer Service Hub.

Microsoft Learn: Service entities (Service, Resource, and Service Appointment). Describes how service-related activities are tracked and categorized in the system.

University of Washington (Information School): CRM System Design and Implementation. Courseware discussing the logical grouping of entities (Cases to Products) for business process automation.

The proposed solution is incorrect because it suggests creating "custom question types," which is not a feature in Dynamics 365 Customer Voice (the successor to Voice of the Customer). Users must select from a predefined set of question types such as Text, Rating, and Net Promoter Score (NPS).

Furthermore, the most efficient and logical method to customize a standardized survey for different clients is to copy the existing survey to create a new version. This new version can then be modified as needed, preserving the original template. The solution's approach of creating a new survey from scratch is inefficient and does not leverage the existing standardized asset.

A. Yes: This is incorrect. The solution is based on a non-existent feature ("custom question types") and proposes an inefficient workflow that ignores the best practice of copying an existing template.

1. Microsoft Learn. (2023). Available question types in Dynamics 365 Customer Voice. This document lists the specific

predefined question types available (Choice

Text

Rating

Date

Ranking

Likert

File upload

and NPS). It makes no mention of creating custom question types.

Reference: https://learn.microsoft.com/en-us/dynamics365/customer-voice/question-types (Section: "Available question types")

2. Microsoft Learn. (2023). Copy a survey. This document outlines the correct procedure for the scenario. It states

"You can create a copy of a survey... Copying a survey creates a new survey with the same questions and settings as the original survey." This is the appropriate method for creating client-specific versions of a standard survey.

Reference: https://learn.microsoft.com/en-us/dynamics365/customer-voice/copy-survey (Paragraph 1)

3. Microsoft Learn. (2022). Voice of the Customer deprecation. This document confirms that Voice of the Customer (VoC) is deprecated and replaced by Dynamics 365 Customer Voice. The concepts in the question apply to Customer Voice

which is the current

relevant application for the MB-230 exam.

Reference: https://learn.microsoft.com/en-us/dynamics365/voice-of-customer/voc-deprecation (Paragraph 1)

To meet the requirement of asking questions automatically before a chat session begins without additional licensing, Pre-chat surveys are the native configuration within the Omnichannel for Customer Service chat widget. While Power Virtual Agents (now Copilot Studio) can ask questions, it often requires additional licensing depending on the tenant's current SKU.

For protecting sensitive data like credit card numbers, Data masking rules are the standard mechanism. These rules use regular expressions to identify and mask sensitive patterns (like credit card strings) in real-time, preventing the information from being visible to the agent or stored in the plain-text transcript, ensuring compliance and security.

Microsoft Learn (Dynamics 365 Customer Service): "Configure a pre-chat survey." This documentation specifies that pre-chat surveys are used to gather information from users before a conversation starts.

Reference: Section: "Omnichannel for Customer Service" > "Chat" > "Configure pre-chat survey."

Microsoft Learn (Dynamics 365 Customer Service): "Create and manage data masking rules." This guide explains how to define masking patterns to hide sensitive data in chat and asynchronous channels.

Reference: Section: "Omnichannel for Customer Service" > "Security" > "Data masking."

Microsoft Dynamics 365 Licensing Guide (2024/2025 editions): Clarifies that basic Omnichannel capabilities include Pre-chat surveys, whereas Power Virtual Agents/Copilot Studio integration may involve separate service credits or licensing tiers.

Microsoft Tech Community - Customer Service Blog: "Best Practices for Securing Customer Data in Omnichannel." (Official Product Team publication). Details the application of Regular Expressions (Regex) within Data Masking rules to redact PCI (Payment Card Industry) data.