Almanac
Microsoft/d365csDynamics 365

Consultant-focused KB for Microsoft Dynamics 365 Customer Service: implementation notes, gotchas, and configuration decisions beyond the official docs — across case management, queues and routing, knowledge base, SLAs, omnichannel, agent experience, Copilot, analytics, and administration.

d365cs/07-copilot-in-customer-service/feature-copilot-ask-a-question.md
feature-copilot-ask-a-question.mdv1 · history
CurrentApplies to EnterpriseUpdated 6 days agoSource Microsoft Learn ↗

What it does

Ask a question is the Copilot help pane chat where a rep types a question in natural language and gets an answer grounded in configured knowledge, with citations. Draft a response is the same engine aimed at live chat, producing a suggested reply the rep can send or edit.

Key facts

  • Both are GA. They run in the Copilot help pane (side pane) in Copilot Service workspace, enabled under Support experience > Productivity > Copilot settings > Manage.
  • Supported knowledge sources for Ask a question and Draft a response are the Dynamics 365 knowledge base and knowledge sources configured in Copilot Studio. External web resources are not supported for either — that's email only.
  • Copilot Studio knowledge sources are still preview and support public websites, SharePoint, file upload, Dataverse and enterprise data via Microsoft Graph connectors. Copilot connectors are not supported.
  • Copilot reads only the content attribute of the knowledge article table. Anything in custom fields, attachments, tables or images inside the article body is not read.
  • Articles must be the latest version, in Published state, and tagged with the relevant UI language. The knowledge index refreshes daily, so publishing changes are not immediate.
  • Custom instructions on the Customer Support agent cap at 5,000 characters and apply only when the Dynamics 365 knowledge base is the source. They are not applied to Copilot Studio sources.
  • Filters come in three kinds: preset (always applied, invisible to reps), representative (visible, rep can toggle) and automated (applied contextually, optionally exposed to the rep). Limit is 5 filters per category. Supported field types are String, Whole Number, Option Set and Two Options.
  • Regional coverage differs by feature. Ask a question is broadly available except China; Draft a chat response is restricted to North America, Europe and the UK, and its language list is much shorter — English, Danish, Dutch, French, German, Italian, Japanese, Spanish, Portuguese (Brazil) and Thai.
  • Deterministic response mode forces verbatim, repeatable output for a given input rather than a fresh generation each time. Article tagging for verbatim responses and custom instructions in Ask a question both hit GA on 28 February 2026 in the 2025 wave 2 plan.
  • The Customer Support agent can be extended in Copilot Studio (Extend agent with Copilot Studio, GA) to add tools and change behaviour.

When to use / skip

This is the feature that lives or dies on knowledge quality, and that is the conversation to have before you enable anything. A client with 40 well-maintained published articles gets a good result. A client with 900 articles, half of them superseded and none of them tagged with a language, gets confident answers from 2019 documentation and blames Copilot.

Enable Ask a question wherever knowledge management is in reasonable shape. Draft a response is worth it for chat-heavy operations, but check the region and language list first — it's the most restricted of the agent-facing Copilot features and plenty of European multi-language deployments discover that late.

Filters are the part most teams skip and then need. If knowledge is segmented by brand, region or product line, configure filters at the same time you enable the feature, not after reps complain about cross-brand answers.

Configuration decisions

  • Dynamics 365 knowledge base only, or Copilot Studio sources as well. Adding Copilot Studio brings SharePoint and web content in scope but loses your custom instructions and rules out email drafting from those sources.
  • What goes into the 5,000 characters of custom instructions: tone, formatting, escalation behaviour, terminology, what to say when the answer isn't in knowledge.
  • Which filters are preset (silently enforced) versus representative-visible. Preset is the right default for security-adjacent segmentation; rep-visible is right for convenience.
  • Whether to turn on deterministic responses, and for which content — usually the compliance-sensitive answers where variation is unacceptable.
  • Whether the enhanced features set (advanced case analysis, app navigation by prompt, multistep reasoning) is enabled for the side pane — it's opt-in there, always on in the immersive experience.

Gotchas

  • Copilot reads the content attribute only. Clients who keep resolution steps in a custom field, an attached PDF or a table inside the article get answers with the useful part missing, and nothing in the UI tells them why.
  • Daily index refresh means a published fix is not answerable today. Set that expectation before the client tests it ten minutes after publishing.
  • Custom instructions silently stop applying the moment Copilot Studio sources answer the question. Tone and escalation rules apply inconsistently and it looks like the model ignoring instructions.
  • The knowledge-source-to-feature matrix is easy to get wrong: web sources for email only, Copilot Studio sources for Ask a question and Draft a response only. There is no combination that gives you everything.
  • Language tagging on articles is not optional. Untagged articles are effectively invisible to Copilot even though they look fine in the knowledge search UI.
  • Copilot Studio knowledge sources are preview. Don't design a client's go-live-critical knowledge strategy around them and don't put them in a support agreement.
  • Docs are inconsistent on the immersive Copilot experience — one page calls it preview, another describes it as GA in North America and preview elsewhere. Check the state in the client's own tenant and region before demoing it.

Consultant notes

  • Run a knowledge audit before enabling. Count published, latest-version, language-tagged articles. That number, not the total article count, is what Copilot is working with, and it is usually a shock.
  • Demo with the client's ten most common questions, prepared in advance. Freestyle demos of Ask a question find the gaps in knowledge, which is a useful exercise but a bad first impression.
  • Write the custom instructions with the client's service manager in the room. The escalation sentence — what Copilot says when it doesn't know — is the one that matters most and is always left as a default.
  • Check filters against the client's data segregation rules before go-live. Preset filters are the mechanism people reach for as an access control, and they are not one; article-level security still needs the normal knowledge permissions.
  • If the client wants SharePoint content in Ask a question, price in Copilot Studio licensing and the preview caveat explicitly, in writing.

Worth revisiting once Copilot Studio knowledge sources go GA, or if Draft a response picks up more regions and languages.

Was this accurate?
Related
Copilot knowledge drafting from cases07-copilot-in-customer-serviceCopilot email drafting and prompt-enabled templates07-copilot-in-customer-serviceKnowledge-first deflection or more agents11-decision-guidesKnowledge article templates and categories03-knowledge-baseKnowledge article lifecycle03-knowledge-baseCopilot access, privileges and data controls07-copilot-in-customer-service