A Microsoft cloud agentic solution that reads the tasking note, searches Content Manager, SharePoint and any other defined location, and cites every claim.
Full walkthrough, 3 minutes 15. Recorded from the working application.
Specialists in governed information for over 20 years. Fusion MCP is built on the Content Manager SDK we have spent that time working inside.
Nobody in a ministerial or parliamentary team needs help composing a brief. They need the approval from 2019, the figure the department actually published, and the background they wrote for a different committee last March. That is where the hours go, and none of it is drafting.
You are looking for something you cannot name precisely. A prior position, an approval, a figure the department has already used in public. Not knowing its title, its author or its date is what turns it into an afternoon.
The figure quoted this morning does not match the figure in the file. Someone has to catch that before the minister does.
The same background, assembled from scratch, because last time's version is filed under a title nobody would search for.
One line changes in clearance, the pack rebuilds, and the deadline has not moved an inch.
The parliamentary end of it runs to a calendar nobody in the department controls.
The brief has to exist before the question does. You are preparing against what you think is coming, across every portfolio issue live that week.
Line by line against the budget papers, and everything taken on notice lands on the committee's date rather than one that suits the department.
Thirty days in the Senate, sixty in the House. Miss it and the minister owes the chamber an explanation for the delay.
Any one of them can send it back, and the deadline does not move. Most of that traffic still runs on email.
Microsoft 365 Copilot reaches SharePoint, Teams, Outlook and OneDrive as standard. OpenText Content Manager carries its own security model, its own retention rules and its own permissions, so it stayed outside. That is where the decisions, the approvals and the correspondence live. We solved that.
The assistant surface
Microsoft SharePointSites, libraries and pages
Connected
Microsoft TeamsChannels and conversations
Connected
Microsoft OutlookMail and calendar
Connected
Microsoft OneDrivePersonal working files
Connected
OpenText Content ManagerThe record of decision
No connector
Anything reading it has to work out what each individual user may see, record by record, before returning a single result.
Terabytes of records accumulated over decades, not a sampled subset that fits in an index.
Carried with every record, and honoured on the way out as well as on the way in.
Our own component, built on the OpenText Content Manager SDK over twenty years of working inside it. It is the bridge that lets an agent read Content Manager, and the only component we supply. Everything else we deploy is a Microsoft service, reaching the Content Manager instance you already run.
Learn more about Fusion
Question Time briefs, estimates, Auditor-General examinations and questions on notice, on one data model.
Content Manager through Fusion MCP and SharePoint through the Microsoft 365 connector, in a single query under the officer's own permissions.
A Power Apps front end, Microsoft Copilot Studio doing the thinking, Microsoft 365 Copilot as the surface officers ask from, and one Informotion component opening the records underneath. Every other element is a Microsoft service running in Australian regions.
The application
Despatch BoxPower Apps
Brief registerAll five brief types
Clearance chainDrafting to minister's officeWhat does the thinking
Microsoft Copilot StudioThe discovery and drafting agentMicrosoft 365 CopilotThe surface officers ask fromHow it gets to the records
Fusion MCPResolves permissions and access
Azure API ManagementOne of three connection patternsMicrosoft 365 connectorFor SharePoint and your entire Microsoft 365 deploymentWhere the content stays
OpenText Content ManagerUnchanged, unmigratedMicrosoft SharePointSites, libraries and pagesTeamsOutlookWhat it runs on
Microsoft Power PlatformHosting and lifecycleMicrosoft DataverseBriefs, questions, clearance stepsMicrosoft Azure and Microsoft 365 are independently IRAP assessed for workloads up to and including PROTECTED, most recently in March 2026. Power Apps and Power Automate are named in scope of the ASD Blueprint for Secure Cloud.
Records stay in the systems that already hold them. No migration, and no second copy to govern.
Direct inside your own network, through Azure API Management, or via the Microsoft Power Platform data gateway.
Being the bridge into Content Manager means Fusion MCP also carries its security model. It resolves permissions and access record by record, so a search returns what that officer could already open, and nothing else. Nothing here changes who may see what.
Microsoft Entra ID carries the identity from the front end down to the record.
The Content Manager security model is honoured record by record, not folder by folder.
Source content stays where it is. Only references and the drafts you create are held.
Every search, retrieval and generation is logged and available for review.
While Despatch Box is designed for ministerial briefings, it is not the only government process you face. Each of these has an externally set deadline, an answer assembled from records held across systems, and a consequence for getting it wrong. We can help.
Locating every relevant record, then redacting and packaging the release.
Drafting a reply grounded in what the department has actually said before.
Formal written answers against a deadline and a clearance chain.
Assembling the case record from years of filed material.
Contract history, evaluation records and prior decisions in one view.
Annual, against the budget papers, with every line of expenditure traceable.
The first session is about your environment, not a generic demonstration. How your Content Manager is implemented, how briefs move through your clearance chain, and where the time actually goes. You will know what this looks like against your own setup, and what it would cost, before anything is deployed.
Two hours on your process, your clearance chain and how your Content Manager is configured.
Your own use cases, demonstrated against a test instance of Content Manager.
Deployed into your environment, with one team using it against live records.
Rolled out across the briefing types you choose, with filing and reporting in place.
