web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Community site session details

Community site session details

Session Id :

How to Generate a Lead Summary with Copilot Actions using Power Automate Flow

Inogic Profile Picture Inogic 1,135 Moderator

Microsoft Copilot in Dynamics 365 Sales provides powerful AI-generated insights such as Lead summaries, opportunity summaries, relationship intelligence, and email drafting suggestions. While many users interact with these prompts directly within the Sales app, fewer organizations leverage them in automated scenarios.

In this blog post, we’ll demonstrate how to incorporate outputs generated by Copilot in D365 Sales into automated workflows using Power Automate, specifically using the Lead Summary prompt.

Business Use Case

In many sales organizations, sales representatives qualify Leads throughout the day, and managers rely on visibility into these newly qualified Leads. Reviewing each Lead manually can be time-consuming, and important context may be missed without opening the record. When a salesperson qualifies a Lead, the record moves forward in the sales process, but managers often need quick insight into who the customer is, what the requirement is, why the Lead was qualified, and any relevant engagement or activity history.

Instead of receiving a generic notification such as “Lead ABC has been qualified,” we can automatically send a more informative message: “Lead ABC has been qualified. Below is the AI-generated Lead summary.” This approach provides immediate business context, enables faster managerial review, reduces navigation time, improves pipeline oversight, and supports more efficient coaching and follow-up.

Please find below steps to send Lead Summary to manager using Copilot Action:

Step 1: Configure the Flow Trigger

Create an automated cloud flow using the Dataverse trigger “When a row is added, modified or deleted.” > Set the table to Lead and the change type to Modified.

Although you could restrict the trigger to specific events such as Lead qualification or status changes, for this example we will allow it to run on updates, but only for high-priority Leads.

To ensure this, add a Trigger Condition in the trigger settings:

@equals(triggerOutputs()?[‘body/prioritycode’], 2)

This condition ensures the flow runs only when the Lead’s Priority is set to High, preventing unnecessary executions and keeping the automation efficient... Read More

Comments