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-email-drafting.md
feature-copilot-email-drafting.mdv1 · history
CurrentApplies to EnterpriseUpdated 6 days agoSource Microsoft Learn ↗

What it does

Copilot writes customer email replies from case context, either in the side pane or inline in the rich text editor. Admins can also embed Copilot prompts inside email templates, so a template ships with instructions like "add warranty information and pitch the extended warranty" that Copilot fills in when the rep applies it.

Key facts

  • Three separate surfaces, three separate settings. Write an email - Help pane (side pane), Contextual email drafting with AI (inline in the rich text editor, under Settings > Features), and Copilot for email templates / Copilot recommended email templates for prompt-enabled templates.
  • Inline contextual drafting applies to Customer Service and standalone Contact Center. It is not available in the embedded Contact Center experience.
  • Copilot prompts in email templates and Copilot-powered template recommendations both went to public preview on 15 April 2025 and reached GA on 31 October 2025 in the 2025 wave 2 release plan. Contextual partial email content followed the same GA date after a July 2025 preview.
  • A template can carry multiple Copilot prompts, but only one prompt per template may use knowledge sources — that's the Use knowledge sources toggle on the prompt.
  • Every prompt needs alternate text. That's what renders for reps who don't have Copilot permissions, so the template still works for unlicensed users. Skip it and those reps get a template with a hole in it.
  • Email drafting is one of the few Copilot features that can use external web resources. Up to 5 trusted web domains, searched 2 levels deep from the configured domain, refreshed daily, and the domains must be publicly indexed by Bing.
  • Trusted webpages apply to email only. Ask a question and Draft a response cannot use external web sources; they use the Dynamics 365 knowledge base and Copilot Studio sources instead.
  • Copilot Studio knowledge sources are the mirror image: supported for Ask a question and Draft a response, not supported for Write an email.
  • Context fields are configurable via Manage data — case title, description, customer contact, subject — but case notes and email content are fixed and cannot be removed.
  • Email sentiment is documented as preview. Translation is a separate checkbox, Let representatives translate responses using Copilot, and requires the languages to be provisioned in Dynamics 365 first.
  • Configuring templates needs CSR Manager and System Administrator.

When to use / skip

Enable side-pane email drafting on any Customer Service deployment where email is a real channel. It's GA, it's low risk, and reps can ignore it. Inline drafting in the editor is the better experience once reps are past the novelty stage, because it keeps them in one place.

Prompt-enabled templates are the part worth real design effort, and also the part most projects skip. They're how you get consistent, on-brand output instead of whatever the model felt like writing. If the client has an existing library of 60 email templates and strong tone-of-voice rules, this is where you spend the workshop time. If they have three templates and no style guide, don't bother — plain drafting plus custom instructions will do.

Trusted webpages are worth it only where the client has genuinely useful public content — published product manuals, a public support site. Pointing it at a marketing site produces confident, useless emails.

Configuration decisions

  • Side pane, inline, or both. Running both is fine but you're training reps on two entry points.
  • Which templates get Copilot prompts, and which single prompt in each is allowed to reach knowledge. That "one knowledge prompt per template" limit shapes the template design, not the other way round.
  • The alternate text for every prompt — decided by whoever owns tone of voice, not by the person doing the config.
  • Which 5 trusted domains, if any, and whether Bing search is enabled in the Power Platform admin center to support them.
  • Which case fields feed email context, and whether custom fields carrying the actual issue detail need adding.
  • Whether translation is on, and which languages are provisioned to back it.

Gotchas

  • Trusted domains need public Bing indexing. An intranet, an authenticated support portal or a freshly launched site will not work, and the failure is silent — Copilot just writes without that content.
  • The 2-levels-deep crawl limit bites on sites with deep documentation trees. Content four clicks from the domain root is invisible.
  • Reps without Copilot privileges see the template's alternate text, not an error. If alternate text is missing or lazy, the client discovers it when a customer receives a half-written email.
  • Knowledge sources configured in Copilot Studio will not be used for email drafting no matter how many times you republish. It's a documented feature-by-source split, not a config error.
  • Case notes and email content are always in the email context and can't be removed via Manage data. If the client has sensitive internal notes on cases, that's a policy problem to raise before go-live, not after.
  • Enabling any of this needs the AI terms opt-in in the admin center and, outside the US, India, Australia and the UK, cross-region data movement enabled in the Power Platform admin center. Both are tenant-level and both need someone with authority to agree to them.

Consultant notes

  • Build two or three prompt-enabled templates during the design phase and demo those, not the generic "write an email" button. That's the conversation that gets the client's content team engaged.
  • Tell the client plainly that Copilot drafts do not get sent unreviewed, and check whether their QA process needs adjusting to reflect that reps are now editing rather than writing.
  • Get the trusted-domain list agreed with whoever owns the client's public web presence. Marketing changing the site structure will quietly degrade email quality with no alert.
  • Before go-live, test drafting with a rep who has a restricted custom security role. Copilot email failures on custom roles are almost always the missing Copilot interaction privileges.
  • Push back on "can Copilot send the email automatically". It can't in this feature, and the clients who ask usually want an autonomous agent instead.

Worth another look when email sentiment leaves preview, or if the trusted-domain limit or crawl depth changes.

Was this accurate?
Related
Copilot ask a question and knowledge sources07-copilot-in-customer-serviceCopilot knowledge drafting from cases07-copilot-in-customer-serviceKnowledge article templates and categories03-knowledge-baseCopilot access, privileges and data controls07-copilot-in-customer-serviceCopilot case and conversation summaries07-copilot-in-customer-serviceCase Management Agent07-copilot-in-customer-service