Elbuz sorts tickets into queues and puts on top those where the customer has waited longest past the promised time, no scanning by eye.
When you need this:
- Not sure where to start in the morning — “SLA breached” shows who is past the deadline, “My open” your work for today.
- A customer gives a ticket number — search finds it in any queue.
- Dozens of tickets after the weekend — bulk actions change status, assignee or tag on several at once.
- A manager needs the workload — “Team” shows each person’s open and overdue tickets.
Where to start: open “Tickets” and click “SLA breached” in the left rail.
What the ticket list can do
- Standard queues — ready-made sets from “My open” to the archive, with counters.
- Custom queues — a filter by channel, priority, department or tag on top of a standard queue.
- Search — by number across all tickets, by text in the current queue.
- Sorting and density — the longest-overdue tickets on top; the compact view fits more rows.
- Board — the same tickets in columns by status; drag a card to change its status.
- Bulk actions — status, assignee, priority, department, tag or merge for several tickets at once.
- “Team” — each employee’s workload right in the queue rail.
Which queue to open and when
The queues on the left are saved sets of tickets with counters. They don’t move tickets around: one ticket can be in several queues at once. The rail runs from “mine and urgent” down to the archive.
| Queue | What’s in it | When to open it |
|---|---|---|
| “My open” | Your tickets with the status “New”, “Open” or “On hold”. Tickets waiting for the customer aren’t here | First thing in the morning: this is your work for today |
| “Unassigned” | Tickets with no assignee, except solved and closed ones | Once a day: this is where tickets land that distribution doesn’t hand out (the customer has been silent for over 3 days), and with “Manual” distribution, all new ones |
| “SLA breached” | Tickets past their reply or resolution deadline | Twice a day; for a manager, all the time |
| “All open” | All “New” and “Open” tickets, whoever they belong to. “Pending” and “On hold” tickets aren’t included | To see the overall workload. The window opens on this queue the first time |
| “Pending” | You replied and are waiting for the customer | When you need to remind the customer about the ticket |
| “On hold” | You’re waiting for someone other than the customer: a supplier, the warehouse, a colleague | When the third party has replied |
| “Solved” | Solved but not yet closed (up to 4 days) | To check that nothing was closed too early |
| “All tickets” | Everything, including closed tickets | To look up an old ticket |
| “Knowledge base gaps” | Tickets for which AI found no answer in the knowledge base | To write the missing articles — see “AI in tickets” |
The window remembers the selected queue, sorting, view and list density in your browser: on another computer it opens with the default settings. At the bottom of the list you see the queue name and the number of tickets in it.
A row shows only what sets a ticket apart from its neighbours. In “Pending”, “On hold” and “Solved” there is no status in the row, since it’s the same for all; in “My open” and “Unassigned” there is no assignee. Of the priorities, only “High” and “Urgent” are shown.
Custom queues
“New queue” in the “My queues” section is a filter on top of a standard queue: you pick the base (the “Tickets” field), then the channel, priority, assignee (“Me” means whoever opens the queue), department and tag. For example, “All open” + the Viber channel gives a separate queue for the person who handles messengers.
The “Visible to all staff” checkbox makes the queue shared; without it, the queue is yours only. Right-click your queue for “Edit queue” or “Delete queue”; deleting a queue doesn’t touch its tickets. Anyone with access to the window can edit or delete a shared queue.
Enter one tag in the “Tag” field: if you enter several separated by commas, the queue filters by the first one only. You can hide the queue rail with the chevron at the top (“Hide / show queues”) to give the list more room.
1
My open2
SLA breached3
My queues / New queue4
Search5
View6
Sorting and list view7
Due-date chip- My open — your work for today, with a counter next to it.
- SLA breached — tickets whose deadline has already passed.
- Your own queues are filters on top of a standard queue.
- Search: a number finds a ticket across all tickets, text searches within the queue.
- View switches between List, Board and Reports.
- Sorting, density and shortcut keys.
- How much time is left until the deadline or how long it is overdue.
How to find a ticket by number or name
The search box is the first thing in the list header; its placeholder reads “Number, subject, customer”. Press / to put the cursor there.
- A number (125 or #125) searches by ticket number or by the number from the system the ticket was imported from — across all tickets your “Data scope” lets you see, regardless of the queue.
- Text searches the current queue — by subject, name, contact and customer. If text search finds nothing, switch to the “All tickets” queue.
While there is a query in the box, the counter at the bottom of the list shows the number of matches, not the size of the whole queue. Search by number also finds a ticket merged into another one: it contains the link “Merged into ticket #N”.
How to arrange the list
Sorting, density and the keyboard shortcut reference are in the “⋮” menu on the right of the list header (tooltip “Sorting and list view”).
Sorting
The default is “Nearest deadline”: overdue tickets on top, starting with the longest overdue, then those whose deadline is closest; tickets with no deadline (“Pending”, solved) go to the end. So the first row is always the one where the customer has waited longest past the promised time.
| Sorting | What’s on top | When to use it |
|---|---|---|
| “Nearest deadline” | Overdue tickets, then those whose deadline is closest | Every day, by default |
| “Unread and priority” | Unread tickets, ordered “Urgent” → “High” → “Normal” → “Low”, then by the customer’s latest message, newest first | When priority matters more than the deadline |
| “Waiting longest” | Tickets whose latest customer message is the oldest | Clearing a backlog after the weekend. It ignores whether you’ve already replied, so it works best in the open queues |
| “Newest first” | Just-created tickets | To see what has come in |
| “Recently updated” | Tickets with the latest change | To find what you were just working on |
List density
“Detailed” shows the subject, the first words of the message and the chips in each row. “Compact” drops the message text: name, subject and date on one line, chips on a second, so more tickets fit on screen. Compact suits a long queue; detailed, when you need to see what the customer writes about.
“Waiting N” and bold rows
A row usually ends with the date of the customer’s latest message. If a “New” or “Open” ticket’s last message is the customer’s, you see an orange “waiting 40 min” or “waiting 1 d 3 h”. It counts calendar time, not business hours, as customers feel it. The date is in the tooltip; once you reply, the date returns.
The “unread” mark is shared by everyone: as soon as any colleague opens a ticket, it stops being bold for you too. So “bold” means “a new message nobody has opened yet”, not “I haven’t seen it”.
How to see all the work as a board
The view button with an arrow next to the search opens “List”, “Board” and “Reports”; its icon shows the current view. The board shows unclosed tickets in columns by status: “New”, “Open”, “Pending”, “On hold”, “Solved” (solved in the last 7 days). A column holds up to 50 cards; the rest are in the list.
- Dragging a card to another column changes its status. It’s the same change as with a chip: an event in the feed, and moving a ticket to “Solved” with ratings turned on sends the customer a rating request.
- Clicking a card opens the ticket to the right of the board; the cross in the ticket header closes it, and the board goes back to full width.
- The board shows the same set as the selected queue, standard or custom, laid out by status. For “All open” that means only the “New” and “Open” columns; all five appear in “All tickets”.
- Search on the board covers subject, name, contact and number. A number is looked up across all tickets your “Data scope” lets you see, not only in the queue.
The board suits a manager in a meeting and a small team that looks at all the work together. For day-to-day replies, the list is faster. For what the “Reports” view shows, see “Reports and customer ratings”.
1
View button2
Column header with counter3
Ticket card4
Solved column- Switches between List, Board and Reports.
- Status and how many tickets are in it.
- Click opens the ticket; dragging to another column changes its status.
- Solved tickets of the last 7 days.
How to change several tickets at once
Select tickets with the checkbox on a row’s channel icon, Ctrl+click (⌘+click on a Mac) or Shift+click for a range. The header checkbox is “Select all on the page”. A “Tickets selected: N” bar appears with “Status”, “Assignee”, “Priority”, “Department”, “Add tag” and “Merge”; the cross on the right is “Clear selection”. A plain row click clears it too.
Right-clicking gives the same changes, except tag and merge: a “Tickets selected: N” menu with the submenus “Status”, “Priority”, “Assignee” and “Department”. Right-clicking a row that isn’t selected acts on that row only.
- Each ticket is changed separately, with an event in the feed, just as with a chip in the header.
- Tickets outside your “Data scope” are skipped; the summary reads “Tickets changed: N”.
- Bulk “Solved” with ratings turned on sends a rating request to every customer who hasn’t received one yet.
- Bulk assignment sends each assignee “Ticket #N is assigned to you”; you don’t get a notification for tickets assigned to yourself.
- “Add tag” adds the tag to each ticket’s existing tags rather than replacing them.
“Merge” works with two or more selected tickets: Elbuz asks “Merge the selected tickets (N) into the oldest one, #X?”, moves the emails, messages and notes of the others into the ticket with the lowest number and closes them. Then #X opens. For what exactly carries over in a merge, see “Customer and orders in a ticket”.
1
Row checkbox2
Tickets selected: 33
Add tag4
Merge5
Clear selection- Marks a ticket, same as Ctrl+click.
- How many tickets will change.
- Adds a tag to the existing ones.
- Merges the selected tickets into the oldest one, irreversible.
- Clears the selection without changes.
How a manager sees the team’s workload
Below “My queues” in the rail is the “Team” section, visible to those whose “Data scope” covers all tickets. Each row is an employee with tickets that aren’t closed, plus the number of their “New” and “Open” tickets.
- A dot next to the name means the employee has overdue tickets.
- A highlighted row means they have 1.5 times more open tickets than the team average. Tooltip: “Workload is 1.5× above average”.
- The row tooltip reads “Name: N open, M overdue”.
- Clicking a name opens their open tickets in the list; the bottom of the list shows “Selection: Name”. This selection isn’t remembered: next time the window opens on a regular queue.
Unassigned tickets aren’t in “Team”; they’re in the “Unassigned” queue. To move some tickets from an overloaded colleague to someone else, open their selection, select the tickets and change “Assignee” on the bulk actions bar. The same figures, with the “New” and “Longest waiting” columns, are in the “Right now” block of the “Reports” view (“Reports and customer ratings”).
1
Team2
Overdue dot3
Highlighted row- Visible to those whose data scope covers all tickets.
- The employee has overdue tickets.
- Open tickets above the team average by 1.5 times.
- Clicking a name opens that employee's open tickets.
What changes in a narrow window
The “Tickets” window shares the desktop with other windows, so it’s sometimes narrow. Elbuz adapts it automatically:
- Window up to 1300 px wide — the queue rail collapses to icons; the queue name is in the tooltip. Widen the window and the rail comes back the way you left it with the chevron.
- Narrow list — the bulk actions bar buttons turn into icons with tooltips.
- Narrow ticket — the right panel with the customer and orders hides, and a “Customer” button appears in the ticket header. It slides the panel out over the feed; clicking the feed hides it.
1
Queues as icons2
Customer button3
Slide-out customer panel- In a window narrower than 1300 px the queues collapse into icons; the name is shown in the tooltip.
- Slides out the customer panel.
- A click on the conversation hides the panel.
Scenarios
An agent’s morning
Open “SLA breached” and reply from top to bottom. Then “My open” sorted by “Nearest deadline”: the J key opens the next ticket. Finish with “Unassigned”. To skip deciding where to start once your own tickets are done, use “Take next”.
A separate queue for messengers
An employee handles only Viber and Telegram. “New queue” → “Tickets”: “All open”, channel Viber, name “Viber”. Create a second one the same way for Telegram. Tick “Visible to all staff” if several people handle messengers.
Redistributing a queue after a vacation
In “Team”, the manager clicks the name of the employee who went on vacation, and the list shows their open tickets. They select half, set “Assignee” → a colleague, and give the rest to a second colleague. Each gets the notification “Ticket #N is assigned to you”.
Closing a batch of spam
In “Unassigned”, Ctrl+click the advertising emails, then “Status” → “Closed”. The summary shows how many tickets were changed.
A broken promotion
Customers write that a promo code doesn’t work. Find these tickets by searching for “promo code” in “All open”, select them all, set “Priority” → “High” and “Add tag” → “promotion”. A custom queue with the “promotion” tag lets everyone working on it see them.
What to do when you can’t see a ticket
| What you see | Why | What to do |
|---|---|---|
| A ticket has disappeared from the queue | Its status or assignee changed, it was merged into another ticket, or it closed after 4 days | Find it by number — search looks up the number in all queues; a merged ticket leads to the target ticket |
| Text search finds nothing | Text is searched only in the current queue | Switch to “All tickets” and search again |
| A custom queue with tags doesn’t show everything | Several tags were entered in the “Tag” field, and the queue uses only the first | One tag per queue; for a second tag, create another queue (custom queues) |
| The board has only two columns | “All open” is selected, and it holds only “New” and “Open” | Select the “All tickets” queue (board) |
| There is no “Team” section | Your department’s “Data scope” doesn’t cover all tickets | Ask an administrator to change “Data scope” in the group permissions (setup) |
| “Tickets changed” is lower than the number selected | Some tickets are outside your “Data scope” and were skipped | Ask a colleague with wider access or a manager |
FAQ
Why is a ticket in both “My open” and “SLA breached”?
Queues are sets, not folders: a ticket appears in every queue whose conditions it meets. Your overdue ticket will be in both.
Can my colleagues see my queue?
Only if “Visible to all staff” was ticked when you created it. Without it, the queue is yours only.
The list opened differently on another computer. Why?
The queue, sorting, view and density are remembered in the browser. On another computer or in another browser you get the default settings.
Can I add a tag to many tickets at once?
Yes: select the tickets and click “Add tag” on the bar above the list. The tag is added to each ticket’s existing tags.
Which ticket does a bulk “Merge” go into?
Into the ticket with the lowest number among those selected, which is the oldest. The others are closed with a link to it (bulk actions).
Why is there no status in the row?
In queues where all tickets have the same status (“Pending”, “On hold”, “Solved”), it isn’t repeated in every row. For the same reason, the assignee isn’t shown in “My open” and “Unassigned”.
Where to find it and who has access
- Menu
- Organizer → Tickets
- Other ways in
- Directories → Contacts → Tickets; a shortcut on the desktop
- Access right
- the “Tickets” window in “Group permissions”; you see the tickets the department’s “Data scope” allows
- “Team” section
- for those whose “Data scope” covers all tickets
The window has the queue rail on the left, the ticket list in the middle and the ticket itself on the right. For working inside a ticket, see “How to reply to a customer in a ticket”.
Related topics
- If you need the overall picture of the workspace — “Working with tickets as an agent”.
- You’ve opened a ticket and are ready to reply — “How to reply to a customer in a ticket”.
- The list has two tickets from the same customer — “Customer and orders in a ticket”.
- Want new tickets to be handed out automatically — ticket distribution.
- If you’re choosing a helpdesk for an online store — what it gives your store.
