Add human review to Copilot Studio AI decisions
Diesen Beitrag auf Deutsch lesen
Use Copilot Studio and SharePoint to route unmatched loan purposes to a human reviewer through Outlook or Teams, then record the decision and rationale.
TL;DR
Copilot Studio can compare a loan purpose with a SharePoint list of Allowed and Flagged categories. If no match exists, the agent returns Human-Review, sends an Outlook or Teams review request, waits for a Yes or No decision and rationale, and updates the SharePoint application record.
Original by Matthew Devaney, on Matthew Devaney. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Define explicit Allowed and Flagged categories, and configure the agent to return Human-Review when no exact match exists so uncertain cases do not receive an unattended decision.
- Admins/CoE: Assign the human review action to a named reviewer and store the decision, review status, and rationale in SharePoint so the workflow remains traceable.
- Leadership/Business: Identify decisions that are too risky for an agent to make alone and ensure reviewers can respond before the process continues.
Frequently asked questions
How does the agent in the loan example decide when a person has to review?
The agent compares the stated loan purpose with a list of pre-evaluated purposes. If a match exists, it returns that exact purpose and its category.
What does the human review action collect and how does it reach the right person?
The flow sends an Outlook message titled Action Required together with the applicant's name.
How does the flow record human and automated decisions in SharePoint?
After a human review, an expression sets the decision field to Allowed for yes and otherwise to Flagged, the human-reviewed flag to yes, and the rationale is copied over.