SymConductorAgent orchestration
Orchestrate agent actions from start to finish.
SymConductor™ is the orchestration layer for agentic actions. Coordinate the signal that starts a case, the agents that handle its steps and the people who need to decide – without treating each handoff as a new task.
- Carrier emailProof of delivery attached
- POD-4821.pdfShipment SH-4821 · 1 page
Triggers
Start from the signal your operation already produces.
Connect the workflow to a defined event: a document arriving, a schedule becoming due, a system update or a request from a person. An event tells the workflow what happened and which case needs attention.
Trigger examples
- Documents
- A proof of delivery is received.
- Operational signals
- An ETA moves outside an agreed tolerance.
- Inbox or message
- A supplier response or customer request arrives.
- Schedule
- A recurring review becomes due.
- System call
- An approved API or webhook signals a change.
- Manual start
- A person requests a review.
Handoffs
Pass the evidence forward, not just the instruction.
A document specialist may identify a discrepancy. A validation step compares it with the order. A reviewer needs both before deciding what to change. SymConductor's coordination model keeps those responsibilities connected around the same case.
Independent checks can be designed as parallel branches; decisions that depend on their results wait for the relevant evidence.
Illustrative workflow
From an incoming delivery document to a decision-ready case.
Follow one delivery-and-invoice review through five stages. Each stage has a defined task, and a defined response when something is missing.
| Stage | Work | If something is missing |
|---|---|---|
| Retrieve | Gather the delivery document and related records | Identify the missing source |
| Plan | Define the checks needed for this case | Ask for clarification |
| Call | Use the approved tools for those checks | Record the failed or unavailable operation |
| Verify | Review the result against the workflow's rules | Hold the proposed update |
| Write | Apply an authorised change through a supported connection | Preserve the unresolved state for follow-up |
The verification and approval requirements belong to the workflow definition. They are not granted by a model's confidence.
Human decisions
Approvals at the right points keep you in control.
SymConductor pauses the run and brings the proposed change, its evidence and its decision owner together. The person deciding sees why the workflow paused and what decision is needed before it continues.
Failure handling
SymConductor handles exceptions by the rules you set.
You define the retry, timeout and escalation behaviour before a workflow goes live. An unavailable source or uncertain result then leads to a defined next step – not repeated attempts without a limit.
Defined for each workflow
- How long the workflow waits for a response.
- Which calls can be retried safely, and how often.
- How duplicate events and writes are handled.
- Which conditions require a person.
- What record remains when a run stops.
FAQs
Questions teams ask about SymConductor.
SymStudio™ is the no-code agent builder, where you define and review the workflow. SymConductor™ is the orchestration layer that coordinates its execution.
That is a separate model-selection feature associated with SymRouter™. SymConductor™ coordinates the workflow steps and their dependencies.
Yes. Multi-agent workflows are part of the platform’s scope. Confirm the available handoff, branching and execution patterns for your implementation.
The workflow pauses at its defined decision boundary until the decision owner acts. Notification, escalation and resume behaviour are agreed for each deployment.
No. Reviewing or replaying a run is different from reversing a change in an external system. Any compensating action requires its own support and authorisation.
Bring one workflow. See it orchestrated from start to finish.
Walk through its trigger, the systems it touches and the decisions along the way – including where the run stops for a person.