Rules
Workflows run the actions you configured, in order, against the conditions, dependencies, and exception steps you set. No AI is involved unless you add it.
Agentic enterprise orchestration
Orchestrate IT and business operations together
When operations span systems and teams, execution depends on more than individual tasks. Symphony connects technical operations and business processes through workflows covering actions, dependencies, approvals, and exceptions.
Technology stack
Applications, databases, operating systems, cloud.
Business operations
Processes spanning enterprise applications and functions.
Symphony
Orchestration platform
- Execution
- Dependencies
- Approvals
- Visibility
Trusted by enterprise teams
Platform scope
One platform across the technology stack and the business
A technical procedure crosses infrastructure layers. A business process crosses applications and functions. Symphony brings the required work into defined workflows, with shared controls over execution.
Full-stack orchestration
Run technical procedures across the stack.
Refreshes, upgrades, and maintenance require coordinated actions across several technology layers. Symphony connects preparation, execution, and validation within reusable workflows.
Enterprise orchestration
Connect business processes across the enterprise.
Business operations depend on activities across systems and teams. Symphony coordinates process steps, dependencies, approvals, and exception responses across functions.
- Connect actions Bring system tasks and existing automation into a workflow.
- Manage dependencies Define prerequisites, execution order, and information passed between steps.
- Include decisions Set approval points and responses to exceptions.
- Follow progress Track workflow status and review recorded activity.
The agentic layer
Rules run the routine, agents handle the rest, people decide
Every workflow on this page runs through the same layer. Predefined rules carry the steps that never change. Maestro brings a person in through Microsoft Teams when a decision is needed. isAI watches for the conditions you define and initiates the responses you have permitted. Whichever is doing the work, the controls beneath apply.
Maestro
Review the context of a step, request an action, and give or withhold approval from Teams. The approval is part of the workflow record, not a message beside it.
isAI
Monitors the supported conditions you define and initiates the responses you have already permitted, inside the policy you configured. Nothing it does sits outside that policy.
One workflow
Actions, dependencies, approvals, exceptions, and the record of what ran
No mode authorises itself. Access, approvals, validation, and execution records apply to all three, and are set out in the governance section below.
Orchestration in practice
Twelve workflows, before and after Symphony
Explore how Symphony brings system actions, checks, and human decisions into an orchestrated procedure.
Illustrative workflow
Operating system patching
Context
A maintenance window requires coordinated work across operating systems, databases, and applications.
TodayManual handoffs between teams6 handoffs
Change boardInfrastructureDatabaseApplication
Confirm downtimeApprove windowStop databasePatch and rebootStart and checkRestart and verifyClose change
With SymphonyOne orchestrated sequence
Approval gate: Prepare
SymphonyChange boardInfrastructureDatabaseApplication
1Prepare
2Protect
3Execute
4Validate
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Prepare: Check prerequisites, system health, and the maintenance window.
- 2Protect: Perform the required backups and service shutdowns.
- 3Execute: Apply patches and run the configured restart sequence.
- 4Validate: Check service health, record results, and notify the relevant teams.
Exception handlingIf a check fails, follow the defined stop, recovery, or escalation path before dependent work proceeds.
Illustrative workflow
System refresh and copy
Context
A non-production system is refreshed from production, across cloud, operating system, database, and application.
TodayManual handoffs between teams5 handoffs
Business ownerApplicationDatabaseInfrastructure
Request refreshExport target configProvision storageRestore backupPost-copy stepsConfirm data
With SymphonyOne orchestrated sequence
Approval gate: Prepare
SymphonyBusiness ownerApplicationDatabaseInfrastructure
1Prepare
2Protect
3Execute
4Validate
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Prepare: Confirm the source and target systems, capacity, and the agreed refresh window.
- 2Protect: Preserve target-specific configuration and take the agreed backups.
- 3Execute: Run the copy, restore, and post-copy reconfiguration across the layers in scope.
- 4Validate: Reimport users and roles, check the system responds, and record the result.
Exception handlingIf a post-copy check fails, hold the target and route the detail to the responsible team.
Illustrative workflow
Kernel and database upgrade
Context
An upgrade touches the application kernel and the database under it, with its own prerequisite checks.
TodayManual handoffs between teams6 handoffs
Change boardApplicationDatabaseInfrastructure
Check prerequisitesApprove changeStop servicesUpgrade databaseApply kernelReboot hostVerify versions
With SymphonyOne orchestrated sequence
Approval gate: Prepare
SymphonyChange boardApplicationDatabaseInfrastructure
1Prepare
2Protect
3Execute
4Validate
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Prepare: Verify current versions, prerequisites, and the approved change window.
- 2Protect: Coordinate the backup and the controlled stop of dependent services.
- 3Execute: Apply the kernel and database steps in the configured sequence.
- 4Validate: Restart, confirm versions and service health, and record the outcome.
Exception handlingWhere a prerequisite is unmet, stop before the change and route it for review.
Illustrative workflow
Cloud provisioning and migration
Context
A landscape is built or moved on AWS, Azure, or Google Cloud, with the application stack configured on top.
TodayManual handoffs between teams5 handoffs
Cloud teamNetworkDatabaseApplication
Request quotaOpen routesBuild serversInstall databaseInstall applicationConfirm connectivity
With SymphonyOne orchestrated sequence
Approval gate: Prepare
SymphonyCloud teamNetworkDatabaseApplication
1Prepare
2Provision
3Execute
4Validate
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Prepare: Confirm the target design, network, and access required for the build.
- 2Provision: Create the infrastructure through the configured cloud and automation actions.
- 3Execute: Install or move the database and application layers in sequence.
- 4Validate: Check connectivity and service health, and record what was built.
Exception handlingIf provisioning returns an error, stop the sequence and route the detail with its context.
Illustrative workflow
Background job execution and recovery
Context
Scheduled jobs run across systems overnight, and a failure blocks everything waiting behind it.
TodayManual handoffs between teams5 handoffs
OperationsService deskApplicationBusiness owner
Spot failed jobRaise ticketDiagnoseConfirm rerunRestart jobCheck chain complete
With SymphonyOne orchestrated sequence
Approval gate: Recover
SymphonyOperationsService deskApplicationBusiness owner
1Schedule
2Monitor
3Recover
4Record
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Schedule: Run the job chain against its dependencies and business calendar.
- 2Monitor: Watch for failures, long-running jobs, and step errors.
- 3Recover: Run the configured restart or recovery step for the failure in question.
- 4Record: Log what failed, what ran, and the resulting state.
Exception handlingWhere recovery is not permitted without a decision, route the job with its log for approval.
Illustrative workflow
Incident triage and remediation
Context
An incident is raised in the service desk and needs an action in the application or infrastructure layer.
TodayManual handoffs between teams5 handoffs
Service deskIncident managerApplicationInfrastructure
Log incidentAssignInvestigateCheck hostApply fixClose ticket
With SymphonyOne orchestrated sequence
Approval gate: Act
SymphonyService deskIncident managerApplicationInfrastructure
1Receive
2Assess
3Act
4Close
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Receive: Pick up the incident from the connected service management tool.
- 2Assess: Gather the supporting context from the systems involved.
- 3Act: Run the permitted remediation step for that incident type.
- 4Close: Update the ticket with what ran and the resulting state.
Exception handlingWhere the action is outside policy, route it to the responsible person with the context gathered.
Illustrative workflow
Order-to-cash
Context
An order moves across commercial, finance, and fulfilment systems, with decisions required along the way.
TodayManual handoffs between teams6 handoffs
SalesCreditFulfilmentFinance
Enter orderCredit check by emailRelease orderPick and shipInvoiceChase mismatchApply payment
With SymphonyOne orchestrated sequence
Approval gate: Review
SymphonySalesCreditFulfilmentFinance
1Validate
2Review
3Coordinate
4Reconcile
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Validate: Check order information against the relevant business data.
- 2Review: Assess credit conditions and route exceptions to the appropriate approver.
- 3Coordinate: Sequence permitted fulfilment and billing actions across connected systems.
- 4Reconcile: Match payment information and route unresolved differences for review.
Exception handlingWhere judgment is required, route supporting context to the responsible person and record the decision.
Illustrative workflow
Procure-to-pay
Context
A requisition becomes an order, a receipt, and an invoice, across procurement and finance systems.
TodayManual handoffs between teams6 handoffs
RequesterApproverProcurementAccounts payable
Raise requisitionApprove by emailCreate orderConfirm receiptMatch invoiceResolve mismatchPay
With SymphonyOne orchestrated sequence
Approval gate: Approve
SymphonyRequesterApproverProcurementAccounts payable
1Validate
2Approve
3Match
4Settle
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Validate: Check the requisition against the relevant master and contract data.
- 2Approve: Route the order for approval according to the configured thresholds.
- 3Match: Compare order, receipt, and invoice through the configured checks.
- 4Settle: Release the permitted payment actions and record the outcome.
Exception handlingWhere the match does not resolve, route the difference with its documents for review.
Illustrative workflow
Purchase request approval
Context
A purchase request needs information checks, a business decision, and follow-on actions in connected systems.
TodayManual handoffs between teams5 handoffs
RequesterApproverProcurementFinance
Raise requestAsk for missing detailsResend with detailsApprove by emailCreate orderConfirm budget
With SymphonyOne orchestrated sequence
Approval gate: Approve
SymphonyRequesterApproverProcurementFinance
1Initiate
2Check
3Approve
4Continue
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Initiate: Receive the request and required information.
- 2Check: Validate the configured data requirements and prerequisites.
- 3Approve: Route the request to the designated reviewer.
- 4Continue: Execute the configured follow-on actions after approval and record progress.
Exception handlingRoute incomplete or rejected requests for resolution before dependent actions proceed.
Illustrative workflow
Record-to-report and month-end close
Context
The close runs to a calendar, across several systems, with dependencies between the tasks.
TodayManual handoffs between teams6 handoffs
ControllerAccounts payableAccounts receivableIT operations
Publish close calendarPost accrualsRun period-end jobsPost receiptsChase reconciliationsRerun failed jobSign off
With SymphonyOne orchestrated sequence
Approval gate: Report
SymphonyControllerAccounts payableAccounts receivableIT operations
1Prepare
2Execute
3Reconcile
4Report
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Prepare: Confirm the close calendar, task owners, and prerequisite postings.
- 2Execute: Run the scheduled close tasks in their configured dependency order.
- 3Reconcile: Run the configured reconciliation checks and surface differences.
- 4Report: Complete the reporting steps and record what ran and when.
Exception handlingWhere a reconciliation does not clear, hold the dependent task and route the difference.
Illustrative workflow
Joiner, mover, and leaver
Context
A person joins, changes role, or leaves, and the change has to reach every connected system.
TodayManual handoffs between teams5 handoffs
HRLine managerIT service deskApplication owners
Record changeApprove access by emailRaise ticketsCreate accountsConfirm to HRClose case
With SymphonyOne orchestrated sequence
Approval gate: Validate
SymphonyHRLine managerIT service deskApplication owners
1Receive
2Validate
3Provision
4Record
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Receive: Pick up the change from the owning human resources system.
- 2Validate: Confirm the role, the access implied, and the required approvals.
- 3Provision: Apply the permitted account and access actions across connected systems.
- 4Record: Confirm completion in each system and record the evidence.
Exception handlingWhere an access change needs review, route it for approval before it is applied.
Illustrative workflow
Supply and fulfilment exceptions
Context
A planning or fulfilment run raises exceptions that sit between planning, warehouse, and logistics teams.
TodayManual handoffs between teams5 handoffs
PlanningWarehouseLogisticsIT operations
Run planning jobReview exceptionsCheck stockAdjust planRebook shipmentRerun fulfilment
With SymphonyOne orchestrated sequence
Approval gate: Route
SymphonyPlanningWarehouseLogisticsIT operations
1Run
2Detect
3Route
4Confirm
- Approval gate: A designated person decides, through Maestro in Microsoft Teams where configured, and the decision is recorded.
- Exception path: The configured response runs, isAI initiates a permitted response within policy, or the issue routes to a person.
- 1Run: Execute the scheduled planning or fulfilment jobs in dependency order.
- 2Detect: Identify the exceptions the run has raised across the systems involved.
- 3Route: Send each exception to the responsible team with its supporting detail.
- 4Confirm: Re-run the affected step once resolved and record the outcome.
Exception handlingWhere an exception blocks a downstream step, hold that step until the decision is recorded.
Workflow steps and integration requirements depend on the process and systems involved.
Execution and governance
Controls that apply however the work runs
Define how workflows run, which actions require approval, and how exceptions receive attention. Symphony combines orchestration with AI-assisted interaction while retaining configured execution controls: Maestro handles approvals and requests in Microsoft Teams, and isAI initiates permitted responses within configured policy.
-
Access
Apply roles and permissions to operational actions.
-
Approvals
Require human review at designated steps.
-
Validation
Check prerequisites and results within the workflow.
-
Execution records
Review recorded activity and workflow progress.
Integration fit
Built on the systems you already run
Build workflows using supported integrations, APIs, reusable actions, and existing scripts. Configure the connectivity and permissions required for execution across your environment.
Enterprise applications and service management
SAPSAP BTPServiceNowJiraTopDeskFreshservice
Cloud infrastructure
Microsoft AzureAWSGoogle CloudIBM Cloud
Databases and operating systems
SAP HANAOracleIBM DB2Microsoft SQL ServerSAP ASELinuxWindows
Automation and interfaces
AnsibleTerraformREST APIsShell and PowerShellABAPCustom scripts
Integration and action coverage are reviewed against your requirements.
Evaluation
Questions teams ask before a first workflow
Where should we start?
Choose an operation or process with recurring manual coordination, several system dependencies, or frequent exceptions. Map the current steps, required decisions, and expected outcome.
Is Symphony limited to the examples shown here?
The examples illustrate possible applications. Symphony supports building workflows for technical and business procedures using reusable actions, integrations, and custom extensions.
Do we need to replace our existing systems?
Symphony connects to existing systems through supported interfaces. The integration approach depends on the applications, available actions, and access requirements involved.
How are approvals and exceptions handled?
Workflow configuration defines approval points and exception responses. These include stopping execution, running recovery steps, or routing an issue for human review.
Is AI required for every workflow?
No. Predefined workflows run using configured actions, conditions, and dependencies. AI-assisted interaction supports additional ways to work with the platform.
What should we bring to a demo?
Bring an operation or business process, the systems involved, and the challenges you want to address. This helps the team focus the discussion on relevant capabilities.
Next step
Start with one workflow
Bring an operation or business process that crosses systems and waits on people. That is enough to see where orchestration fits.
- Your workflow, end to endThe steps, systems, and dependencies from trigger to completion, drawn as one sequence.
- Where decisions and exceptions sitWhich steps wait for an approval, and what happens when a check fails.
- How your systems connectThe integrations, actions, and permissions the workflow would need in your environment.