# Getting Started
URL: /getting-started
Type: tutorial
Description: Set up a new Stylo workspace end-to-end so your agents see AI-drafted reply suggestions in their helpdesk.
Keywords: getting started, setup, onboarding, first run, rollout, assist, first workflow
By the end of this tutorial, an agent who opens a ticket sees a reply already drafted for them in the Stylo sidebar. Getting there takes four things: your helpdesk connected, your brand voice set, your knowledge connected, and one Response Workflow that drafts replies. It takes about 20 minutes.

<Callout type="info">
  **Before you start**, you need an **admin** role in Stylo and the ability to
  connect your helpdesk (Zendesk).
</Callout>

<Mermaid
  chart="flowchart LR
  A([New workspace]) --> B[1 Connect your helpdesk]
  B --> C[2 Set your brand voice]
  C --> D[3 Connect knowledge]
  D --> E[4 Create a Response Workflow]
  E --> F([Agents get drafted<br/>replies on tickets])"
/>

Set up your workspace [#set-up-your-workspace]

<Steps>
  <Step>
    Connect your helpdesk [#connect-your-helpdesk]

    Stylo reads and replies to tickets through your helpdesk, so connect it first.

    1. Go to **Integrations**.
    2. Find **Zendesk** and start the connection. You'll sign in to Zendesk and authorize Stylo.
    3. When you return, Zendesk shows a **Connected** status.

    **You're done when:** Zendesk appears with a **Connected** status on the Integrations page.

    <Callout type="info">
      See [Integrations](/integrations) for the full list of tools you can connect.
    </Callout>
  </Step>

  <Step>
    Set your brand voice [#set-your-brand-voice]

    Tell Stylo how your team sounds, so the very first draft already reads like you. Open **Tone & Instructions** and set, at a minimum:

    * **Tone of voice** — friendly, balanced, professional, or matter-of-fact
    * **Response length** — concise, balanced, or detailed
    * **Company name** and **industry**, for context

    **You're done when:** your tone is saved. Every reply Stylo drafts from now on follows it.

    See [Brand Settings](/brand-settings) for every option and what it changes.
  </Step>

  <Step>
    Connect knowledge [#connect-knowledge]

    Give Stylo the content it should answer from — your help center, docs, or uploaded files — so replies cite your real policies instead of guesses.

    1. Open **Knowledge**.
    2. Connect a documentation source, or upload files.

    **You're done when:** your first knowledge base appears and finishes syncing.

    <Callout type="info">
      No knowledge yet? You can still continue and add it later — but connect it
      before you trust drafts on policy questions like refunds or shipping.
    </Callout>

    See [Knowledge Base](/knowledge-base) and [Knowledge sync and documents](/knowledge-sync-and-documents).
  </Step>

  <Step>
    Create a Response Workflow [#create-a-response-workflow]

    This is the step that puts a draft in front of your agents. A [Response Workflow](/response-workflows) writes a contextual reply for a ticket; set it to draft into the sidebar and your agents review and send with one click.

    1. Go to **Response Workflows** and select **New workflow**. Stylo opens the editor.
    2. Give it a clear **name** and fill in &#x2A;*Use this when…** — describe, in plain language, the tickets it should handle (for example, "the customer asks where their order is"). Stylo uses this to match the workflow to incoming tickets.
    3. Write the **response template** — what the reply should say.
    4. Set the workflow to **draft suggestions into the agent sidebar** for review, rather than send on its own.
    5. Choose what triggers a draft — for example, **when a customer replies**.
    6. **Enable** the workflow. New workflows start off, so this last step is what makes it run.

    **You're done when:** the workflow is enabled and set to draft into the sidebar.

    <Callout type="info">
      Start with one narrow, predictable request rather than every support process at
      once. See [Creating a workflow](/response-workflows/creating-a-workflow) for the
      full walkthrough and [Response modes](/response-workflows/response-modes) for the
      difference between template and guided drafting.
    </Callout>
  </Step>

  <Step>
    See it working [#see-it-working]

    Open a real ticket that matches your &#x2A;*Use this when…** description. Stylo's sidebar shows a drafted reply your agent can review, edit, and send.

    As drafts add up, your Home page starts reporting how often agents accept them — your first signal of whether the workflow is pulling its weight.

    **You're done when:** a draft appears on a matching ticket.
  </Step>
</Steps>

Where to go from here [#where-to-go-from-here]

Your Home page doubles as a live health check once you're running — it surfaces pending approvals, failed runs, and knowledge bases with sync errors, so it's worth a glance each day.

When a workflow consistently produces replies your agents send unchanged, you can let it send on its own. Move there deliberately, one workflow at a time — see [Progressive Automation](/response-workflows/progressive-automation).

Next steps [#next-steps]

<Cards>
  <Card title="Creating a workflow" href="/response-workflows/creating-a-workflow" description="Build your first Response Workflow step by step." />

  <Card title="Integrations" href="/integrations" description="Connect the tools Stylo pulls data from and acts on." />

  <Card title="Brand Settings" href="/brand-settings" description="Define voice, tone, and rules for AI output." />

  <Card title="Knowledge Base" href="/knowledge-base" description="Ground AI responses in your own content." />

  <Card title="Progressive Automation" href="/response-workflows/progressive-automation" description="Let proven workflows send on their own, safely." />

  <Card title="Troubleshooting" href="/troubleshooting" description="Diagnose sync errors, failed runs, and connection issues." />
</Cards>