> ## Documentation Index
> Fetch the complete documentation index at: https://docs.haloagents.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Halo is an AI-native customer support platform that knows your product, your customers, and what's happening for them right now.

## What Halo is

Halo is a customer support platform built around AI agents that actually understand your business. Instead of a generic chatbot bolted onto a knowledge base, Halo connects three things:

* **Your knowledge** — your docs, help articles, internal SOPs, and synced data from HubSpot, Zoom, Fathom, PandaDoc, Slack, and more.
* **Your customers** — every contact, company, plan, integration status, usage metric, and custom trait you push into Halo.
* **Your operations** — an inbox for human agents, Outreach for proactive messaging, a help center for self-service, and integrations that let agents create deals, file bug tickets, and request billing changes on their own.

When a user asks a question, the AI sees who they are, what they've configured, what's broken right now, and what's documented. That's why answers come back specific instead of generic.

## What you'll set up

A typical Halo workspace has five things working together:

<CardGroup cols={2}>
  <Card title="AI Agents" icon="bot" href="/agents/overview">
    Configurable personas that handle chat, email, Slack, and Live Help. Each agent has its own instructions, skills, channels, and escalation rules.
  </Card>

  <Card title="Channels" icon="message-square" href="/channels/email-overview">
    Where your customers reach you: the embedded web widget, your support email address, Slack workspaces, and your help center.
  </Card>

  <Card title="Knowledge" icon="book-open" href="/knowledge/overview">
    What the agent knows: crawled docs, uploaded files, internal articles, and distilled insights from connected tools.
  </Card>

  <Card title="Inbox" icon="inbox" href="/inbox/overview">
    The shared inbox where your team handles tickets, jumps into live conversations, and replies via chat or email.
  </Card>
</CardGroup>

The fifth thing is **context** — the structured data your app pushes via the SDK and REST API so the AI knows things like "this user's HubSpot sync is broken" or "this company is on the Pro plan with 3 seats remaining." Context is what turns a good support tool into one that resolves issues instead of asking clarifying questions.

## How a question flows through Halo

When a user types a message into the widget (or sends an email, or pings your support channel in Slack):

<Steps>
  <Step title="The agent loads context">
    Halo loads the user's traits, company, and any context entries you've sent — plus any data synced from connected integrations like Stripe and HubSpot.
  </Step>

  <Step title="The agent searches knowledge">
    The agent searches your knowledge base (docs, files, help center articles, distilled meeting transcripts) for relevant content using semantic search.
  </Step>

  <Step title="The agent reasons and acts">
    The agent uses its instructions, skills, and connected tools — it can highlight UI elements, create tickets, file Linear bugs, request a refund, log an activity in HubSpot, or just answer.
  </Step>

  <Step title="Escalation if needed">
    If confidence is low or the user explicitly asks for a human, the agent escalates by creating a ticket in your inbox (with priority, segment-based routing, and the full conversation attached).
  </Step>
</Steps>

## Where to start

If this is your first time in Halo, follow the in-app **Setup** wizard — it walks you through company info, knowledge sources, your first agent, widget install, and team invites. Then come back here for deeper guides.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    Install the widget and get your first AI conversation in under 5 minutes.
  </Card>

  <Card title="How Halo Works" icon="diagram-project" href="/getting-started/how-it-works">
    The full architecture — agents, channels, knowledge, context, escalation, and how they fit together.
  </Card>

  <Card title="Setup Checklist" icon="list-check" href="/getting-started/setup-checklist">
    The full setup journey: knowledge, agents, channels, integrations, team, and going live.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/overview">
    The REST API for chat, tickets, identifying users, sending events, and managing series enrollment.
  </Card>
</CardGroup>