# Stylo Documentation
URL: /
Type: concept
Description: Learn how to roll out Stylo, configure grounded AI responses, and scale toward safe automation.
Keywords: overview, introduction, stylo, docs home
<div className="docs-hero">
  <div className="docs-eyebrow">
    Customer Support AI Docs
  </div>

  <div className="docs-lead">
    Stylo helps support teams answer faster with grounded AI, reusable workflows, and a controlled rollout path from agent assist to automation. Use these docs to set up your workspace, connect the systems your team relies on, and define how Stylo should respond.
  </div>
</div>

{/* TODO(docs): Screenshot of the docs home page highlighting the setup path for new admins. Tracked in public/images/README.md. */}

Start with setup [#start-with-setup]

If you are setting up Stylo for a new workspace, start here:

1. [Getting Started](/getting-started) to understand the initial rollout path
2. [Integrations](/integrations) to review connected systems and add the ones your workflows need
3. [Knowledge Base](/knowledge-base) to connect help center content, docs, or uploaded files
4. [Brand Settings](/brand-settings) to define tone, voice, and response rules
5. [Response Workflows](/response-workflows) to standardize repeated support work

This setup path matches the onboarding checklist inside the Stylo workspace. It is the fastest way to move from initial configuration to a useful live workflow.

<div className="docs-grid">
  <div className="docs-card">
    <h3>
      <a href="/getting-started">
        Getting Started
      </a>
    </h3>

    <p>
      Follow the first-run path for a new workspace and understand what to
      configure first.
    </p>
  </div>
</div>

Choose the right path [#choose-the-right-path]

<div className="docs-grid">
  <div className="docs-card">
    <h3>
      <a href="/workspace-overview">
        Workspace Overview
      </a>
    </h3>

    <p>
      Learn where admins and agents work in Stylo and what each area of the
      product is for.
    </p>
  </div>

  <div className="docs-card">
    <h3>
      <a href="/assist">
        Assist
      </a>
    </h3>

    <p>
      See how agents review drafts, adjust responses, and work with grounded
      suggestions.
    </p>
  </div>

  <div className="docs-card">
    <h3>
      <a href="/knowledge-base">
        Knowledge Base
      </a>
    </h3>

    <p>
      Improve answer quality by connecting reliable content and keeping it up to
      date.
    </p>
  </div>

  <div className="docs-card">
    <h3>
      <a href="/response-workflows">
        Response Workflows
      </a>
    </h3>

    <p>
      Build repeatable response logic with instructions, conditions, guardrails,
      and actions.
    </p>
  </div>
</div>

Who these docs are for [#who-these-docs-are-for]

* Admins and operators who set up integrations, knowledge, brand guidance, and workflows
* Support leaders who want a safer rollout path from assist to more automation
* Agents who need to understand how Stylo drafts responses and when manual review still matters

What you can do in Stylo [#what-you-can-do-in-stylo]

* Connect the external systems your team uses in support operations
* Ground AI responses in your help center, internal docs, and uploaded files
* Define brand rules so responses match your team’s tone and constraints
* Build workflows for repeated ticket patterns
* Review results before you expand automation further

Related [#related]

* [Members and Access](/members-and-access) to invite teammates and manage workspace access
* [Managed APIs](/managed-apis) to connect API-backed tools used in workflows
* [MCP Servers](/mcp-servers) to configure MCP-based integrations
* [Query Mapping](/query-mapping) to improve retrieval using real support conversations

LLM access [#llm-access]

<div className="docs-callout">
  Machine-readable exports are available at <a href="/llms.txt">/llms.txt</a>{" "}
  and <a href="/llms-full.txt">/llms-full.txt</a>. These are intended for
  crawlers, retrieval systems, and other AI tooling that need a cleaner
  representation of the docs.
</div>