… 10 unchanged lines …
  - Selection criteria include a look-back period. On first start the agent processes every qualifying lead created inside that window; afterwards it works in near real time.
  - Re-run behaviour is specific: a full re-run happens when a lead's email goes from empty or invalid to valid, when the account name goes from empty to valid, or when the lead newly meets the selection criteria. A change from one email address to another triggers only email validation. Related-table criteria are checked hourly, and only for leads inside the look-back period.
  - The agent uses Copilot Studio capacity — prepaid message packs or pay-as-you-go — for research, target customer profile matching and initial outreach generation. Viewing insights already generated costs nothing.
+ - It feeds the [[feature-recommended-actions-agent]] by default. A **Connected skills** > **Recommended Actions** toggle on the agent's settings page controls whether its action recommendations appear in the **Suggested actions** carousel on the Leads list page; the integration is on unless you turn it off, and turning it off leaves the agent's own interface unaffected. Note that prioritised actions from this agent are charged.
  - Language is set on the agent, not per user. Research page headings appear in the seller's language while insights and outreach emails come out in the agent's language.
  - Research and engage adds an **AI disclaimer** and **Other terms** field alongside the email signature, for telling recipients they're corresponding with an agent. Get legal to write it.
  - Once configured, the agent can't be deleted without Microsoft support. Stopping it prevents new leads being taken on; leads already in flight continue to hand-over or escalation.
    … 31 unchanged lines …
  
  ---
  
- *Worth another look after the next release wave — the agent has changed version and behaviour repeatedly, and the upgrade path is the part that bites.*
+ *Refreshed 19 Sept 2026 for the Recommended Actions connected skill. Worth another look after the next release wave — the agent has changed version and behaviour repeatedly, and the upgrade path is the part that bites.*