# Tickets: table view, priorities and reference numbers

Source: https://frosvo.com/docs/ticketing
Updated: 2026-10-22

Work conversations as tickets without a separate system: a sortable table, priorities, bulk actions, a ticket form for your website, a support page and reference numbers.

Every conversation in Frosvo can be worked as a ticket — no separate system.

## The table view

At the top of the inbox, switch from **Chat** to **Table**. Each conversation is a row with its subject, channel, priority, status, assignee and when it started. Sort by any column, filter, and tick several rows to **assign**, **tag**, **set priority**, **resolve** or **reopen** them at once. Frosvo remembers the view you used last.

## Priority

Set **low**, **normal**, **high** or **urgent** from the conversation's side panel or in bulk. Sort and filter by it in the table.

## Requests from your website

- **Ticket form** — paste `<script src="https://your-frosvo-address/f.js" data-site="your-site-key"></script>` where you want the form.
- **Support page** — every website also has a hosted page at `/support/your-site-key` to link to.

Each request gets a **reference number** and a confirmation email, and arrives in the inbox like any conversation. Customers can follow their requests and replies in the customer portal.

## Deadlines

Set first-reply and resolution targets under **Automation → SLA**. See [Automation](/docs/automation).

## Put priorities to work

Mark billing outages as **urgent** and general questions as **normal**, then sort the table by priority so the most important work is at the top. Combine this with response-time targets under [automation](/docs/automation), so you are warned before a deadline passes.

## Measure it

[Reports](/docs/reports) show first-reply and resolution times, so you can see whether priorities are working. Use the ticket form on pages where customers expect a formal request, such as a contact or support page, and the chat for quick questions.

## Common questions

**What if a customer replies to the confirmation email?** Replies are linked to the request, so the history stays together.

**Can I filter by priority?** Yes. Sort and filter the table by priority, status, channel or assignee.

**Where do customers follow their requests?** In the customer portal, with replies.

## Common questions

### Do I need a separate ticketing tool?

No. Every conversation can be worked as a ticket in the same inbox.

### Do customers get a confirmation?

Yes. Each request gets a reference number and a confirmation email.

### Can I change many tickets at once?

Yes. Tick several rows in the table, then assign, tag, set priority, resolve or reopen them together.