> ## 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.

# User handbook

> A clean, professional end-user handbook explaining how to submit requests, track tickets, handle approvals, and rate resolutions in Ravenna.

export const ArcadeEmbed = ({code, title = 'Demo', aspect = 56.25}) => {
  const arcadeIframeRef = useRef(null);
  useEffect(() => {
    function onArcadeIframeMessage(e) {
      if (e.origin !== 'https://demo.arcade.software' || !e.isTrusted) return;
      const arcadeIframe = arcadeIframeRef.current;
      if (!arcadeIframe || !arcadeIframe.contentWindow) return;
      if (e.data.event === 'arcade-init') {
        arcadeIframe.contentWindow.postMessage({
          event: 'register-popout-handler'
        }, '*');
      }
      if (e.data.event === 'arcade-popout-open') {
        arcadeIframe.style['position'] = 'fixed';
        arcadeIframe.style['z-index'] = '9999999';
      }
      if (e.data.event === 'arcade-popout-close') {
        arcadeIframe.style['position'] = 'absolute';
        arcadeIframe.style['z-index'] = 'auto';
      }
    }
    window.addEventListener('message', onArcadeIframeMessage);
    const arcadeIframe = arcadeIframeRef.current;
    if (arcadeIframe && arcadeIframe.contentWindow) {
      arcadeIframe.contentWindow.postMessage({
        event: 'register-popout-handler'
      }, '*');
    }
    return () => {
      if (arcadeIframe && arcadeIframe.contentWindow) {
        arcadeIframe.contentWindow.postMessage({
          event: 'unregister-popout-handler'
        }, '*');
      }
      window.removeEventListener('message', onArcadeIframeMessage);
    };
  }, []);
  const embedUrl = `https://demo.arcade.software/${code}?embed&embed_mobile=tab&embed_desktop=inline`;
  return <div style={{
    position: 'relative',
    paddingBottom: `calc(${aspect}% + 41px)`,
    height: 0,
    width: '100%'
  }}>
      <iframe ref={arcadeIframeRef} src={embedUrl} title={title} frameBorder="0" loading="lazy" allowFullScreen allow="clipboard-write" style={{
    position: 'absolute',
    top: 0,
    left: 0,
    width: '100%',
    height: '100%',
    colorScheme: 'light'
  }} />
    </div>;
};

<Info icon="copy">
  **This is a template you hand to your employees.** Copy it, swap in your channel names, your Portal link, and your support email address, and cut the entry points you have not turned on. The [Notion versions](/guides/user-onboarding/handbook/notion) are the fastest way to do that.
</Info>

## What is Ravenna?

Ravenna is your organization's service desk. It runs where you already work: Slack, Microsoft Teams, a web portal, and email. You submit a request, an AI assistant tries to answer it immediately, and if it needs a person, it becomes a tracked ticket you can follow.

What that gets you:

* Submit a request without leaving Slack, or from a browser if you prefer
* Get an instant answer from your company's own knowledge when one exists
* Track everything you have filed in one place, wherever you filed it
* Approve requests from the same place you read messages

<Info>
  **On Microsoft Teams rather than Slack?** Post in your connected Teams channel, or `@`-mention **Ravenna**, and the assistant picks it up. Two differences: private chats with the Ravenna bot are not available yet, so use the channel, and Teams does not send satisfaction surveys. Approvals do arrive in your Teams chat.
</Info>

### Types of requests you can submit

<CardGroup cols={2}>
  <Card title="IT support" icon="laptop">
    Software access, equipment requests, troubleshooting, and password resets
  </Card>

  <Card title="HR assistance" icon="users">
    Onboarding questions, policy clarification, benefits, and form requests
  </Card>

  <Card title="Facilities" icon="building">
    Office supplies, desk assignments, maintenance requests, and workspace needs
  </Card>

  <Card title="Operations" icon="gear">
    Process questions, vendor requests, compliance support, and procedural guidance
  </Card>
</CardGroup>

Which teams and forms you see depends on how your organization set Ravenna up. If you are not sure where something belongs, ask Ravenna and it will point you at the right team.

***

## How to submit requests

Four front doors, all producing the same tracked ticket. Pick whichever is closest to hand.

