# Agent Performance Console Overview

The Agent Performance Console is an AI agent monitoring and insights platform that answers the question every business leader is asking: "Are my AI agents actually delivering business outcomes?"

It's not a traditional analytics tool. It's a management platform designed to help you manage your AI agents the way you'd manage employees, with clear performance expectations, measurable objectives, and transparent accountability.

{% embed url="<https://vimeo.com/1171090864/829c578dad?fe=ci&fl=sv&share=copy>" %}

The Console Includes:

1. [An analytics dashboard](https://docs.satisfilabs.com/resource-center/ai-agent-engine/reporting-and-analytics/agent-performance-console/dashboard) that covers high-level AI Agent volume metrics and a summary view of each Agent’s OKR performance.
2. [Profile pages](https://docs.satisfilabs.com/resource-center/ai-agent-engine/reporting-and-analytics/agent-performance-console/agent-profiles) per AI Agent with a detailed view of OKR performance.
3. [AI Agent chats](https://docs.satisfilabs.com/resource-center/ai-agent-engine/reporting-and-analytics/agent-performance-console/agent-chat) are accessible from each profile page and can answer natural language data questions and provide qualitative insights and recommendations.
4. [Why we built the Console](https://agent.satis.fi/our-why). This section walks through the core concepts behind the Console, including key definitions, system architecture, and real-world agent examples. We highly recommend starting here to understand the purpose of the Console and how it’s designed to be used.

## Core Definitions

### Objectives & Key Results (OKRs)

OKRs (Objectives and Key Results) are a goal-setting framework that helps organizations define what they want to achieve (the Objective) and how they’ll measure success (the Key Results). The Objective is a clear, qualitative outcome, while Key Results are specific, measurable targets that prove progress toward that outcome. When applying OKRs to **AI Agents**, the **Objective** defines the business outcome the agent should drive (e.g., faster resolutions), and the **Key Results** quantify the agent’s performance and impact (e.g., accuracy, time saved, and successful task completion rate). They align teams around priorities, improve focus and accountability, and make it easier to track performance over a set time period.

<figure><img src="/files/jr9N3HT6RLCUwNr0rwje" alt=""><figcaption></figcaption></figure>

### Agents

Agents are digital staff members modeled after real-world operational roles (e.g., Ticketing Agent, Food & Beverage Manager, Guest Experience Host).

* Defined OKRs guide their responsibilities
* Success metrics and daily actions
* Enterprise system integrations

### Agent Campaigns

Agent Campaigns are structured, AI-driven missions assigned to individual agents that align behavior with strategic business outcomes.

* Campaign Identity & Duration
* Measurable Key Results
* Journey Workflows
* System Integrations & Analytics

### Journey Workflows

Journey Workflows are tactical playbooks nested within campaigns that define how customer interactions unfold.

* Triggers & Sequential Steps
* Multi-channel Execution
* Branching Logic & Upsells
* Agent CTAs

<figure><img src="/files/kaPJ1ZsQnf95vepzw6gf" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Fq9UQ4StYwlWLnQcJsZN" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.satisfilabs.com/resource-center/ai-agent-engine/ai-agent-engine-basics/agent-performance-console-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
