- Organisation
- Capita, United Kingdom
- Predecessor
- Siloed teams and disconnected systems in Capita's lead-to-cash process, with 350+ agents already running across multiple platforms
- Destination
- Expanded MuleSoft adoption connecting the underlying revenue stack, with MuleSoft Agent Fabric used as a centralised orchestration and governance layer across hundreds of agents
- Workload
- MuleSoft and MuleSoft Agent Fabric
- Stage
- operational
Verified platform change
Salesforce reported on 18 June 2026 that Capita expanded its MuleSoft adoption, uses MuleSoft to connect the underlying revenue stack and uses MuleSoft Agent Fabric as a centralised orchestration and governance layer across hundreds of agents.
Transition
From: Siloed teams and disconnected systems in Capita's lead-to-cash process, with 350+ agents already running across multiple platforms
To: Expanded MuleSoft adoption connecting the underlying revenue stack, with MuleSoft Agent Fabric used as a centralised orchestration and governance layer across hundreds of agents
Known unknowns
The dated Salesforce source proves the bounded expanded-adoption and operational orchestration state by 18 June 2026. It does not establish a private exact cutover day, claim replacement of every Capita integration platform, or prove autonomous operation of every agent without human or policy controls.
Official sources
Updates
Source rechecked on 26 September 2026. The current first-party Salesforce release has not materially changed; the bounded expanded MuleSoft adoption and operational Agent Fabric orchestration state remains supported without a private exact-cutover, every-platform-replacement or uncontrolled-autonomy claim.