
TL;DR
Process orchestration software coordinates long-running work across systems, teams and AI agents, and it holds the state of every case until that work finishes.
It sits above BPM suites, iPaaS and single-tool workflow automation, because it owns the whole case and the waits between steps.
Revenue processes such as lead to loan, claims and vehicle sales run on two lanes, systems and conversation. Most products model the first lane far better than the second.
A question, a channel switch or a long silence should change the state of a case. Buyers should ask for that in writing.
Picture a home loan applicant we'll call Claire. By Thursday she has uploaded her payslips and cleared her identity checks, and she has sent one WhatsApp message asking whether her annual bonus counts as income.
The process dashboard shows her case on track, waiting on one document. Nothing in it records the question. She goes quiet, and the following week another lender funds her loan.
Process orchestration software exists to keep cases like Claire's moving, and it handles the system side well. This guide covers what the category does, how it differs from BPM and iPaaS, and the part of a revenue process that most tools leave unmodelled.
What is process orchestration software?
Process orchestration software coordinates one long-running piece of work across systems, teams and AI agents, and it remembers where every case stands. A loan application can run for weeks. Something has to know which step it's on, what it's waiting for, and what happens when that wait runs out.
What the software does day to day
Tracks state. Every case has a current step, an owner and a history.
Sequences work. It calls systems, assigns tasks and starts agents in the right order.
Waits properly. A case can sit for nine days on a missing document and resume from the right place.
Handles exceptions. Timeouts, failed calls and rejected documents each have a defined path.
Reports on the flow. Teams can see where cases pile up and how long each step takes.
The term covers more than one thing, so check which one you're reading about. Search results mix enterprise process platforms such as Camunda and Flowable, IT job schedulers, and SAP's product of the same name. This post is about the first group.
Analysts now track that group directly. Forrester evaluates adaptive process orchestration, which it describes as platforms that run AI agents and nondeterministic control flows alongside deterministic ones. Gartner publishes a Magic Quadrant for business orchestration and automation technologies, usually shortened to BOAT.
Agents are still early in this market. In a survey of 1,150 senior IT and business decision makers and architects at large organizations, commissioned by Camunda, organizations said they had automated 48% of their processes on average. Only 11% of their agentic AI use cases reached production in the past year.

