Agent Intake & Approval Agent
Key Result: Every request logged and approved before build Layer: Governance Problem: Uncoordinated agent requests and overlapping builds Status: Live
Home • Agent Registry • Results • Roadmap • Campaign & Commercial Projects • Leadership & Strategy • How to Build MOCC • HubSpot Expert in South Wales
Layer: Governance
Status: Live
Platform: Microsoft Copilot Studio • Microsoft Teams • SharePoint
Deployment: Veriforce — all agent requests
Last updated: October 2026
Business Problem
As the number of agents grew, there was no consistent way to capture what a new agent was meant to solve, who had approved it, or how it worked. Requests came in informally, and documentation, where it existed, was written after the build. That made ownership, risk review and long-term visibility harder to maintain.
Functionality was also being built that overlapped with existing agents and tools in the stack.
Solution Overview
The Agent Intake & Approval Agent is a Copilot Studio topic embedded in Teams. It asks the requester structured questions about what the agent helps solve, what it outputs and how it works, and tidies the answers into a single request. Every request is logged on a SharePoint list. The agent then produces a report for the approvers showing any potential crossover with existing agents and existing tech stack functionality. The request and report go to the Head of Digital Marketing Operations and the Head of Digital Performance for approval before any build. Approved requests are logged on an approved list, and the agent then creates the agent’s documentation so its setup and workings stay visible over the long term.
Business Value
- Every agent request is logged on a SharePoint list, giving a full record of what was asked for
- No agent is built without approval from two Heads
- Approvers see potential overlap with existing agents and stack functionality before any build starts
- Approved agents get documentation created by the agent, so setup and workings stay visible long term
- Requests and approvals sit on separate lists, giving a clear audit trail from request to approval
Cost Savings
- Time reclaimed: 3 hrs/month = £75/month = £900/year at the MOCC’s illustrative £25/hour rate
- Governance value: Every build is intentional and tracked, creating an auditable approval trail and helping prevent overlapping builds
Design Insights
Approval happens before build, so overlap with existing agents and tools is caught before any time is spent building.