> For the complete documentation index, see [llms.txt](https://support.rosysalonsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.rosysalonsoftware.com/tickets/tickets-drop-down-overview.md).

# Tickets Drop-down: Overview

The **Tickets** drop-down provides access to most sales related functionalities.

![Tickets Dropdown](/files/37bc74f224ae1cc646c19812a11c5a8133f11c76)

![](https://support.rosysalonsoftware.com/hubfs/Knowledge%20Base%20Import/rtaImage-Aug-19-2022-12-37-09-33-PM)

**Ticket List:** Shows the real-time status of sales transactions of the Date shown at the top.

* The date at the top will always default to Today's date unless changed using the Calendar Icon next to it.
* When a client is checked in for a service, their ticket will auto-generate into the Open Tickets column on the left.
* Once you check out a client, *(or collect payment)*, the ticket will automatically move to the Closed Tickets column on the right.

![](https://support.rosysalonsoftware.com/hubfs/Knowledge%20Base%20Import/rtaImage-Aug-19-2022-12-37-09-13-PM)

![Ticket List](/files/f87c5c580b746e548dacbf8c804158b419765ac0)

[**New Ticket**](/tickets/creating-a-new-ticket.md)**:** A quick link to creating a new ticket for a service, product, package, or gift card without adding it to the Schedule.

[**Payment In**](/tickets/payment-in-payment-out-feature.md)**:** Record any Cash income or Checks not recorded on a ticket using this feature so that your Cash Drawer and income balance at the end of the day.

[**Payment Out**](/tickets/payment-in-payment-out-feature.md)**:** Record any Cash taken out of the drawer throughout the day along with a Reason.

[**Inventory Use**](/inventory/inventory-use-w-video.md)**:** Keep track of any Products, *(retail or professional)*, that are used by the Salon or an employee, or to record any lost/missing items.

[**House Sale**](/tickets/house-sale-ticket.md)**:** This is used for transactions of which the client does not wish to provide their information for.

* *For example: If someone walks into the Salon simply to purchase a Product or Gift Card, and does not want to give you their information to create them as a client, you'll use the House Sale Ticket.*

[**Ticket Summary**](/reports/ticket-summary.md)**:** Provides a detailed summary grouped by employee for all closed(paid) transactions throughout the Date Range chosen.

* If the employee running this Ticket Summary is under the role of Service Provider, they will only be able to see their *own* information.

[**Price Check**](/inventory/product-price-check.md)**:** Allows you to quickly look up the price of a Product.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.rosysalonsoftware.com/tickets/tickets-drop-down-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.