# Tickets

> Work the problems your agent could not solve, in one list by state, with the whole thread and a reply that emails the customer

Source: https://www.hey.support/docs/conversations/tickets

---

Tickets live in the **Inbox**, in their own **Tickets** section under Chats and AI agent. It is the same job as a chat, somebody needs a reply, differing only in whether they are still sitting in the chat. On a narrow screen the list header switches between Chats and Tickets instead.

Set the capability up first in [Tickets](/docs/capabilities/tickets) under Capabilities.

## The list

The Tickets menu group follows the work: **All tickets**, **Unassigned** and **My open**, each with a count, and **By status** for **Open tickets**, **Waiting on them**, **Solved** and **Closed**. The agent picker above the Inbox narrows everything to one agent.

Each row leads with the person and when they last wrote, then the ticket number and subject, its status, and who has it. A dot means the last word was the customer's. A red **Overdue** marks a ticket past the reply time the customer was promised.

Work views start sorted **Waiting longest**: tickets owed a reply first, the longest wait at the top.

**Filter** narrows by priority, category, teammate or Overdue; search covers names, addresses and ticket numbers. **Select** sets the status, priority or teammate of several tickets at once. The table button shows the same tickets as a table, 25 to a page, where you can change status, priority and teammate in place.

## Working a ticket

Opening a ticket shows the whole thread with who wrote each reply and any photos or PDFs. The status button in its header moves it on, and **View chat** opens the conversation it started in.

<Steps>
  <Step>
    ### Reply or leave a note

    **Reply** goes to the customer as an email with your words and a link back to their ticket. The paperclip attaches a photo or PDF, which they open from that link. Type `#` for your saved replies; `{{ticket_number}}` fills in the ticket's number. The arrow beside **Send** sends and sets the status in one go.

    **Internal note** never leaves your team: not in the customer's email, not on their status page, not in anything the API returns.

    Replying to a ticket nobody has taken assigns it to you. An assignment someone chose is left alone, and a note never assigns anything.
  </Step>

  <Step>
    ### Move it on

    **Open** picks it up. **Waiting on them** parks it while the customer owes a reply. **Solved** finishes it, which emails the customer and asks how you did.

    A solved ticket closes itself after a few days. If the customer replies first, it reopens and the close is cancelled.
  </Step>

  <Step>
    ### Teach your agent

    When you solve a ticket, the Inbox asks **Should your agent answer this itself next time?**, with the customer's question and your reply filled in. Edit either and save: a short answer becomes a quick answer, a long one joins your agent's knowledge. **Not now** keeps the same prompt under **Teach your agent** in the ticket's more actions menu.
  </Step>
</Steps>

<Callout type="info" title="Draft with AI">
  Writes a reply from your knowledge and puts it in the composer for you to read, edit and send. It never sends anything itself, never invents a policy, refund amount, delivery date or order status, and writes `[PLACEHOLDER]` where it needs a fact nobody has given it.
</Callout>

## Ticket info

The panel beside the thread shows who wrote in, with their email and phone, then **Ticket info**: status, priority, teammate and category, each saved the moment you pick it. Below are the promised reply time, the number and where it came from. Under it are the answers they filled in, their earlier tickets and the linked chat. On a narrower screen the same panel opens from the thread header.

## Reports

Ticket reports are on your agent's **Insights** page, under **Tickets**. They answer one question first: what share of chats your agent solved without a ticket. Under it: how many tickets came in, how many are finished, median first reply and resolution time, the average rating, and the breakdown by kind.

Times are medians in working hours. A ticket that arrived at six on Friday and was answered at nine on Monday counts as about fifteen minutes, because that is how much of your attention it took.

<Accordions>
  <Accordion title="Why a number shows as a dash">
    Every number that could mislead shows as a dash instead. The share solved without a ticket needs conversations to compare against; an average rating needs someone to have rated. A missing number is more use than a made-up one.
  </Accordion>

  <Accordion title="Tickets elsewhere in the dashboard">
    A conversation that produced a ticket says so in the thread, with a link to it. A handoff nobody took shows a quiet band naming the ticket it became. **Create ticket**, in the conversation's **More actions** menu, turns any conversation into one: **Create and email them the link** or **Create without emailing**.

    Tickets waiting on your reply also appear in the notification bell, and every alert (the bell, the email, Slack) opens the ticket itself in the Inbox.
  </Accordion>
</Accordions>

<NextSteps>
  <IconCard icon="clipboard-list" title="Tickets capability" href="/docs/capabilities/tickets" description="Categories, the reply promise and when the agent opens one." />

  <IconCard icon="inbox" title="Inbox" href="/docs/conversations/inbox" description="The conversation a ticket started in." />

  <IconCard icon="search" title="Quick answers" href="/docs/knowledge/quick-answers" description="Where a short taught answer lands." />
</NextSteps>