How does process orchestration differ from BPM, iPaaS and workflow automation?
The short version is scope. Each category below coordinates a different amount of the work, and only the last one owns a case from start to finish across several systems.
| Category | What it coordinates | Where it usually stops |
|---|---|---|
| iPaaS | Data moving between applications | Short transactions, with no view of the whole case |
| Workflow automation | A fixed sequence inside one tool or team | The edge of that tool |
| BPM suite | Modelled and governed processes, often inside one suite | Changes that need a redesign of the model |
| Process orchestration | Systems, teams and agents across days or weeks | The system side of a customer-facing process |
Most companies run more than one of these, and that's fine. If you need a shortlist of engines, our guide to workflow orchestration tools compares them. For how a long-running case survives a crash, read our piece on fault tolerance.
Revenue processes run on two lanes, systems and conversation
Every customer-facing process has a system lane and a conversation lane. The system lane holds checks, documents, approvals and handoffs. The conversation lane holds what the customer says, asks, ignores and repeats.
The better vendor guides do put a customer in the example. Camunda's handbook walks through a mortgage applicant who uploads an ID, takes a selfie and supplies files. Those are the inputs a process engine expects.
Real applicants also ask questions, change channel, hesitate and go quiet. We read seven of the top guides and tools lists on this topic. None treats those moments as events that change the state of a case, and the closest is one line in Camunda's handbook about an agent resuming work when the customer replies.
As we wrote in why your process workflow is lying to you, a clean diagram can hide where the work actually stops.
Here's what each moment should do to a case.
A question opens an obligation to reply, and holds any automated chasing until the answer goes out.
A channel switch keeps the case and its history together, so WhatsApp, voice and email add to one thread.
An objection routes the case to the answer or offer that deals with it.
Silence past a set window triggers a next move chosen from what the customer last said.
A process that can't hear the customer will report a stalled case as on track.
Lead to loan stalls between application and disbursal
Lending shows the two lanes most clearly, because the system lane is so heavily regulated. Drop-off is common before anyone reaches a decision. In a small survey of 250 UK SME founders run by the lender Juice in November 2025, 59% said they had abandoned a loan application midway.
What the system lane does
It runs eligibility rules, pulls the bureau report, calls verification and eSign tools, assembles the file for underwriting and triggers disbursal. Orchestration software is very good at this sequence and at the waits inside it.
What the conversation lane does
It answers Claire's bonus question from policy, then guides her to the next document in the same chat. If she stops halfway through a form, it picks up from that field. A few KYC steps can run in the chat itself, connected to the verification tools the lender already uses.
We've mapped the leaks in more detail in our post on loan origination drop-offs.
The dashboard said on track. The customer had asked a question nobody answered.
A claim stalls while the policyholder waits for news
In claims, the system lane may be working perfectly while the customer has no idea. J.D. Power's study of 5,958 claimant evaluations, fielded from December 2024 to August 2025 and reprinted in full by InsuranceNewsNet, found that insurers deliver adequate digital updates just 22% of the time. The same study found that 22% of customers use more than one channel for the same question.
Both numbers describe the conversation lane. A status change in the claims system should become a plain update the policyholder can read. And a question asked in chat and again by phone should land as one open item on one case.
Healthcare has the same shape. In an American Medical Association survey of 1,000 physicians published in May 2026, 79% reported that patients abandon treatment because of authorization challenges.
The authorization is a system step. The patient who hears nothing while it runs is the conversation lane.
A vehicle deal stalls between enquiry and showroom
Car sales move from the web to a physical showroom, so context has to cross that gap. In a study of 1,700 dealership inquiries by DAS Technology, a vendor, from late 2024, 19% of responses took more than an hour.
Most deals still finish in person. In a survey of 2,300 buyers, Cox Automotive found that 53% of buyers completed all their purchase steps at the dealership.
So picture Marcus, who asks about a hybrid on the website at 9 p.m. and books a test drive on WhatsApp the next morning. The dealer management system records one appointment. The salesperson should also see the trim he asked about, the trade-in he mentioned and the reason he chose hybrid.
A vehicle sale closes in the showroom, on a conversation that began somewhere else.
Deterministic steps for compliance, agents for the conversation
Deciding which parts of a process run on fixed rules is the design question that matters most. Regulated steps need the same result every time, and customer language needs interpretation.
| Part of the process | Control type | Example |
|---|---|---|
| Eligibility and credit rules | Deterministic | Income and bureau thresholds |
| Required disclosures | Deterministic | Fixed wording sent at a fixed step |
| Customer questions | Agent | Answering a policy question from approved content |
| Stalled-case recovery | Agent | Choosing the next message from the conversation so far |
The agent acts on its own inside boundaries the team configures once. When a case needs a specialist, escalation is another branch in the process, set by a rule and carrying the full history with it.
That split also keeps agent projects scoped. An agent answering customers against approved content is a much smaller thing to take to production than an agent trusted with a credit decision.
What should you require from software running customer-facing processes?
Most buying checklists for process orchestration software come from IT, and they cover the system lane well. Add the second group below if customers are part of the process.
Process requirements
State that survives weeks. A case resumes correctly after a long wait or a system failure.
Rules and agents in one process. Deterministic and agentic steps share a single model and audit trail.
Write-back to systems of record. Your CRM, loan origination, claims or dealer management system stays current without manual entry.
Conversation requirements
Conversation events as triggers. A question, objection, channel switch or silence can start, pause or reroute a case.
One case across channels. WhatsApp, voice, email and webchat attach to the same record.
Memory an agent reads first. Every agent sees what the customer already said before it acts.
Stall reasons in reporting. You can see how many cases stopped at a step and how many stopped at an unanswered message.
How do you start with business process orchestration on one revenue process?
Trying to orchestrate every process at once is the slowest way to learn what your process orchestration tools can do. Pick one process with a clear end and a measurable stall, and work through four steps.
Map both lanes. Draw the system steps, then write down what customers ask or do at each one.
Read fifty stalled cases. Sort them by whether a step or a conversation stopped them.
Choose control types. Mark each step as a fixed rule or an agent, using the split above.
Measure time to resume. Track how long a stalled case takes to start moving again, and report it alongside completion rate.
Lead to loan is a good first candidate for a lender, and enquiry to test drive for a dealer group. Both have a clear finish, and both generate a lot of customer messages along the way.
Where Zigment fits on the stack you already run
Zigment is a Conversational Revenue Orchestration Platform for GTM teams, and it adds the conversation lane to the process you already run. Your loan origination system, claims platform or dealer management system stays in place.
Its Conversation Graph keeps a running timeline of what each customer said and did across WhatsApp, voice, email and webchat. AI agents read that timeline before they act. They qualify leads, answer questions, guide applicants to completion, chase stalled cases and write the outcome back to your systems.
The case status is only half the record
Pull last month's stalled cases and read the final message in each one. Some will have stopped at a document or an approval, and your process tool will have told you so.
How many stopped at a question nobody answered?
See how the Conversation Graph keeps that record across every channel a customer uses.