> ## 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.

# Core Objects

The main RogerIQ data model: organizations, projects, conversations, messages, contacts, companies, knowledge, widgets, forms, and beacons.

# Core Objects

RogerIQ is organized around a small set of durable objects. Understanding these makes the dashboard, API, widget, and integrations easier to reason about.

## Organization

An organization owns members, projects, API keys, usage, and account-level settings.

## Project

A project is the primary support workspace. Conversations, contacts, companies, knowledge, forms, beacons, widget configuration, integrations, analytics, and agent configuration are scoped to a project.

## Conversation

A conversation is a customer support thread. It has a status, priority, channel, assignee, tags, contact, and ordered messages.

Supported statuses include `open`, `pending`, `snoozed`, `resolved`, `closed`, `spam`, and `deleted`.

Supported channels include `email`, `chat`, `slack`, `discord`, `telegram`, `api`, `widget`, `form`, `phone`, `sms`, `whatsapp`, `facebook`, and `instagram`.

## Message

A message belongs to a conversation. The sender type is `customer`, `agent`, `ai`, or `system`. Messages can be public replies or internal notes.

## Contact and Company

Contacts represent people. Companies group related contacts and add account context. Contacts can carry email, name, phone, company, job title, external ID, and metadata.

## Knowledge Article

Knowledge articles can be manually authored, AI-generated, crawled from a site, imported from OpenAPI, or synced from HolyDocs. Published articles are indexed for search and AI citations.

## Widget

The widget is the customer-facing support surface. It can show docs search, AI answers, messaging, previous conversations, proactive messages, attachments, and customer identity.

## Form

A form is a schema-driven public intake surface. Submissions create conversations and preserve the submitted payload.

## Beacon

A beacon is a floating entry point linked to a form, optional docs site, and messaging configuration. It is useful for "contact us" experiences that do not require the full chat widget.