> ## Documentation Index > Fetch the complete documentation index at: https://docs.useboom.ai/llms.txt > Use this file to discover all available pages before exploring further. # Start here > What Boom is, and which part of this site is yours depending on what you do. Boom puts an AI agent in conversation with your customers over WhatsApp. One agent per organization, briefed once from your knowledge base, sent on whatever mission you need: winning back customers who left, answering support, onboarding someone who stalled, qualifying a lead, collecting a document, asking why people churn. The four ideas the rest of this site is built on: * **[The agent](/the-agent)** does the talking, in your voice, and hands off to a person when it should not handle something. * **[An initiative](/initiatives)** is one mission: who you reach and what the agent is trying to accomplish. * **[A journey](/journeys)** is the flow that carries a mission, the messages and waits and branches. * **[Extraction](/extraction)** turns each conversation into typed fields you can count and export, instead of transcripts nobody reads. If a customer writes to you first, no mission is needed. See [inbound conversations](/inbound). ## Which part of this site is yours **If you run the campaigns and not the code**, read this page and the five above it. They are prose, no code required, and they will tell you what Boom can do and what the words mean when someone on your team says "the segment hasn't been evaluated". The day to day work of creating and launching happens in the Boom app. This site documents the API underneath it. **If you are integrating Boom from your own systems**, start with the [API overview](/api-reference/overview), then the quickstart and authentication pages in that same tab. [One uniform surface](/one-surface) explains why every REST endpoint has an identically named MCP tool. **If you want an AI agent to operate Boom for you**, [connect over MCP](/use-mcp) and install the [skills](/skills). That is the fastest path from nothing to a running initiative, because the agent reads the same documentation you would and already knows the order of operations. ## Two things worth knowing before you plan around them WhatsApp is the conversational channel. Email is outbound only right now: a journey can send one, and there is no reply loop back to the agent. The dashboard, the API and MCP are not three copies of the same surface. A few things live only in the app, and this site says so where it matters: creating an email template, connecting a database, re-running extraction over conversations that already closed. ## Related What answers your customers, and how it improves from your corrections. One mission: audience, objective, and what it comes back with. Point Claude or Cursor at Boom and sign in. No API key. Every capability over REST, with the same names over MCP.