Dynamics 365: Verbatim Knowledge Setup

Key insights

• Verbatim knowledge responses: The video explains how Dynamics 365 Customer Service Copilot can return the exact wording from a knowledge article instead of summarizing or rephrasing it.
  This ensures agents deliver approved text exactly as written when accuracy matters.
• Why it matters: Industries like healthcare, finance, insurance, and government need precise, legally reviewed language to meet rules and protect customers.
  Verbatim responses reduce risk from accidental wording changes and support regulatory compliance.
• Article-level control: Verbatim behavior is set inside the knowledge article, not in Copilot itself.
  Knowledge managers tag content in the Copilot Service workspace so the system respects approved wording at retrieval time.
• doNotSummarize tag: To force an entire article to be returned verbatim, add the doNotSummarize keyword to the article and publish it in the Copilot Service workspace > Service > Knowledge Articles.
  Copilot then returns the full article text unchanged when it matches a query.
• Section-level verbatim: For only part of an article, select the subsection and apply the Verbatim icon so Copilot returns just that marked text verbatim.
  This lets organizations protect critical phrases while allowing normal summarization elsewhere.
• Trust and auditability: Verbatim responses include a link back to the source and let agents use the Check sources option to verify origin and accuracy.
  That creates a clear audit trail and builds confidence in AI-driven replies.

Overview of the Video

In a recent YouTube presentation, Dian Taylor - [MVP] (Dynamics 365 Talk) demonstrates a new capability in Dynamics 365 Customer Service that lets organizations return exact text from knowledge articles to customer service representatives. She frames the feature as a response to an important question: when must an AI assistant stop paraphrasing and instead deliver the precise, approved wording? Consequently, the video focuses on how to tag articles or specific sections so the Copilot assistant returns content verbatim rather than summarizing it.

Taylor highlights scenarios where precision matters, such as compliance statements, safety instructions, and legal wording. She also shows step-by-step how knowledge managers can apply tags and icons in the knowledge editor to control Copilot’s behavior. Overall, the video aims to help organizations balance conversational support with the need for exact messaging in regulated contexts.

How Verbatim Tagging Works

The solution centers on tagging content inside the Copilot Service workspace, not on changing Copilot’s global settings. For entire articles, the technique involves adding the keyword doNotSummarize so that Copilot returns the full article text. In contrast, for selective control, the editor can mark individual sections with the Verbatim icon, which tells Copilot to deliver only that selected passage verbatim.

When an agent uses the Ask a question feature, Copilot consults the knowledge base and respects these tags during retrieval. The returned result includes the original wording and a link back to the source article so representatives can check the source. This design ensures that fidelity to approved language remains visible and traceable in the support workflow.

Benefits and Practical Tradeoffs

Verbatim responses bring clear advantages for regulated industries because they reduce the risk of deviation from approved language and thus support compliance and auditability. In addition, the approach builds trust since agents can confirm the source and verify accuracy before responding to customers. However, this precision comes at a cost: strict verbatim replies may sound less conversational and friendly than AI-generated summaries, which can affect customer experience in some contexts.

Therefore, organizations must weigh the tradeoff between exactness and tone. For example, using verbatim tagging for legal disclaimers or safety procedures makes sense, but applying it to everyday troubleshooting steps may make responses feel stiff. By selectively tagging only the necessary sections, teams can preserve conversational engagement while protecting critical wording.

Implementation Challenges and Recommendations

Adopting verbatim tagging requires clear governance and ongoing maintenance, because knowledge content changes and grows over time. If teams do not manage tags consistently, they risk having outdated or inconsistent verbatim sections that can create confusion. Moreover, tagging at the article level versus the section level introduces choices about granularity and control, and each choice brings different overhead for content owners.

To address these challenges, Taylor suggests practical steps such as establishing tagging guidelines, auditing tagged content regularly, and training knowledge managers on when to use doNotSummarize versus the Verbatim icon. In addition, organizations should track version history and localization needs, since exact wording often requires separate reviews for other languages. These practices reduce the risk of content drift and help maintain clarity across the knowledge base.

Operational Considerations and Best Practices

Performance and user adoption are important factors to monitor after enabling verbatim responses. For instance, frequent use of verbatim content can increase the number of long, exact-text returns that agents must read and confirm, which may affect handling time. Thus, teams should pilot the feature in targeted areas first and measure both compliance outcomes and agent efficiency.

Finally, Taylor emphasizes combining verbatim tagging with visible source checks inside the Copilot pane to keep agents informed and confident. By balancing precision with usability—tagging only where required and training staff on the workflow—organizations can gain the compliance benefits of verbatim replies without sacrificing too much conversational quality. Consequently, this measured approach helps teams deliver accurate, auditable, and user-friendly support.

Keywords

Set up verbatim knowledge responses Dynamics 365, Dynamics 365 knowledge base verbatim responses, Configure verbatim responses Dynamics 365, Dynamics 365 Customer Service knowledge management, Knowledge article verbatim responses Dynamics 365, Dynamics 365 knowledge response setup guide, Verbatim knowledge responses Power Platform, Dynamics 365 knowledge management best practices