Find records and draft policies
Ask for the evidence behind a decision and get exactly what your VeriProof access allows. Policy authors can draft and test a rule from the same conversation, then review it in VeriProof before it goes live.
Integrations, Microsoft Copilot Studio
Bring your business rules into Copilot Studio
The agents your business builds in Copilot Studio never go through your developers, and they still touch loans, accounts, and customers. Give them the same rules, the same reviewer, and the same record as everything else in the fleet, without leaving the conversation.
From a question to a checked action
Check business actions
A conversation ends in a business change more often than anyone plans for. The confirmed action gets checked against your rules first, and what happened is kept on record.
See the decision behind a loan update
A person picks an action for a loan shown in Copilot Studio. Before the record changes, the lending service checks the current facts against policy.
The approval does not go through. The loan is recorded as denied under the lending policy, and the agent says so, with a link to the evidence that explains why.
Keep the checks that protect your business
Current business facts
Decisions use the current record in the business system, rather than treating conversation text as the source of truth.
Existing user access
Microsoft sign-in identifies the person. Their existing access in VeriProof and the business system determines what they can do.
One checked change
The connected action service checks the rules before changing the record and reports the result for review.
Where could your team use more control?
The loan example is a starting point. Apply the same approach to the business actions you connect.
Case and application decisions
A case decision needs more than a conversation. Current records and the person's assigned role inform whether an action can proceed.
Account and payment changes
Policy checks come before the account update or payment instruction, giving your team control at the point of change.
Customer communications
Keep sensitive messages within your rules. The sending service can check the recipient, purpose, and content before release.
A starting point for your developers
Customer setup guide
Connection instructions and examples cover evidence access, policy drafting, and business actions. Your developers can choose the path that fits.
Maintained reference code
Start with the working loan example, then connect the record and business action from your own system.
Connected evidence
The decision history connects the request to its recorded result, including human review when the workflow requires it.
Bring policy checks and decision evidence to Copilot Studio.
Tell us what your Copilot Studio agent needs to do. We will show you where the check goes and what your compliance team sees afterward.