Knowing where the process stands
An order may be awaiting approval, waiting for stock confirmation or ready to be submitted to the ERP.
The business needs to know which steps have completed and what should happen next.
Getting information between systems is one thing. Managing the work that happens between them is another.
Integration and orchestration solve different problems.
Understanding the distinction becomes important when CRM activity involves multiple applications, departments and decisions.
An integration allows applications to exchange information or request an action.
Imagine a salesperson closes a deal in HubSpot.
An integration sends the relevant details to an ERP, where an order is created.
The ERP returns an order number, which is recorded against the opportunity in HubSpot.
This is a straightforward example of system integration.
The process might be triggered by a CRM workflow, an API request or an event in another application.
For many organisations, this is exactly what they need.
There is no reason to make a simple integration more complicated than necessary.
Now consider a more demanding order process.
Before creating the order, the organisation needs to check inventory, confirm pricing, validate the customer’s credit status and obtain approval where necessary.
Those activities may involve several applications and people.
Some steps can happen simultaneously.
Others depend on earlier steps being completed.
An approval might take several hours.
A system might become unavailable halfway through.
Orchestration coordinates those activities and maintains the overall state of the business process.
An order may be awaiting approval, waiting for stock confirmation or ready to be submitted to the ERP.
The business needs to know which steps have completed and what should happen next.
If a system becomes unavailable, some actions may be retried.
But retries need care.
A request to create an order shouldn’t create a duplicate simply because the first response was lost.
A well designed process can track completed actions and avoid repeating transactions unnecessarily.
Not every decision should happen automatically.
A discount might require approval from a sales manager.
A credit issue might require finance to intervene.
An orchestrated process can pause, obtain the required decision and continue when the necessary conditions have been met.
An AI assistant might initiate an order by interpreting an employee’s request.
It could retrieve information and invoke an authorised action.
The orchestration process can then coordinate the operational steps using established business rules.
That distinction matters.
If two systems simply need to exchange information according to established rules, a conventional integration may be the better approach.
Orchestration becomes useful when the business needs to coordinate dependencies, approvals, long-running activities and exception handling.
The objective is to introduce the level of engineering appropriate to the problem.
A business process might begin from Slack, conversational AI, a custom application or the CRM itself.
The interface initiating the request doesn’t change the operational requirements.
The business still needs to know what happened, which actions succeeded and how problems should be resolved.
Integration connects the systems. Orchestration coordinates the business process.
Kongo helps organisations establish which approach their requirements justify, then engineers the solution.
Talk to Kongo about your requirements, the systems you already operate and what you’re trying to improve.