<CardGroup cols={2}>
  <Card title="Ravenna Slack app" icon="slack" href="#ravenna-slack-app">
    Message Ravenna directly, or open its app home
  </Card>

  <Card title="Public support channels" icon="comments" href="#public-support-channels">
    Post in a shared team channel
  </Card>

  <Card title="The portal" icon="globe" href="#the-portal">
    A web page for forms and for tracking requests
  </Card>

  <Card title="Email" icon="mail" href="#email">
    Email the address you already use
  </Card>
</CardGroup>

***

### Ravenna Slack app

1. Look for **Ravenna** in your Slack sidebar. Slack groups AI apps under **Agents**, so check there first, then **Apps**
2. Click to open it. The **Home** tab is your dashboard
3. Use the **Messages** tab to chat with the assistant like any other direct message

<Tip>
  You can also add Ravenna to the agent picker in the top right of Slack, which keeps it within reach from anywhere.
</Tip>

#### App overview

<Card>
  <ArcadeEmbed code="AhBk77T1g1Czm2wIOtZr" title="How to use Ravenna Slack app" />

  <Tabs>
    <Tab title="Home tab">
      Your dashboard: the teams you can file with, your open tickets, and anything waiting on your approval.
    </Tab>

    <Tab title="Messages tab">
      Chat with Ravenna's AI assistant like any other direct message. Each conversation lives in its own thread, so you can scroll back to past requests and reply in a thread to continue one.
    </Tab>
  </Tabs>
</Card>

#### Creating requests

<Tabs>
  <Tab title="Home tab">
    **Structured request.** Fill in a form when you already know what you need.

    <Steps>
      <Step title="Click Create a new ticket">
        Open the Ravenna app home tab and click the **Create a new ticket** button.
      </Step>

      <Step title="Select a workspace">
        Choose the team or department that owns your request.
      </Step>

      <Step title="Choose a form">
        Pick the form that matches your need.
      </Step>

      <Step title="Fill in the details">
        Describe what you need clearly. Specifics get you resolved faster.
      </Step>

      <Step title="Submit">
        Your ticket is created and updates arrive in a dedicated thread.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Messages tab">
    **Conversational.** Describe the problem and let the assistant work out where it goes.

    <Steps>
      <Step title="Open the Messages tab">
        Head to the Messages tab in the Ravenna Slack app, like opening a direct message.
      </Step>

      <Step title="Describe what you need">
        Plain language is fine. You do not need to know which team owns it.
      </Step>

      <Step title="Send your message">
        The assistant either answers from your company's knowledge or helps you open a ticket. Replies arrive in a thread on your message.
      </Step>

      <Step title="Track progress">
        Updates appear in the conversation thread, and in the **Home** tab.
      </Step>
    </Steps>

    <Note>
      Some teams have the assistant collect form details through conversation instead of showing you a form. If it asks you one question at a time and then shows you a filled-in form to confirm, that is why. Longer forms and private forms always open as a form.
    </Note>
  </Tab>
</Tabs>

***

### Public support channels

Posting where everyone can see the answer means the next person with your question finds it instead of asking again, and Ravenna learns from the thread.

#### Finding your support channels

Look for channels like these in Slack:

* `#ask-it` for IT requests
* `#ask-hr` for HR questions
* `#facilities` for office requests
* `#support` for general questions

Not sure which ones exist? Ask Ravenna in the **Messages** tab for a list of active support channels.

You can always file privately through the Ravenna Slack app instead, even when a public channel is available.

#### Submitting requests in channels

<AccordionGroup>
  <Accordion title="Post your question" icon="message-square">
    Type your request in the channel with enough detail for someone to act on it.
  </Accordion>

  <Accordion title="Watch for confirmation" icon="ticket">
    Ravenna acknowledges the request, usually with a 🎫 emoji reaction or a threaded reply. The exact format depends on how your organization configured it.
  </Accordion>

  <Accordion title="Follow the thread" icon="messages-square">
    All the back and forth happens in the message thread. The ticket also appears in the **Home** tab of the Ravenna app.
  </Accordion>
</AccordionGroup>

***

### The portal

The portal is a web page where you can file a request, ask a question, and see everything you have submitted. Your company will share the link.

<Steps>
  <Step title="Open the portal link">
    Sign in with your usual company account. There is no separate password.
  </Step>

  <Step title="Pick a request type">
    Choose from the featured options, or search the full list.
  </Step>

  <Step title="Or just ask">
    The portal has a chat box, and the assistant answers from your company's knowledge before it creates a ticket.
  </Step>

  <Step title="Track everything">
    **My requests** shows every ticket you have filed, including the ones you opened in Slack or by email.
  </Step>
