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

# Tickets

> How tickets work — what Swan asks you for, answering, snoozing and dismissing, and notifications.

When an automation run can't finish without a person, Swan opens a **ticket** and assigns it to one teammate. The run waits on the ticket and picks up where it left off once the ticket is answered. Everything one run needs from a person arrives as one ticket. Tickets are how Swan asks you to approve, decide or do something; chat conversations ask you directly instead (see [chat and approvals](https://docs.getswan.com/workspace/chat-and-approvals.md)).

## The tickets feed

Your open tickets are listed at [agent.getswan.com/tickets](https://agent.getswan.com/tickets), under **Needs you**, with a count on the rail icon. The chat home also previews your most urgent ones. Search the feed in your own words ("outreach to approve", "anything overdue"), and open a ticket to see it in full, with the company or contact it's about and Swan's summary of what the run did so far.

Each ticket shows the company or contact it's about, the automation (or chat) that opened it, a title, and Swan's account of why it stopped. A ticket is due three days after it opens unless Swan sets another date; overdue and due-today tickets are marked.

## What a ticket asks for

A ticket holds one or more items, and each is one of:

* **A decision** — pick one of Swan's options (its suggestion is marked), or write your own.
* **A question** — type an answer.
* **Something to do** — mark it done, or say why not.
* **An approval** — approve or reject an action Swan held back, such as sending an email. When the ticket shows the exact action, you can edit it first, and it runs as you approved it.
* **Sequences awaiting approval** — approve, reject or edit them in place. See [approvals](https://docs.getswan.com/outreach/approvals.md).

Nothing goes to Swan until every item is answered. Then you get a few seconds to undo, the ticket closes, and the run resumes with your answers. **Ask Swan about this** opens a chat about the ticket if you'd rather talk it through. You can also ask Swan in chat to find, answer, snooze or dismiss your tickets.

## Snoozing and dismissing

**Snooze** hides a ticket until later: in an hour, tomorrow, next week, or a day you choose. It moves to the **Snoozed** tab and comes back with a reminder. A snoozed ticket can still be answered or unsnoozed at any time.

**Dismiss** closes a ticket without answering it, when nothing more should happen. Swan stops waiting, and the run ends once it has no other open tickets.

A ticket nobody acts on expires shortly after it's due, and the run it was holding stops. A ticket also closes on its own when its work gets done somewhere else, for example when its sequences are approved on the Campaign page.

## Who sees what

The feed lists the tickets assigned to you. Only the assignee or an admin can answer, snooze or dismiss a ticket.

## Notifications

When a ticket opens, Swan can tell you on Slack, by email, or both. It decides from what you wrote under **What to notify you about** in [Settings → Notifications](https://agent.getswan.com/settings/notifications); when that doesn't settle it, your **Email** and **Slack** switches decide. Every ticket stays in the feed either way.

On Slack, Swan posts tickets to your own channel, `#<firstname>-swan`, which it creates the first time and invites you to. It's a public channel; if your workspace doesn't let Swan create channels, it uses your DM with Swan instead. To use a different channel, pick one under **Slack channel** in the same settings. Without Slack, those notifications come by email. You can answer from the Slack message, with its buttons or by replying in its thread, and the message updates as the ticket changes. See [Slack](https://docs.getswan.com/integrations/slack.md).

When a [reminder](https://docs.getswan.com/triggers/schedule.md#reminders) wasn't set in a Slack thread, its run reaches you through a ticket or notification, so these settings apply to it too.

## Common questions

**Does dismissing a ticket undo anything Swan already did?**
No. It only closes the ticket and stops the run from waiting on it.

**Why did a ticket disappear from my feed?**
It was answered or dismissed (by you, an admin, or in Slack), snoozed, expired, or its work was done elsewhere.

**I answered part of a ticket and left. Are my answers lost?**
No. They're saved in your browser and the card shows how many you've answered, but nothing reaches Swan until you answer the rest.

**How do I stop ticket emails or Slack messages?**
Say so under **What to notify you about** in [Settings → Notifications](https://agent.getswan.com/settings/notifications). The Email and Slack switches there only decide when your preferences don't, and for snoozed tickets coming back.


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