Close conversations after non-engagement in waiting state - > Configure auto-close after inactivity in the workstream.

Change auto-close duration for wrap-up state - > Configure channel state by using the web API.

Dynamics 365 Contact Center distinguishes between inactivity while a conversation is waiting and the lifecycle behavior of a conversation that has entered Wrap-up. For supported persistent channels, the workstream exposes an Auto-close after inactivity setting. Microsoft states that a conversation remaining in Waiting for longer than the configured inactivity interval is automatically transitioned to Closed. This capability applies to persistent chat, SMS, social, and Microsoft Teams channels.

Wrap-up closure is controlled through the underlying channel-state configuration. Microsoft documents that administrators can modify the auto-close duration for conversation states by updating the Channel State Configuration data. The value can be managed through Power Apps or programmatically through the supported Web API when an organization requires a business-specific timeout rather than the standard lifecycle duration.

Consequently, waiting-state inactivity belongs at the workstream level, while customized wrap-up state timing is handled through the channel-state configuration/API mechanism.

The source exhibit on page 30 confirms these two selections.

Study Guide reference: Implement channels - > Configure chat and digital channels - > Configure persistent conversations and conversation lifecycle settings.

An application tab template defines which application, entity record, dashboard, custom page, web resource, or other workspace component can open inside a representative session. Microsoft states that application tab templates specify applications that are available when representatives start a session in Copilot Service workspace.

Every multisession workspace session contains at least one application tab known as the anchor tab. Additional application tabs can also be configured so that when the representative accepts an interaction, the required records and applications are immediately available. For example, a session can open the active conversation, customer record, related case, knowledge search page, and a line-of-business application without requiring the CSR to navigate manually.

The application tab templates are then associated with a session template, which defines the overall session experience. Microsoft specifically describes session templates as reusable combinations of session attributes and application tab information.

Notification templates control information displayed before an interaction is accepted, not the data/apps loaded within the resulting session. Email and message templates relate to communication content rather than workspace composition.

Study Guide reference: Configure the Dynamics 365 Contact Center representative experience - > Configure application tab templates and session templates.

A quality-management and compliance process requires durable evidence of completed customer interactions. Voice call recording provides the actual audio record, allowing authorized reviewers to replay conversations for quality assessment, investigation, coaching, and compliance purposes. Microsoft supports administrators enabling call recording together with voice transcription and provides controls for accessing the resulting recordings and transcripts after conversations end.

Transcription creates a searchable textual representation of the voice interaction. When combined with appropriate retention controls, transcripts can be preserved for the organization's specified compliance period. Microsoft documents retention management for Contact Center transcripts and warns that recordings are subject to applicable consent and communications-recording laws.

Live sentiment analysis helps supervisors understand customer sentiment during or after an interaction but does not itself provide the retained conversation record. Real-time translation addresses language accessibility, while post-call surveys gather customer feedback. Neither substitutes for retaining the underlying communication.

Therefore, transcription with retention and voice call recording together provide the evidentiary artifacts needed for systematic quality review and compliant recordkeeping.

Study Guide reference: Implement channels - > Provision and manage the voice channel; configure recording and transcription capabilities.

External availability requires both an appropriate publication state and permission for the portal audience. Dynamics 365 knowledge articles follow a controlled lifecycle that includes Draft, Approved, Scheduled, Published, Expired, and Archived states. Microsoft documentation states that after an article has been completed and reviewed, it is published to make it available to portal customers. Publishing therefore ensures that draft or merely approved internal content is not automatically exposed.

Visibility must also permit the portal audience to view the content. Power Pages and Dynamics 365 knowledge management can use content-access controls and external/public-facing knowledge settings to determine which audiences can discover an article. Consequently, configuring article visibility for external users is required in addition to publishing.

Federated search concerns external knowledge sources and does not make unpublished Dynamics 365 articles externally available. Versioning is useful for article lifecycle management but does not itself expose content. Search indexing cannot override article publication state or audience authorization.

Study Guide reference: Configure the Dynamics 365 Contact Center representative experience - > Create and administer knowledge management - > Integrate knowledge into portals.

Microsoft explicitly supports a reference architecture in which an organization retains its existing CRM and CCaaS platform while adding Microsoft AI capabilities. In this model, Copilot for Service is embedded within the existing representative environment and provides AI assistance such as knowledge-based answers, summaries, drafting, and collaboration without taking ownership of the underlying interaction-routing architecture.

The critical architectural boundary is routing ownership. Microsoft's reference architecture states that customer interactions continue through the existing CCaaS channels and telephony, and work continues to be routed by the existing CRM/CCaaS provider. Copilot augments the representative experience but does not require Dynamics 365 to replace the external platform's queue assignment, transfers, or orchestration logic.

Options B and C violate the stated requirement because they transfer call orchestration into Dynamics 365. Option D also changes the existing architecture by bypassing the CCaaS routing implementation and rebuilding it through Power Automate.

Embedding Copilot as an assistance layer therefore provides the required incremental AI modernization without forcing a contact-center platform migration.

Study Guide reference: Deploy Dynamics 365 Contact Center - > Plan integration architecture; configure embedded and existing-CCaaS deployment patterns.

A session template controls how a representative session behaves when a work item is accepted. Microsoft defines a session template as a reusable combination of session attributes and application-tab information. It determines the session experience, including which application opens as the anchor tab and which additional application tabs are automatically opened when the session begins.