</Steps>

<Tip>
  **Updates arrive by email.** The portal does not have its own notification inbox, so watch your inbox for replies on requests you filed there.
</Tip>

***

### Email

Email your team's usual address, write your request the way you normally would, and send. No special formatting, no subject line conventions.

Ravenna organizes and tracks the request behind the scenes, and replies come back to you by email as usual. The ticket also shows up in the Ravenna Slack app, so your history is in one place either way.

***

## Rating a resolution

When your ticket is marked done, you may get a short 5-star survey in Slack asking how the support went. One click, with an optional comment.

It is worth answering. Your team uses those ratings to find the request types that are going badly, and a low score with a sentence of context is the most direct way to tell them something is not working.

<Note>
  Surveys are turned on per support channel, so you will not get one for every ticket. They are delivered in Slack only, not in Microsoft Teams.
</Note>

***

## Giving feedback on AI answers

When Ravenna answers using your company's knowledge, you may see thumbs up and thumbs down buttons under the response.

<AccordionGroup>
  <Accordion title="Helpful answer" icon="thumbs-up">
    Thumbs up when the answer was accurate. It confirms the underlying document is doing its job.
  </Accordion>

  <Accordion title="Needs improvement" icon="thumbs-down">
    Thumbs down when the answer was wrong or out of date. It flags the document for review, and on most teams it also opens a ticket so a person picks your question up.
  </Accordion>
</AccordionGroup>

That feedback is how your organization finds the questions its documentation does not answer yet, so the answers get better for everyone.

***

## Approvals

Some requests need someone to sign off before work starts, a budget request or an access request for example. If that is you, here is how it reaches you.

### How approval requests arrive

You always get a direct message from Ravenna with the ticket details and **Approve** and **Decline** buttons. That DM is sent whatever your notification settings say, so approvals do not get lost.

Depending on the ticket, you may also see:

| Also happens | When |
| - | - |
| An `@`-mention in the ticket's Slack thread | The ticket lives in a public channel |
| An entry under **My Approvals** in the Home tab | Always, until you decide |
| An Adaptive Card in your Microsoft Teams chat | Your organization runs on Teams |
| An email notification | Your organization has pending-approval emails on |

<Note>
  If your organization requires identity verification for approvals, the buttons take you to Ravenna in a browser to confirm it is you before the decision is recorded.
</Note>

### Your options

<AccordionGroup>
  <Accordion title="Approve" icon="circle-check">
    The request moves forward. The requester and the assignee are notified, and work continues.
  </Accordion>

  <Accordion title="Decline" icon="circle-x">
    The request stops. You can add a reason, and it is worth doing, because it tells the requester whether to resubmit with corrections or drop it.
  </Accordion>

  <Accordion title="Ask before deciding" icon="message-circle">
    There is no separate "need more info" button. Reply in the ticket thread or the DM to ask your question, and approve or decline once you have an answer. The request stays pending until you act.
  </Accordion>
</AccordionGroup>

<Warning>
  Approvals block the request completely. Nothing happens on the ticket until every approver has decided, so a request left undecided is a colleague waiting.
</Warning>

***

## Summary

You can now:

* **Submit requests** through the Ravenna app, a public channel, the portal, or email
* **Track everything** you have filed from the Home tab or **My requests** in the portal
* **Get instant answers** from your company's knowledge, and flag the ones that are wrong
* **Rate resolutions** when the survey arrives
* **Handle approvals** from Slack, Teams, or the portal

A few habits that make it work better:

* Use a public channel when the question is not sensitive, so the answer helps the next person
* Give a thumbs down when an answer is wrong. Nobody finds out otherwise
* Decide approvals the day they arrive

<Tip>
  **Need help with Ravenna itself?** Ask in the Messages tab, or file a request like any other.
</Tip>


## Related topics

- [User handbook](/guides/user-onboarding/handbook/quirky-edition.md)
- [Notion templates](/guides/user-onboarding/handbook/notion.md)
- [Product Updates](/changelog/2025.md)
- [Overview](/documentation/automate/knowledge/overview.md)
- [Go live](/guides/day-one/go-live.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.