---
title: "Operator: A look under the hood"
description: "Operator is a customer-operations Agent built to help teams understand, manage, and improve customer experience across workspaces. The post distinguishes a production Agent from a prototype that simply gives an LLM API access and a system prompt, describing more than 50 purpose-built tools and 10 skills for data retrieval, reporting, investigation, and operational tasks. Its intelligence layer combines semantic search tuned against millions of support conversations, workspace-specific attribute awareness, and encoded reasoning, while the action layer supports configuration and content changes through reviewable diffs requiring explicit approval. A hybrid conversational and graphical interface presents charts, dashboards, and structured proposals within the existing platform. The post argues that read-only custom tools can be built in weeks, but production reliability, safe actions, multi-tenant isolation, graceful degradation, and ongoing maintenance require substantially greater investment."
---

# Operator: A look under the hood

[Intercom](https://yomu.fyi/company/intercom) · Jack Ryan · May 15, 2026

**Type:** Explainer

## Summary

Operator is a customer-operations Agent built to help teams understand, manage, and improve customer experience across workspaces. The post distinguishes a production Agent from a prototype that simply gives an LLM API access and a system prompt, describing more than 50 purpose-built tools and 10 skills for data retrieval, reporting, investigation, and operational tasks. Its intelligence layer combines semantic search tuned against millions of support conversations, workspace-specific attribute awareness, and encoded reasoning, while the action layer supports configuration and content changes through reviewable diffs requiring explicit approval. A hybrid conversational and graphical interface presents charts, dashboards, and structured proposals within the existing platform. The post argues that read-only custom tools can be built in weeks, but production reliability, safe actions, multi-tenant isolation, graceful degradation, and ongoing maintenance require substantially greater investment.

## Context

A prototype that gives a foundation model API access, support data, and a system prompt can demonstrate basic querying and reporting, but it obscures the engineering required for a production Agent operating across thousands of workspaces with different configurations, data models, usage patterns, and edge cases.

## Approach / What changed

Operator uses more than 50 purpose-built tools and 10 skills, semantic search, workspace-specific attribute awareness, encoded reasoning, and a proposal system for safe actions. It combines conversational interaction with graphical components such as charts, dashboards, and reviewable diffs, and operates within the existing platform.

## Takeaways

- Operator’s tools encode decisions about which data to fetch, how to structure it, what context to include, and what to omit; its skills chain multiple tools into tasks such as debugging conversations and updating help-center content.
- Actions including publishing help articles, configuring connectors, and modifying Fin configuration are presented as reviewable diffs, and nothing goes live without explicit approval.
- The post estimates that a useful read-only custom tool can be built in weeks, while production reliability, security, data isolation, graceful degradation, and ongoing maintenance make a full system a quarters-long effort.

**Tags:** [AI Agents](https://yomu.fyi/topic/ai-agents), [Architecture](https://yomu.fyi/topic/architecture), [Reliability](https://yomu.fyi/topic/reliability), [Search](https://yomu.fyi/topic/search)

- Source: [Intercom](https://www.intercom.com/blog/operator-a-look-under-the-hood)
- Source URL: https://www.intercom.com/blog/operator-a-look-under-the-hood
- Ingested by Yomu: 2026-09-09T08:20:41.509Z

[Read original post](https://www.intercom.com/blog/operator-a-look-under-the-hood)