O
OOMeta
← Back to Insights

August 2026 · 5 min read

Orchestration Is the Real Agent Gap
UiPath and Infobip

Orchestration Is the Real Agent Gap: UiPath and Infobip

Key Definitions

Orchestration Layer The middleware that strings agents, robots, APIs, documents, and people into one governed business process — handling permissions, memory, data retrieval, audit, and human handoff.

Coding Agent AI programming assistants like Claude Code, Cursor, GitHub Copilot, and Codex whose main output is code. They build prototypes fast, but do not by themselves run those prototypes as governed business processes.

Guardrail A checkpoint that validates an agent's content and actions against business rules before output reaches a customer or system, preventing out-of-bounds behavior from shipping.

In the past two weeks, two very different companies delivered the same verdict. UiPath launched Maestro Flow on August 19; Infobip's AgentOS narrative, covered on August 27, points to the same conclusion: enterprises are not short of agents — they are short of the orchestration layer that turns agents from prototypes into governed business processes.

Two vendors, one verdict: the gap is orchestration

UiPath's Maestro Flow is a developer-first orchestration canvas: it lets coding agents — Claude Code, Cursor, GitHub Copilot, Codex — design, run, observe, and govern complete end-to-end business processes from their native development environment, as a single artifact from prototype to production. UiPath CPTO Raghu Malpani's line is widely quoted: "Enterprises don't have an agent problem; they have an orchestration problem. With coding agents, it's never been easier to build an agent. But running a real business process, spanning agents, robots, systems, and people — and being able to prove what happened at every step — needs an orchestration layer that ties these together in a real business environment."

Infobip's AgentOS is the same argument from a different direction. The Croatian communications company launched AgentOS on April 1 as a control layer for AI agents across marketing, sales, and support — connecting customer data, workflow automation, and channels like WhatsApp, SMS, RCS, email, and voice, then handing off to a human when the machine hits its limits. The commentary frames it as the next phase of enterprise AI being orchestration, not conversation: making the bot accountable for action, not just for dialogue.

Why coding agents build prototypes but cannot run processes

The context numbers show the size of the problem. BCG's 2025 research found 45 percent of APAC firms are experimenting with or deploying agentic AI; Adobe reports 88 percent of Asia-based respondents say fragmented data limits responsive, personalized customer experiences. Companies are not short of pilots — they are short of production systems. UiPath's diagnosis: coding agents make building trivially easy, but without an orchestration layer, process logic fragments, becomes hard to govern and costly to maintain — prototypes cannot ship, work stalls waiting on review, automations go untracked, and the cost of experimentation itself becomes a brake on progress.

Infobip's chief innovation officer Krešo Žmak makes the same layered point: the consequential layer sits around the model. Its Knowledge Agent answers from company documents via retrieval-augmented generation; the Agentic Chunker paired with a cross-encoder lifts vector-search recall from 70 to 95 percent while cutting document preparation from months to hours; Active Recall carries conversation history through a session; guardrails check agent output against business rules before it reaches a customer.

What the orchestration layer must provide: permissions, memory, audit, handoff

An effective orchestration layer needs four things, and skipping any of them breaks it. Permissions: role-based access control, data isolation, SSO, and API-level authentication — Infobip claims SOC 2 and ISO 27001 certifications, GDPR compliance, AES-256 encryption, web-interface actions logged for up to five years, and agent-layer tracing so a company can reconstruct why an AI responded as it did. Memory: cross-session context rather than starting from zero. Reliable retrieval: a governed knowledge base. Handoff: human approval and clean escalation paths — when the machine is uncertain or business impact is high, escalate rather than push through.

LAQO: from conversation to accountability

Infobip's flagship example is digital insurer LAQO. LAQO GPT runs on WhatsApp, grounded in policy documents, routing conversations by intent from the first message; an orchestrator was later added to coordinate a knowledge agent alongside two specialist agents for travelers and contractors. Per Infobip: the chatbot handled 30 percent of inbound requests, supported a 330 percent jump in sessions, and resolved 90 percent of queries within three to five messages; in the first half of 2026, LAQO GPT resolved about 40 percent of all customer interactions on its own, alongside a 4.7 customer satisfaction score and a 26 percent rise in completed travel insurance purchases. These figures come from the vendor's own client relationship — treat them as a case study, not an independent benchmark.

Three judgments for buyers

Judgment one: evaluate the orchestration layer as its own line item

When evaluating an agent, ask four questions separately: can it access the right data, operate inside governance rules, escalate cleanly to a human, and prove the cost and audit of every step? The answers decide whether it is a conversation tool or a production system.

Judgment two: pay for infrastructure, not for a likable chatbot

AgentOS is priced like infrastructure — a platform fee, message-processing fee, AI credits, and channel fees. The real cost and value both live in the orchestration layer: data access, governance, audit, handoff — not how charming the assistant is.

Judgment three: accept agents on accountability, not conversation

Acceptance metrics should center on action: how many interactions were resolved (not just handled), how much was completed inside guardrails, how often it went out of bounds, and whether audits can reconstruct the reason. Making the bot accountable for action is the whole reason an orchestration layer exists.

For digital transformation leads, these two weeks of product signal combine into one selection note: coding agents solve the build, orchestration solves the run. The former is already commoditized to near-free; the latter — permissions, memory, audit, handoff — is the real battlefield of the next round, and the hard gap for production-grade agents.

References

  • UiPath press release: UiPath Launches UiPath Maestro Flow (2026-08-19) — https://www.uipath.com/newsroom/uipath-launches-maestro-flow
  • Deeptech Times: The agentic AI battleground — who will control the enterprise orchestration layer? (2026-08-27) — https://deeptechtimes.com/2026/08/27/the-agentic-ai-battleground-who-will-control-the-enterprise-orchestration-layer/
  • BCG 2025 research: 45% of APAC firms piloting or deploying agentic AI (via Deeptech Times); Adobe: 88% of Asia respondents cite fragmented data limiting personalization

FAQ

Why say enterprises don't have an agent problem but an orchestration problem?+

UiPath CPTO Raghu Malpani's exact framing: enterprises don't have an agent problem, they have an orchestration problem. Building an agent with coding agents has never been easier, but running a real business process spanning agents, robots, systems, and people — and proving what happened at every step — needs an orchestration layer.

What does UiPath Maestro Flow solve?+

It lets coding agents like Claude Code, Cursor, GitHub Copilot, and Codex design, run, observe, and govern end-to-end business processes from their native development environment. The version prototyped is the version that ships — no rebuild or re-platforming, running on the Maestro orchestration engine.

What results does Infobip's AgentOS show in the LAQO case?+

Infobip reports that in the first half of 2026 LAQO GPT resolved about 40 percent of all customer interactions on its own, with a 4.7 customer satisfaction score and a 26 percent rise in completed travel insurance purchases; earlier it handled 30 percent of inbound requests with 90 percent resolved within three to five messages. These are the vendor's own figures.

What must an orchestration layer provide?+

Permissions (RBAC, data isolation, SSO), cross-session memory, reliable data retrieval, an audit trail for every step, and a clean handoff to a human when the machine hits its limits. Skip any of these and automation just delays the moment a customer gets annoyed.

What should a buyer pay for?+

AgentOS is priced like infrastructure: a platform fee, a message-processing fee, AI credits, and separate channel fees. The test is not how well the bot talks, but whether the agent can access the right data, operate inside governance rules, escalate cleanly, and prove it is worth the cost.