Guides
Breadcrumbs

What are OCP® Agents

Overview

An Agent in the Omilia context is an autonomous or semi-autonomous component designed to perform tasks within a contact center ecosystem. Agents integrate perception, reasoning, and action to handle customer interactions, automate workflows, and provide intelligent routing and responses.

Core Capabilities

Agentic Intelligent Routing (Concierge Agent)

The Concierge Agent provides a new paradigm for contact center routing by using real-time reasoning and contextual awareness instead of static queue logic and intent matching.

  • Zero-Shot Routing: Dynamically routes calls or chats to the optimal queue or agent without pre-programmed mappings (no intents)

  • Dynamic Queue Awareness: Continuously monitors queue load, agent skill, and conversation intent to make intelligent routing decisions. It is fully integrated with the Contact Centre to ensure real-time adaptability.

  • End-to-End Orchestration: Acts as a control layer across all channels and agents. Defines the agents, flows and context that should be through the entire conversation.

  • Seamless PhoneBook Integration: Supports routing based on PhoneBook entries to queues or extensions.

  • Automatic Disambiguations: Automatically detects missing or important information and prompts the callers before queue transfer.

This ensures minimal transfer rates, higher first-call resolution, and optimized operational efficiency. It enables a zero-day go live as it requires no training.

Dependencies: Requires integration with the CCaaS provider. Currently supported integrations are: RingCX for Queues and Phone Directory.

When to use:

  • New applications/customers that want to add intelligent routing and start the Self-Learning journey.

  • Existing Customers who want to add dynamic routing adaptation to their existing applications.

Task Agents

Task agents define all of Omilia’s Agents (regardless of their level of autonomy) designed to perform tasks. They perform multi-step workflows, integrating perception, reasoning, and action within the contact center ecosystem.

Agents can have three different levels of autonomy:

Low autonomy Agents

Fully powered by miniApps, it offers fully controlled and explainable agents to handle tasks that can be put together in a well determined flow. Applications designed to handle specific, well-defined tasks within a rigid and predictable workflow.

Characteristics

  • Deterministic flow with low/no autonomy.

  • Ideal for predictable and repeatable use cases.

  • Complete transparency and control over the conversational logic.

This level ensures reliability and full governance; ideal for customers who prioritize compliance, transparency, and predictable outcomes.

Medium autonomy agents

Omilia’s Medium Autonomy Agents (a.k.a Agentic Fallback) integrate seamlessly with existing deterministic (Low Autonomy) workflows (such as those built in Orchestrator and miniApps™) to enhance understanding and improve containment rates. There are two levels of fallback support:

  1. Asynchronous context update - The agent is updating the context of the conversation based on a wider understanding of the conversation.

  2. Full-handover - The Task Agents attempts to complete the task.

Medium autonomy agents are characterized by the following:

  • Adaptive Understanding: When predefined flows fail to capture a user’s intent or fail to fulfill the requested task, the Agentic AI dynamically interprets the request using contextual reasoning, enterprise knowledge, and a broader understanding of the context.

  • Intelligent Recovery: Rather than failing silently, the system activates a fallback agent that can clarify, infer, or autonomously complete the task based on business rules and guardrails.

  • Safe Escalation: If ambiguity remains, the fallback agent escalates intelligently to human agents or specialized systems with complete conversation context (through Intelligent Routing).

  • Determined intelligence: The boundaries and context of the AI agent are well contained within the task at hand, not allowing unbounded interactions with no visibility.

This approach bridges the gap between static workflows and autonomous AI, ensuring resilience and uninterrupted service continuity.

Agentic Fallback can be framed within any scope in an existing application. It can be enabled at the miniApp level (for example, enhancing understanding on a numeric miniApp while capturing a zip code) or at a task level (offering an agentic task resolution opportunity to an otherwise deterministic flow.

Two Levels of Fallback Support

  • Belief State Update:
    The agent asynchronously updates the conversation context for improved understanding without taking control.
    Ideal for customers who prefer to maintain deterministic control without enabling full autonomy.

  • Agent Takeover:
    The fallback agent temporarily assumes control to attempt task completion autonomously with an high-autonomy agent. .
    Ideal for flows with low success rates or where agentic reasoning can boost performance.

High Autonomy Task Agents

High Autonomy Task Agents are specialized autonomous agents designed to execute multi-step workflows, integrating perception, reasoning, and action within the contact center ecosystem.

High autonomy agents are characterized by the following:

  • Dynamic Planning & Execution: These agents autonomously plan and execute tasks in real-time without relying on pre-built reactive workflows.

  • Integration-Ready: They interact with CRMs, billing systems, and ticketing tools to automate complex, cross-system processes end-to-end. 

Agentic Task Agents interact with enterprise systems via explicitly defined APIs, using tools structured according to the MCP (Model Context Protocol) schema for standardized integration and execution. Webservice miniApps are used interchangeably as tools when given a description, but OCP supports the use of external MCP servers for increased flexibility and full customer control.

Characteristics

Faster issue resolution, improved automation ROI, and a foundation for fully autonomous customer service.

Target Use Cases:

  • Highly complex use cases where deterministic flows would fall short or take a long time and costly implementation to get ROI. Examples would be:

    • Hotel Reservations with multiple complex integration points (different amenities per hotel, per room, etc);

    • Use cases where additional reasoning on extracted data could provide valuable insights (such as, “where did I spend all my money last month”).

  • Customers that are already exposing their data through MCP and want an Agent to interact with their data and converse with their customers.

  • Quick-to-value deployment of agents that handle complex tasks, skipping the long hurdles of developing and deploying deterministic flows by compromising a certain level of control.

FAQ Agents

Lightweight agentic components specialized in retrieving, synthesizing, and delivering accurate answers based on existing documents or websites. They extend the Omilia Agentic Framework’s reasoning layer to provide instant, contextually grounded responses.

  • Retrieval-Augmented Understanding: The FAQ Agent leverages customer’s documentation, and Omilia’s RAG (Retrieval-Augmented Generation) layer to extract accurate and explainable responses from structured and unstructured sources.

  • Adaptive Answering: Rather than serving static FAQs, the agent dynamically composes personalized responses, taking into account conversation context, customer profile, and intent confidence.

  • Optimized for voice:
    Operates across voice and digital channels, but with latency optimized for voice.

Requires a Pathfinder Knowledge base. Supports both offline and online RAG for different levels of governance flexibility.

Current limitations of our FAQ agents:

  • Our knowledge base management is non-existent. We just upload documents and do retrieval on them with very little understanding and visibility over the data.

  • We currently do not support native integration with external Knowledge Bases for retrieval except through naive integration (Webservice miniApps)

Target Use Cases:

  • Ingest unstructured information (PDFs, Webpages other text documents) and add an agent to converse

For more information of how to create Agent read the corresponding guide in Orchestrator User Guide | Agentic Flow User Guide.