Because the requirement specifically concerns inconsistent session behavior, assigning the same session template across the relevant workstreams or representative scenarios standardizes what occurs when sessions start. This produces predictable behavior regardless of the department handling the interaction.

An application tab template defines an individual application that can appear inside a session, but it does not define the complete session behavior. A capacity profile controls concurrent workload and representative capacity, not workspace behavior. An experience profile governs a broader collection of representative-experience settings, including productivity tools, inbox, channels, and other features; however, the direct mechanism for standardizing session startup behavior is the session template.

Study Guide reference: Configure the Dynamics 365 Contact Center representative experience - > Configure session templates and application tab templates.

Package Contact Center customizations for promotion between environments - > Create a solution that contains the required components.

Promote the package from development to test with edit restrictions - > Import the package as a managed solution in target environments.

Solutions are the standard Power Platform packaging mechanism used to collect related Contact Center components and promote them between environments. The development solution should contain only the components required for the deployment scope, which makes the release deterministic and maintains component dependencies.

For downstream environments, Microsoft explicitly recommends managed solutions. The official Contact Center ALM module states that an unmanaged solution should be exported from development as managed and imported into downstream environments. Managed deployment establishes a managed layer and protects deployed configuration from casual or unintended direct editing. Microsoft also advises administrators not to edit managed records directly because doing so creates active unmanaged customization layers that can interfere with future upgrades and solution servicing.

Re-creating components independently in each environment defeats ALM consistency. Exporting changes directly from production reverses the intended promotion flow and weakens governance. The correct architecture therefore uses an unmanaged development solution as the authoring source and a managed package as the controlled deployment artifact for test and production.

Study Guide reference: Deploy Dynamics 365 Contact Center - > Create solutions for deployments; Configure ALM for deployments.

1. Register a Channel Integration Framework provider and host it as a web resource.

2. Use the Channel Integration Framework v2 to capture the interaction.

3. Call the Channel Integration Framework API to open an application tab.

VanArsdel is deliberately adopting the representative desktop before completing migration from its existing CCaaS platform. The technical requirements therefore call for Dynamics 365 Channel Integration Framework so the external communication provider can operate inside the Dynamics 365 model-driven representative experience.

The provider must first be registered so Dynamics 365 knows which channel provider implementation to load. The hosted web resource then functions as the provider application running inside the Channel Integration Framework environment. Channel Integration Framework 2.0 is appropriate because Microsoft designed it for integration of telephony channel providers with Dynamics 365 model-driven apps and exposes browser-based JavaScript APIs for communication-provider interactions.

After the interaction is available through the framework, Channel Integration Framework APIs can control the Dynamics workspace, including opening application content associated with the interaction. This allows the CSR to receive the interaction and expose corresponding CRM customer information without abandoning the standardized representative desktop.

Version 1 is therefore not appropriate for the required modern multisession Contact Center integration.

Study Guide reference: Deploy Dynamics 365 Contact Center - > Configure and extend connectors for Dynamics 365 Contact Center; configure integration architecture.

Prevent Payment Card numbers from appearing in AI-generated transcripts and conversations - > Create and manage data masking rules.

Retain customer interactions in accordance with company policy - > Classify and set retention policies by using Microsoft Purview.

The two requirements address different stages of information governance. Sensitive information must first be protected within the interaction itself. Dynamics 365 Contact Center data-masking rules detect configured patterns such as credit-card numbers and replace the protected data with masked characters. Microsoft documents that text masked in a conversation message is also masked in the corresponding conversation transcript. Contact Center includes predefined masking patterns for credit cards and allows administrators to define additional rules.

The second requirement concerns lifecycle governance rather than runtime visibility. Retention policy determines how long customer interaction records must remain available according to organizational and regulatory policy. In the case study, VanArsdel specifically handles PII and payment information and must prevent sensitive information from being retained in transcripts and AI-generated summaries while maintaining compliant records.

Field-level security protects Dataverse columns but does not redact sensitive values appearing inside conversation text. Sensitive-data redaction is related, but the supplied requirement specifically maps payment-card protection to configurable masking rules. Retention and classification are therefore handled independently through Microsoft Purview governance controls.

Study Guide reference: Deploy Dynamics 365 Contact Center - > Configure data protection, security, governance, and Contact Center environments.

1. Initialize Channel Integration Framework context.

2. Run the API to get conversationid details.

3. Run an API call to send messages by using conversationid as a parameter.

The integration first needs an initialized Channel Integration Framework context because VanArsdel is operating an external CCaaS provider through the Dynamics 365 representative desktop. The active interaction must then be identified so the integration can target the correct conversation rather than relying on an unrelated session identifier.

Dynamics 365 exposes an Omnichannel JavaScript API containing getConversationId, which retrieves the unique identifier of the current conversation, and sendMessageToConversation, which sends a programmatic message to a conversation. Microsoft documents conversationId as the identifier used to target a particular conversation; when supplied, sendMessageToConversation directs the message to that interaction.

This distinction is important because a representative can operate multiple sessions. Conversation identity is the reliable interaction-level identifier required by the API. Supplying both sessionid and conversationid is not the documented signature for sendMessageToConversation. Therefore, after the framework context is established, retrieve the conversation identifier and use that identifier when issuing the message operation.

Study Guide reference: Configure the Dynamics 365 Contact Center representative experience - > Extend the representative experience by using APIs and productivity capabilities.