> ## Documentation Index > Fetch the complete documentation index at: https://www.plain.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # What is Plain? > Plain is a support platform for B2B teams, built API-first so you can change how it works rather than work around it. Plain is a support platform for B2B teams. Customer conversations arrive from email, Slack, Microsoft Teams, chat, Discord, or your own product, and become [threads](/docs/product/platform/threads/what-is-a-thread) in a single queue that your team and your AI agents both work from. It is built API-first. Everything the app can do, the [GraphQL API](/docs/graphql/introduction) can do, so you can automate a workflow, build a support portal inside your own product, or run your own agent against the same data your team uses. What is Plain ## Our mission Support is becoming more technical. AI is enabling companies to build anything themselves, and the speed of software change is accelerating faster than the tools teams use to support it. We believe the companies that win are the ones that treat support as infrastructure they build on top of, not a tool whose roadmap they don't control. Plain exists so that every B2B team can build support their way. ## What Plain does * **Channels.** Email, [Slack](/docs/product/channels/slack), [Microsoft Teams](/docs/product/channels/microsoft-teams), [chat](/docs/product/channels/chat), [Discord](/docs/product/channels/discord), and [contact forms](/docs/product/channels/contact-forms) all land in the same queue. You can also bring a channel Plain does not support yet with [custom channels](/docs/custom-channels). * **AI agents.** [Ari](/docs/product/agents/ari) replies to customers. [Sidekick](/docs/product/agents/sidekick) helps your team from inside Plain or Slack. You can also [bring your own agent](/docs/product/agents/bring-your-own-agent), which runs with the same identity and permissions as anyone else. * **The queue.** [Tiers and SLAs](/docs/product/platform/slas), [labels](/docs/product/platform/labels), [priorities](/docs/product/platform/threads/priorities), [assignment](/docs/product/platform/threads/assignment), [business hours](/docs/product/platform/business-hours), and [escalation paths](/docs/product/platform/escalation-paths) decide what your team sees first. * **Automation.** [Workflows](/docs/product/workflows) run on triggers and conditions, so triage, routing, and follow-ups happen without anyone watching the queue. * **Customer context.** [Companies](/docs/product/platform/companies), [tenants](/docs/product/platform/tenants), and [customer cards](/docs/product/platform/customer-cards) pull data from your own systems into the thread your team is reading. * **Self-serve.** A [Help Center](/docs/product/help-center) with a knowledge base, Ask AI, and a customer inbox. ## Who Plain is for Plain suits B2B teams whose support needs outgrow a fixed feature set: * **Technical teams** who want to build on an API rather than file feature requests. * **Fast-growing companies** whose volume and process change faster than a vendor ships. * **Teams adopting AI** who want to choose and swap agents rather than take whichever one is bundled. * **Support teams working with engineering**, where threads need to link to issues, incidents, and code. ## Where to start * Set up a channel, starting with [email](/docs/product/channels/email) or [Slack](/docs/product/channels/slack). * Read how [threads](/docs/product/platform/threads/what-is-a-thread) work, since everything else attaches to them. * If you are building against the API, start with the [data model](/docs/graphql/introduction).