A sales manager configuring Copilot for Sales in Outlook wants that when a rep drafts an email to a contact at an account flagged 'Enterprise' tier, the assistant automatically creates a Dataverse follow-up task assigned to the account's customer success manager. Native email assistant actions in Copilot for Sales don't include this cross-record task creation. How should the manager extend Copilot for Sales to add this capability?
Select an answer to reveal the explanation.
Short Explanation
The trick here is noticing exactly when the manager wants something to happen: while the rep is still typing the email, not after it's sent and logged somewhere. That rules out anything that only reacts to a saved record, because a draft in Outlook hasn't been saved as an activity yet. What actually works is wiring a custom action powered by an automated flow directly to that drafting moment, so the task gets created for the customer success manager right as the rep is composing, no extra click needed. There's no hidden setting that already does this, so looking for a toggle to flip is a dead end. And punting the whole thing to reps doing it manually ignores that this platform is built to connect to exactly this kind of backend record. When the built-in behavior doesn't cover a workflow you need, a custom action tied to the right trigger point is how you extend it properly.
Full Explanation
The correct answer is A. Copilot for Sales supports custom actions built on Power Automate, so triggering a flow off the email-draft event lets the manager create a Dataverse task tied to the account's customer success manager exactly when a rep is drafting to an Enterprise contact, extending behavior the product does not provide out of the box. Option B is incorrect because no such 'auto follow-up' toggle exists in Copilot for Sales; inventing a setting instead of building the missing capability would not produce the desired behavior. Option C is incorrect because Copilot for Sales does integrate with Dataverse, so telling reps to work around it abandons an available extensibility path in favor of manual effort. Option D is incorrect because a Dataverse business rule fires on record save, not on an in-progress Outlook draft, so it cannot react to the moment the manager cares about, and it would only trigger, if at all, after the rep has already sent the email and it has been logged as an activity. The custom action approach is the only one of the four that actually hooks the drafting moment itself.