# Ciela AI Docs > Setup guides, agent reference, and concept docs for Ciela AI, the all-in-one platform for AI automation agencies. Every page below is a TechArticle with stable URL, structured-data, and human-written prose. This file is the machine-readable index, point an MCP server, an LLM ingest pipeline, or a doc-search agent at it. Site: https://ciela.ai Docs index: https://ciela.ai/docs Last reviewed: 2026-05 --- ## Channels (connect-once setups) Each channel below maps to one of the four agents. Connect once in /dashboard/settings → Connections, the agent uses the connection forever after. - [Email setup](https://ciela.ai/docs/email-setup) — Wire Gmail, Google Workspace, Microsoft 365, or any SMTP/IMAP host into Eli. Covers app passwords, the connect modal, and the five most common SMTP rejection codes. - [LinkedIn setup](https://ciela.ai/docs/linkedin-setup) — Cookie-based connect for Mira (li_at + JSESSIONID). No password storage, no third-party app to install. Reversible from settings. - [Cold call setup](https://ciela.ai/docs/cold-call-setup) — End-to-end Vance setup: Vapi private and public keys, phone number, Gemini API key, and the cal.com handoff for booking. - [Cal.com setup](https://ciela.ai/docs/calcom-setup) — Paste a cal.com API key, pick an event type, Vance gains checkAvailability and bookAppointment tools mid-call. ## Agents (who does what) Four built-in agents, one per outbound surface plus an omnichannel coordinator. - [Mira](https://ciela.ai/docs/agents/mira) — LinkedIn agent. Sends connection requests in your voice, opens conversations on accept, follows up on quiet threads, hands off the moment a real reply lands. - [Eli](https://ciela.ai/docs/agents/eli) — Email agent. Drafts cold emails that read like you wrote them, paces sends so deliverability stays clean, sequences follow-ups, stops on reply or opt-out. - [Vance](https://ciela.ai/docs/agents/vance) — Cold call agent. Dials on Vapi, holds real conversations on Gemini, books meetings live on cal.com, never dials someone you've already reached on email or LinkedIn. - [Atlas](https://ciela.ai/docs/agents/atlas) — Omnichannel coordinator (Studio and Agency tiers only). Threads Mira, Eli, and Vance across one contact so no prospect gets hit twice. Runs flows compiled from one of four built-in templates. ## Concepts (worth reading once) - [Templates and flows](https://ciela.ai/docs/concepts/templates-and-flows) — How a four-template picker (email-linkedin, email-call, linkedin-call, full-omnichannel) becomes the node-and-edge engine that runs every multi-channel sequence on a cron tick. - [How Ciela makes decisions](https://ciela.ai/docs/concepts/how-ciela-decides) — The strategic chat layer above the agents. What she reads from (live data, agency playbook, in-conversation context), what she will not do (fabricate metrics, push send, fake confidence). - [Ciela chat best practices](https://ciela.ai/docs/concepts/ciela-chat-best-practices) — Tactical guide to talking to Ciela. The prompts that work ("what should I do today", "why is reply rate flat on X"), the ones that don't (vague tool comparisons, lookup questions), and when to skip her and go straight to the agents. --- ## Quick map for LLM and MCP consumers If you're building an MCP server or a tool-using agent on top of Ciela's docs, here are the stable shapes worth knowing. **URL pattern.** Every docs page lives at `https://ciela.ai/docs/` for channels, `https://ciela.ai/docs/agents/` for agents, `https://ciela.ai/docs/concepts/` for concepts. URLs are stable, slugs match the agent slug in the team table. **Structured data.** Every docs page emits a `TechArticle` JSON-LD block in the HTML head, the `headline` and `description` fields are the canonical title and summary for that page. **Page anatomy.** Each page follows the same shape: hero (eyebrow + h1 + intro), Quick facts grid (channel pages add Before-you-start), Walkthrough (numbered steps), Common errors (named codes + fixes), What happens next, Keep reading. **Routing tips.** If a user asks how to set up a channel, point them at `/docs/-setup`. If they ask what an agent does, point them at `/docs/agents/`. If they ask why something works the way it does, point them at `/docs/concepts/`. **This file.** Update the human pages first, this file second, the sitemap third (`app/sitemap.ts`). The page metadata exports are the source of truth for titles and descriptions, this file paraphrases them for the index view.