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

# Introduction

What RogerIQ does, who it is for, and how the product is organized.

# RogerIQ Documentation

RogerIQ is an AI-native support platform for teams that want a focused help desk, a useful AI agent, and developer-friendly surfaces for widgets, forms, knowledge, and APIs.

The default product is intentionally centered on the workflows a normal support team uses every week: inbox, contacts, companies, knowledge, agent configuration, integrations, analytics, and settings. Advanced migration and governance tools exist, but they stay behind explicit advanced-mode entry points.

**[Quickstart](/quickstart)**

Create a project, connect a support channel, crawl knowledge, and install the widget.
  **[Install the widget](/widget/install)**

Add RogerIQ to a website with the hosted script and JavaScript API.
  **[CLI](/cli/install)**

`rogeriq` — manage tickets, projects, widget, integrations, and KB from your terminal or AI agent.
  **[SDK](/sdk/install)**

`@rogeriq/sdk` — official TypeScript client for Node, Workers, Deno, and browsers.
  **[Use the API](/api/overview)**

Work with conversations, messages, contacts, KB, agent, widget, integrations, and webhooks.
  **[MCP server](/cli/mcp)**

`rogeriq mcp` exposes the API as MCP tools for Claude Desktop / Claude Code.
  **[Sync HolyDocs](/knowledge/holydocs-integration)**

Push docs into RogerIQ knowledge and receive doc-gap feedback.
  **[Webhooks](/api/webhooks)**

Event subscriptions with HMAC signing, inline + long-tail retries, and a test endpoint.

## Product Areas

| Area | What it handles |
| --- | --- |
| Inbox | Conversations from email, widget chat, forms, API, Slack, Discord, Telegram, and other channels. |
| Contacts and companies | Customer identity, conversation history, metadata, company relationships, and memory. |
| Knowledge | Manual articles, crawled sites, hosted docs, OpenAPI ingestion, and HolyDocs sync. |
| Agent | Autopilot, Copilot, and Assist modes with test runs, guardrails, citations, and improvements. |
| Widget | Embeddable chat, docs search, AI answers, previous messages, proactive messages, and identity. |
| Forms and beacons | Hosted forms, iframe embeds, HTML POST, JSON submit, file uploads, and floating contact beacons. |
| API | API-key access for public developer workflows and cookie-authenticated dashboard APIs for the app. |

## How to Read These Docs

If you are setting up a team, start with [Quickstart](/quickstart), then [Onboarding](/setup/onboarding) and [Email channel](/setup/email-channel).

If you are adding RogerIQ to a product, start with [Widget install](/widget/install), [Identify and secure mode](/widget/identify-secure-mode), and [Forms](/forms/overview).

If you are building an integration, start with [API overview](/api/overview), [Authentication](/api/authentication), and [Webhooks](/api/webhooks). Prefer typed code? Use [`@rogeriq/sdk`](/sdk/quickstart). Prefer the terminal? Use the [`rogeriq` CLI](/cli/install).

If you are wiring an AI agent (Claude, Cursor, custom), use the [MCP server](/cli/mcp) or the [agent guide](/cli/agents) for shell-based agents.

RogerIQ uses `projectId` for almost every runtime and API surface. Keep the project ID available when installing the widget, calling the API, connecting integrations, or syncing knowledge.