# Doors overview

> The six doors a customer can walk through — phone, website chat, WhatsApp, Instagram, Messenger, SMS — all answered by the same brain, all landing in the same CRM.

A **door** is a channel customers come through. Each door is a service you add to a business; each has an AI agent answering on it; and everything that comes through any door lands in the same place — a contact, a conversation log, a deal on the board.

| Door | What it is | Setup effort |
| --- | --- | --- |
| [Website chat](/docs/doors/website-chat) | The chat bubble on your site, answering from your knowledge | One script tag |
| [AI receptionist](/docs/doors/ai-receptionist) | A real phone number the AI answers — books, quotes, transfers, takes messages | Buy a number, set the greeting |
| [WhatsApp](/docs/doors/whatsapp) | The same brain on the world's biggest messaging app, templates + 24-hour sessions | Connect a WhatsApp number |
| [Instagram & Messenger](/docs/doors/instagram-messenger) | DMs and story replies answered in seconds | Connect the Meta pages |
| [SMS](/docs/doors/sms) | Two-way texting on your business number | One-time A2P registration |

## One brain, many doors

The doors share the business's [knowledge](/docs/ai/knowledge) and [contacts](/docs/crm/contacts) — a customer who DMs on Instagram and later calls is the *same person* with the same history. What the doors do **not** share is conversation flows: [workflows are siloed per door](/docs/workflows/overview), because the right script for a phone call is not the right script for a DM.

> **WHICH DOOR FIRST?:** The phone. Nothing else recovers revenue as fast as the missed-call redirect — see the [AI receptionist](/docs/doors/ai-receptionist) deployment patterns. Website chat is second: one script tag and it's live.

## What every door produces

- A **conversation** with the full transcript, visible per channel in the service's logs.
- A **contact** — created or matched (phone → email → external ID), never duplicated.
- A **lead / deal** when the conversation warrants it — captured by the AI's lead tool, a form, or a workflow — with [first-touch attribution](/docs/crm/attribution).
- **Trigger events** for [workflows](/docs/workflows/triggers): lead captured, call missed, voicemail left, call ended.
- A **ticket** when a human needs to take over — see [Help desk](/docs/helpdesk/overview).