> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Go live

> Pre-launch checks for a new Ravenna workspace, how to announce it to your team, and the five signals worth watching in the first week.

export const Checkbox = ({items = []}) => {
  const [checked, setChecked] = useState(Array(items.length).fill(false));
  const toggle = index => {
    setChecked(prev => {
      const copy = [...prev];
      copy[index] = !copy[index];
      return copy;
    });
  };
  return <div className="custom-checkbox-list">
      {items.map((text, index) => <div key={index} className="custom-checkbox-item flex items-center mb-2">
          <input type="checkbox" checked={checked[index]} onChange={() => toggle(index)} className="mr-2" />
          <span>{text}</span>
        </div>)}
    </div>;
};

Everything is built. This step is about opening it to real people and knowing where to look when they start using it.

**Time:** about 20 minutes, plus a week of light attention.

## Pre-launch checks

Walk these as an ordinary employee, not as an admin. Use a second Slack account or a colleague who has not seen the setup.

<Checkbox
  items={[
"Send a plain message in your request channel and confirm a ticket is created with a mirror in the thread",
"Confirm the mirror also appears in the triage channel with responder actions",
"Ask the agent a question you know is documented, and check it cites the right source",
"Ask it something deliberately undocumented, and check it escalates the way your instructions say",
"Submit your form end to end and confirm the workflow ran, in the workflow's run history",
"Resolve a ticket and confirm the CSAT prompt arrives",
"Confirm private notes are invisible to the requester",
"Check that every responder who needs access is a member of the workspace"
]}
/>

Two things worth checking specifically because they are quiet failures:

* **The workflow is published, not draft.** Drafts never fire, and nothing tells you at submission time.
* **Knowledge folders are scoped to the channel you launched.** A folder restricted to a different channel simply returns nothing, which reads as an agent that does not know anything.

## Announce it

Say three things: where to ask, what the AI will do, and what happens when it cannot help. Skip the feature tour.

Ravenna ships announcement copy and employee handbooks you can paste into Slack and adapt.

<CardGroup cols={2}>
  <Card title="Announcement templates" icon="megaphone" href="/guides/user-onboarding/announcements" horizontal>
    Launch-day Slack copy in several tones.
  </Card>

  <Card title="Employee handbook" icon="book" href="/guides/user-onboarding/handbook/simple-edition" horizontal>
    A short explainer to share with the whole company.
  </Card>
</CardGroup>

<Tip>
  Pin the announcement in the request channel and set the channel topic to point at it. New joiners find the topic long after the message has scrolled away.
</Tip>

Make it easier to reach from outside Slack too. Deep links let you drop Ravenna into an Okta dashboard, an intranet page, or an email footer.

<Callout icon="link" color="#6B7280">Learn more about [deep linking](/guides/best-practices/driving-adoption/deep-linking)</Callout>

## What to watch in week one

Five signals, in the order they tell you something.

<AccordionGroup>
  <Accordion title="Agent chat logs" defaultOpen>
    The highest-value screen in your first week. Every conversation, the result the agent assigned itself, and any thumbs up or down.

    Read twenty conversations by hand. You will learn more from that than from any dashboard, and you will usually find one missing rule and one badly worded form field.

    <Callout icon="link" color="#6B7280">Learn more about [chat logs](/documentation/automate/agents/deploy-monitor#chat-logs)</Callout>
  </Accordion>

  <Accordion title="Knowledge gaps">
    Questions the agent could not answer, clustered by topic and ranked by severity. This is your documentation backlog, written by your employees.

    <Callout icon="link" color="#6B7280">Learn more about [closing knowledge gaps](/guides/how-to/close-knowledge-gaps)</Callout>
  </Accordion>

  <Accordion title="Unassigned tickets">
    Build a view filtered to unassigned and not resolved, and keep it open. In week one the failure mode is not a bad answer, it is a request nobody noticed.

    <Callout icon="link" color="#6B7280">Learn more about [views](/documentation/tickets/organize/views)</Callout>
  </Accordion>

  <Accordion title="CSAT">
    Low scores are useful, but the comments are more useful. They tell you whether people are unhappy with the answer or with how long it took, which point at completely different fixes.

    <Callout icon="link" color="#6B7280">Learn more about [CSAT](/documentation/measure/csat)</Callout>
  </Accordion>

  <Accordion title="AI Outcome">
    Ravenna classifies every closed ticket an agent touched as **Resolved**, **Assisted**, **Escalated**, or **Not Applicable**. It is the honest measure of how much the AI is actually carrying.

    Do not judge it in week one. Get a baseline, then watch it move as you close knowledge gaps and tighten rules.

    <Callout icon="link" color="#6B7280">Learn more about [analytics dashboards](/documentation/measure/analytics#prepackaged-dashboards)</Callout>
  </Accordion>
</AccordionGroup>

<Tip>
  Schedule an [AI brief](/documentation/measure/ai-briefs) to your triage channel so the weekly summary arrives without anyone remembering to look.
</Tip>

## Where to go from here

Day one covered one team and one desk. The next moves depend on what your week-one signals showed.

<CardGroup cols={2}>
  <Card title="Answers are thin" icon="book-open" href="/guides/how-to/close-knowledge-gaps" horizontal>
    Work the knowledge gaps list.
  </Card>

  <Card title="Too many manual approvals" icon="check-check" href="/guides/playbooks/approval-flows" horizontal>
    Move them into approval templates.
  </Card>

  <Card title="People outside Slack are stuck" icon="globe" href="/guides/playbooks/launch-the-portal" horizontal>
    Launch the Portal.
  </Card>

  <Card title="No agreed response times" icon="timer" href="/guides/playbooks/slas-and-business-hours" horizontal>
    Set SLAs against your business hours.
  </Card>

  <Card title="Ready for the next team" icon="book-open" href="/guides/playbooks/overview" horizontal>
    Pick a department playbook and stand up desk two.
  </Card>

  <Card title="Rolling out company-wide" icon="calendar-check" href="/guides/resources/rollout-checklist" horizontal>
    Follow the week-by-week plan.
  </Card>
</CardGroup>


## Related topics

- [Set up an AI agent](/guides/day-one/set-up-agent.md)
- [Available tools](/documentation/automate/mcp/tools.md)
- [Email support](/guides/playbooks/email-support.md)
- [Workflow builder](/documentation/automate/workflows/workflow-builder.md)
- [Day one](/guides/day-one/overview.md)