Welcome to the new Lovely Views user guide! This guide walks through how Lovely Views works day-to-day in Zendesk, from finding your way around to managing views, handling tickets, and adjusting settings.

Topics covered in this guide:

Overview
What Lovely Views does in Zendesk, what’s new, and the key ideas that show up throughout the app (views, folders, sections, tabs, navbar vs topbar, and saved Seek searches as views).

Getting started
How to open Lovely Views, where it appears in Zendesk (navbar, topbar, and sidebars), and a quick first-time checklist.

Interface overview
How the layout is structured, what each tab is for (List, Home, Views, Seek, Bookmarks, Activity), and the always-available topbar buttons.

List
What List is for, how the sections work (Favorites, Seek, Extra, Personal, Views), and how to find things fast.

Ticket handling
How ticket lists work in Views, previewing tickets, and using bulk actions (edit, merge, spam, read/unread, bookmarks, delete, select all pages).

Home
How Home works, including setting a Home view, setting Seek as Home, and what happens when Home changes while you’re on another tab.

Views
Opening views, using filters and view options, refreshing view results, and managing views (rename, move, edit, clone, delete, export CSV).

Folders
Creating folders, expanding/collapsing, moving views into folders, merging folders, and practical folder structure tips so navigation stays clean.

Bookmarks
What Bookmarks are, ways to bookmark tickets, searching/sorting, and refresh behavior.

Activity
What Activity shows (recently opened and viewed tickets), searching/sorting, and refresh behavior.

Seek
What Seek is for inside Lovely Views and how to open it. For building searches, templates, and deeper Seek usage, this guide links out to the dedicated Seek user guide.

Admin
How Lovely Views is set up for your Zendesk instance.

Personal preferences
Settings each user can control for themselves, like display and behavior options. These changes only apply to the logged-in user.

Preferences
App-wide settings that control how Lovely Views behaves across the account, such as General, List, View, Selected tickets, Bookmarks, Activity, Ticket sidebar, and Backup & Restore. Use this section to fine-tune workflows and performance, and to back up or restore your configuration.

Export and reporting
Downloading the views list CSV, what’s included, and export troubleshooting.

Troubleshooting
Common issues (counts not changing, missing views, Home/Favorites oddities, Bookmarks/Activity not showing expected tickets, preferences not saving, Zendesk limitations).

FAQs
Quick answers to the questions people ask most often.

Getting support
What to include when you reach out so issues can be diagnosed faster.

OVERVIEW

Use this guide to get familiar with the layout, then jump into the sections you need (List, Views, Bookmarks, Activity, and Seek).

Want to go deeper on Seek? See the Seek user guide for building searches, templates, and saved searches.

What Lovely Views is

Lovely Views is a workspace inside Zendesk that makes it easier to navigate views, keep tabs on what’s changing, and handle tickets quickly. You still use your existing Zendesk views and permissions, but the day-to-day experience is more organized and faster to work from.

With Lovely Views, you can:

• Navigate large view lists without the mess

  • Browse views in a structured List (with folders and subfolders).

  • Use Favorites and Home to keep your go-to views easy to reach.

• Work from where you already are in Zendesk

  • Use Lovely Views from the navbar or the topbar panel, depending on your layout.

  • Key buttons are always available in the topbar: Home, Bookmark, New search, Admin, Pin.

• Get full context faster with enhanced previews including AI-generated summaries

  • Scan the full conversation and key ticket details right from the list.

  • Take quick actions from the preview when you need to.

• Handle tickets in bulk

  • Select multiple tickets and apply actions like edit, merge, mark spam, mark read/unread, bookmark, and delete/close.

  • Admin settings control what’s available by role/group.

• Stay on top of changes

  • See ticket counts on views and folders.

  • Use refresh and auto-refresh tools.

  • Use unread tools to spot what needs attention.

• Bookmark tickets privately

  • Bookmarks are personal. They don’t change the ticket or affect other agents.

• Pick up where you left off

  • Activity shows your recently opened and viewed tickets, which is handy when you’re bouncing between issues and need a quick way back.

• Search using Seek

  • Build searches that go beyond standard views by combining conditions (fields, tags, requester/org, groups/brands/forms, dates, status, and keywords).

  • Save a search and reuse it as a repeatable work queue.

Lovely Views doesn’t change how Zendesk defines views, automations, or permissions. It builds on them, then gives you a cleaner place to work from.

What’s new in the latest Lovely Views

This update turns Lovely Views into a fuller “stay-here-while-you-work” workspace, with Quickie-style navigation and tools built in.

What’s new:

• A tabbed workspace

  • Lovely Views now includes tabs like List, Home, Views, Seek, Bookmarks, Activity, so you can switch between navigation, work queues, saved items, and recents without jumping around Zendesk.

    

• New search and Seek built into Lovely Views

  • You can start a search any time from New search, combine conditions (fields, tags, requester/org, groups/brands/forms, dates, status, keywords), and save searches to reuse as a repeatable work queue.

    

    

• Activity tab (recents)

  • Activity shows your recently opened and viewed tickets, so it’s easy to jump back when you’re bouncing between issues.

    

• Bookmarks as a dedicated tab

  • Your bookmarked tickets are grouped in one place, so it’s easier to scan, search, and open them as a personal follow-up list.

    

• Easier folder and view organization

  • Folder actions like Move to (and things like merging folders, if supported) make organizing large view lists less dependent on renaming conventions.

    

Key concepts

Before you jump into the how-to steps, it helps to understand a few core concepts that Lovely Views is built around.

Views, folders, and sections

• Views are your Zendesk views (plus any saved Seek searches you use like views).

  

• Folders are how views are grouped in the List. Some folders come from your naming structure, and others are system folders (like Deleted tickets).

  

• Sections are the top-level groups inside the List tab, like Favorites, Views, Personal, Seek, and Extra. They keep different kinds of items separated so the list stays easy to scan.

  

Navbar vs topbar 

Lovely Views can be opened in two places in Zendesk:

Nav bar (main workspace)
Open Lovely Views from the Lovely Views icon in Zendesk’s left nav bar. This opens the full Lovely Views workspace in the main area, with List always visible on the left.

Topbar (quick panel)
Open Lovely Views from the Lovely Views icon in Zendesk’s topbar. This opens Lovely Views as a panel, with its own row of tabs/icons across the top.

They’re connected. You can use the topbar panel for quick actions, and the nav bar workspace for “living” in Lovely Views while you work.

Sidebars (when enabled)
You may also see Lovely Views actions in the ticket, user, or organization sidebars. We cover those locations in Getting started.

Tabs in Lovely Views

What you’ll see in the main workspace

• List is always visible on the left (it’s your navigation area)

• Across the top, you’ll use these tabs:

  • Home: your Home queue (whatever you set as Home)

  • Views: where views open as ticket result lists (including saved searches opened from the List)

  • Bookmarks: your personal bookmarked tickets

  • Activity: tickets you’ve recently opened or viewed

  • Seek: start a new search or use templates

Note: When you click a view from the List, it opens in Views in the main workspace.
If you click a saved search, it also opens in Views and can be edited like it would in Seek.

What you’ll see in the topbar panel

• List appears as a tab inside the panel 

• You’ll also see:

  • Home

  • View: this is where saved search results appear in the topbar panel

  • Bookmarks

  • Activity

  • Seek

Important differences in the topbar panel

• Clicking a view from the List opens it in the main workspace (not inside the panel). The View tab in the top bar panel is for saved searches only.

• Home is an always-visible button (not a permanent tab). If your Home is set to a saved search, clicking Home opens that saved search inside the topbar panel, and you’ll see a Home tab appear (showing the saved search results).

• If your Home is set to a standard view, clicking Home opens it in the main workspace (not inside the topbar panel).

Saved Seek searches as views

• The Views tab can show a Zendesk view, or a saved Seek search you selected from the List.

• When you open a saved Seek search here, it behaves like a view (ticket results list), but you can also edit it like you would in Seek.

GETTING STARTED

A quick walkthrough to help you open Lovely Views, understand where it appears in Zendesk, and get set up so you can start working right away.

Install and open Lovely Views

For admins (install):

1. In Zendesk, open Admin Center.

2. Go to Apps and integrations > Zendesk Support apps > Marketplace.

3. Search for Lovely Views and open the listing.

4. Click Install.

5. Choose who should have access (roles/groups, if your team uses access restrictions), then Install.

For everyone (open):

• In Zendesk Support, open Lovely Views from the left sidebar (navbar), or from the topbar panel (right-side panel), depending on your layout.

• If you do not see it right away, refresh the Zendesk page.

---

Where Lovely Views appears in Zendesk

Lovely Views can show up in a few places in Zendesk. The two main ones are the main workspace and the topbar panel, and then you may also see it in sidebars.

Main workspace (opened from Zendesk's nav bar, left side)

If you click the Lovely Views icon in Zendesk’s left icon rail, Lovely Views opens in the main workspace.

This is the “full size” experience where you’ll usually see:

• List always visible on the left

• Main tabs across the top (Home, Views, Bookmarks, Activity, Seek)

• The selected tab opened in the main work area (for example, a view’s ticket list)

---

Topbar panel (opened from Zendesk’s topbar)

If you click the Lovely Views icon in Zendesk’s top icon area, Lovely Views opens in the topbar panel.

You’ll see the same main tabs here too, but they open inside the panel instead of taking over the main workspace. This is handy when you want Lovely Views available while keeping your main workspace focused on something else.

---

Ticket sidebar

Depending on your setup, you may also see Lovely Views actions in the ticket sidebar. This is usually for quick actions while you’re already inside a ticket.

(We cover what’s available there in the relevant sections later in the guide.)

---

User sidebar

Lovely Views may also appear in the user sidebar, again depending on what your admin has enabled.

---

Organization sidebar

Lovely Views may also appear in the organization sidebar, depending on what your admin has enabled.

---

First-time setup checklist

Use this once after install (or anytime something feels “off”):

• Open Lovely Views in the topbar and click Pin, so it stays open while you work.

  

• Decide where you’ll mainly work: left sidebar (full workspace) or topbar (always within reach).

• Set your Home view (the view you want to land on first).

  

• Add a few Favorites for your daily queue.

  

• Confirm your preview and view options (things like tickets per page or showing ticket preview, if your team uses it).

  

• Check your bulk actions on a small set of test tickets so you know what’s available for your role (edit, merge, spam, read/unread, bookmark, delete/close, etc.).

  

• Try Bookmarks (save one ticket, then find it again).

  

• Try Activity (make sure recently opened tickets show up).

  

• If you use Seek, run a quick New search, then save it so you can reuse it as a work queue.

  

If something is missing (tabs, actions, or sidebars), it’s usually down to role/group access or admin settings, so it’s worth having an admin double-check those.

INTERFACE OVERVIEW

This section is a quick map of the Lovely Views layout, so you can get oriented and then jump to the tab or feature you need.

Main workspace layout (opened from Zendesk’s nav bar)

This is the full Lovely Views workspace opened from Zendesk’s left-side nav bar.

What you’ll usually see:

• List on the left (always visible for navigation)

• A tabs row at the top (Home, Views, Bookmarks, Activity, Seek)

• A main content area that changes depending on the tab

• Quick actions via the kebab menu on folders, views, and tickets (where available)

• A bulk edit bar that appears when you select one or more tickets (actions depend on your settings and permissions)

Topbar panel layout (opened from Zendesk’s topbar)

This is the panel version of Lovely Views, opened from Zendesk’s topbar.

What you’ll usually see:

• A tabs row so you can switch between List, Home, View, Seek, Bookmarks, and Activity.

• A scrollable content area that shows whatever tab you’re on.

• A row of always-available buttons at the top: Home, Bookmark, New search, Admin, Pin.

Tabs you can use

Lovely Views has two places you can work from:

• Main workspace (opened from Zendesk’s left sidebar icon)

• Topbar panel (opened from the shortcut in Zendesk’s topbar)

The tabs work the same idea in both places, but there are a couple of layout differences.

Main workspace tabs

In the main workspace:

• List is always visible on the left (it’s not a tab here).

• Across the top, you’ll use these tabs:

  • Home

  • Views

  • Seek

  • Bookmarks

  • Activity

Clicking a tab switches the main content area, while the List stays visible for navigation.

Topbar panel tabs

In the topbar panel, you’ll typically see these tabs:

• List

• Home (only if a saved search is set as Home view)

• View

• Seek

• Bookmarks

• Activity

Clicking a tab opens it inside the panel.

Quick description of each tab

• List: Your navigation hub (sections like Favorites, Views, Personal, Seek, Extra).
   

  

• Home: Your default landing view (main workspace). In the topbar panel, this tab only appears if you've set a saved search as Home view.
   

  

• Views: Where you work through tickets in a results list. In the main workspace, Views tab opens when you click a view from List. In the topbar panel, View tab opens to show saved search results.
   

  

• Bookmarks: Your personal saved ticket list.
   

  

• Activity: A quick way back to tickets you’ve recently opened or viewed.
   

  

• Seek: Where you start a new search or use templates.
   

  

Always-visible topbar buttons

These buttons stay available at the top of Lovely Views (in the topbar panel), no matter which tab you’re in:

• Home: Jump back to your Home view.
   

  

• Bookmark: Bookmark the current ticket quickly (and remove it if it’s already bookmarked).
   

  

• New search: Start a Seek search right away.
   

  

• Admin: Open the settings and info area.
   

  

• Pin: Keep the topbar panel open while you work in Zendesk.
   

  

Common patterns

A few UI patterns show up throughout Lovely Views:

Hover tools

• When you hover on items, you may see see quick actions appear.

Kebab menu

• The kebab menu is where you’ll find “everything else” for that item, like rename, move, clone, delete, and other actions depending on what you clicked.

  

LIST

List is your navigation hub in Lovely Views. It’s where you move between work queues, find the right view fast, and keep everything organized as your view set grows.

One quick note before you start:

• In the main workspace, List stays visible on the left.

• In the topbar panel, List shows as its own tab.

In this section, we’ll cover:

• What List is for (and when to use it vs opening a view)

• The different List sections (Favorites, Seek, Extra, Personal, Views) and what each one is meant for

• How List search works (including how it auto-expands sections and folders)

• Ticket counts and refresh controls (what counts mean, when they update, and what refresh does and doesn’t do) 

What List is for

List is your main navigation area in Lovely Views. It’s where you:

• Find the views you need (without scrolling through a messy, flat list)

• Keep your daily “go-to” items close (Favorites and Home)

• Start a search or jump into saved Seek templates or searches (without rebuilding them every time)

• Stay organized with folders and subfolders

Think of it as your control panel for moving between work queues.

Sections in List

List is split into sections that you can expand or collapse by clicking the section name. Each section is there for a different kind of navigation, so you can keep things tidy even as your view set grows.

Favorites

Your shortcuts.

• Shows the views and saved searches you’ve starred so they’re always easy to reach.

• Best for the 5–15 things you open constantly.

Find out more in Favorites.

Seek

Start and reuse searches.

This section is where you kick off a search, jump between the searches you currently have open, and start from a template.

What you’ll see here:

• New search
  Starts a fresh Seek search.

• Temporary search tabs 
  These are the searches you currently have open. They’re not saved, so they can disappear after a reload.

• My templates (including your default template)
  Templates are starting points for building searches quickly.

If you want a search you can reuse as a work queue, save it as a template in Seek. Saved searches show up in your List (under Personal > Searches, and optionally in Favorites if you star them). When you select a saved search from List > Personal > Searches, it opens as a results list, and you can edit it like you would in Seek.

If you’re building or fine-tuning searches, jump to the Seek user guide. This Lovely Views guide only covers Seek where it behaves differently inside Lovely Views.

Extra

Built-in items and “special” lists.

Extra is where you’ll find things that aren’t part of your normal Views folder structure. Think personal follow-ups, quick navigation tools, and a few system-style lists.

What you’ll typically see in Extra:

• Bookmarks
  Your personal bookmarked tickets list.

• My ticket tabs
  A quick way back to tickets you’ve recently had open, especially if you’re bouncing between a few issues.

• Current ticket activity
  A running list of tickets you’ve recently opened or viewed, so you can jump back without hunting.

• My profile
  A built-in folder that groups your personal queues:

  • Assigned

  • Requested

  • Followed

  • CC’d

• Suspended tickets and Deleted tickets
  Special lists that help you spot tickets that are suspended or deleted (you’ll often see these styled differently, like greyed out or red).

Find out more in Extra.

Personal

Your own items.

• Views and saved searches that are only visible to you.

• Useful for “my workflow” queues that you don’t want showing for everyone else.

There are a few menu options for this section: Add view, Manage views, Reload views list, and Download views list CSV.

Find out more in Personal.

Views

Your shared Zendesk views, organized.

• Shows your standard view set, grouped into folders and subfolders.

• This is usually the biggest section, and the one teams rely on for a clean structure.

There are a few menu options for this section: Add view, Manage views, Reload views list, and Download views list CSV.

Admins can also enable a Show only my views toggle. This allows agents to quickly hide shared views and focus only on their own.

Find out more in Views and Folders.

Misc

This folder inside the Views section holds views without a specific hierarchy; you can disable it or rename the folder via List preferences. Additionally, you can enable the option to display this folder or root level views at the bottom of the Views list.

Search in List

The List has its own search, so you can jump to the view or folder you need without scrolling.

When you use List search, it searches what’s in the List (views, folders, and section items), not ticket content.

Find views and folders

1. Click into the Search list field.

2. Start typing the name of a view or folder.

As you type, Lovely Views filters the List down to matches, so you can click straight into what you were looking for.

Tip: If your team uses a naming convention (like “Billing” or “Escalations”), searching that keyword is usually faster than navigating folder-by-folder.

Auto-expand sections and folders for matches

When your search matches something that’s currently “hidden” inside the List:

• The right section will expand (so you can see the match).

• Any parent folders will expand too (so the matching view is visible).

• The List stays expanded while you’re searching, so you can keep scanning nearby matches.

When you clear the search, the List returns to its normal state (and you can collapse folders again if you want).

Ticket counts in List

Ticket counts help you see workload at a glance. You’ll see counts next to items like sections, folders, and views.

What counts mean

• Views: the number is the current ticket total for that view.

• Folders: the number is the sum of the counts for the views inside that folder (including subfolders).

• Sections: the number is the sum of everything inside that section (for example, Favorites totals up the favorites shown there).

• No number showing: it usually means counts haven’t been loaded yet, the item doesn’t support counts, or your access to those tickets is restricted.
  
  Tip: Counts reflect what you can see in Zendesk. If you don’t have access to certain tickets, they won’t be included in your totals.

When counts update automatically

Counts don’t update for every ticket change instantly. In general:

• Counts update when Lovely Views loads, when you switch between items, and when you manually refresh counts.

• Some setups may also update counts on a timer (if your account uses an auto-refresh option), but manual refresh is still the reliable “give me the latest” button.

If you’re expecting a number to change and it hasn’t:

• the ticket may not have fully moved views yet (depending on what changed),

• the view may rely on conditions that update on a delay,

• or you may just need to refresh counts.

Refresh controls

You’ll see the Refresh counts icon in the List for sections like Favorites, Views, Personal, and Extra.

Refresh counts does:

• Update the numbers you see in the List (sections, folders, views).

• Give you the latest totals without needing a full page reload.

Refresh counts doesn’t:

• Rebuild the ticket list content inside an already-open view.

• Force Zendesk to re-evaluate view membership instantly.

If your count looks right but the tickets you’re seeing inside the view look out of date, use Refresh this view from inside the view (that refreshes the results list, not just the numbers).

Favorites

Favorites are shortcuts in the List so you can jump to the views, folders, or saved searches you use most. Admins can enable or disable this feature for agents.

You can reorder your Favorites list by clicking Reorder via the section menu. Then drag and drop, and click Done to save the changes.

Add/remove favorites

• To add a favorite: hover the item in List and click "Favorite" in the item menu.

  Once added, from Favorites section, you can click the item's menu option "Find original" if you want to see where it's originally located in List.

  

• To remove a favorite: click "Favorite" again until the check is removed. 

  If removing from Favorites section, simply click the item's menu option "Remove from Favorites".

  

• Favorites can include views, saved Seek searches, and Seek templates.

Home icon behavior when a view is also a favorite

• A view can be both a Favorite and your Home view at the same time.

• If a view is your Home view, it will show the Home icon on that view in the List.

  

• If it’s also a Favorite, it will still appear in Favorites as well. Nothing breaks, it just means it’s pinned in two convenient spots (Favorites and Home button).

  

Extra

Extra is where Lovely Views groups helpful system and utility views. What you see here can vary depending on your configuration and permissions.

Bookmarks

Bookmarks shows your current bookmark count. Clicking it opens the Bookmarks tab, where you can view and manage your bookmarked tickets.

Bookmarks are personal to each agent. Your Bookmarks list isn’t shared with other agents.

My ticket tabs

This is a special view in Extra that helps you keep track of what you have open. Admins can enable or disable this view for agents.

What it shows

• Tickets you currently have open.

• It’s designed to match how people actually work: bouncing between a handful of tickets and needing a fast way back.

A ticket can disappear from “My ticket tabs” if:

• You no longer have permission to view it (role/group changes, ticket moved, etc.)

• The ticket was deleted or otherwise removed

• Zendesk can’t load it anymore (for example, it was merged or is no longer accessible under your current permissions)

Current ticket activity

This is another utility view in Extra that shows ticket activity (who is viewing/opening tickets). It’s useful for avoiding collisions like two people working the same ticket at once.

Access can be restricted (for example, admins by default, or enabled for selected roles/groups depending on your configuration).

My profile

This folder helps you quickly find common ticket groups which are meant to be ready-to-use “quick filters” for daily work. Admins can enable/disable or rename this folder.

Included are the following preset views:

• Assigned 

• Requested 

• Followed

• CC'd

Suspended and Deleted

Some accounts enable extra utility views like Suspended and Deleted. These are mainly for cleanup and oversight (and are often admin-only depending on Zendesk permissions). 

Admins can restrict access to agents, so if you don’t see these, it usually means they’re not enabled for your account or your role doesn’t have access.

Personal

The Personal section is where each agent’s own items live. These items are private and are not visible to other agents.

Personal includes two sub-sections: Searches (saved Seek searches) and Views (personal).

The position of the Personal section in List can be changed. See Place ‘Personal’ section below ‘Views’ for details.

Searches

Saved searches are always personal.

They’re reusable searches you’ve saved (usually built in Seek) so you can come back to the same work queue without rebuilding it.

Common examples include:

• A personal follow-up queue
• A search for a specific customer or project
• A temporary investigation you want to keep around for a while

Views

Personal views are views that belong only to you.

They behave the same as other views, but are not visible to other agents. This makes them useful for workflows you don’t want to share, or for testing changes before asking an admin to roll something out team-wide.

Typical examples include:

• A draft version of a team view you’re working on
• Your own triage queue
• A QA or audit view

Personal views can also be grouped into folders.

Emoji picker

You can add emojis to folders, views, and saved Seek searches to make items easier to recognize at a glance.

Emojis become visual identifiers in the List and in view headers, helping teams scan faster and organize work visually.

Lovely Views treats emojis slightly differently depending on where they are used.

Folder emoji

Folders use a single emoji as the folder icon.

Only the first emoji becomes the folder icon, even if multiple emojis appear before the name. Any additional emojis are treated as part of the folder name.

Examples

📦 Returns
Icon: 📦

📦🔥 Returns
Icon: 📦 (🔥 is part of the name)

🎯 Priorities
Icon: 🎯

View/saved search emoji

Views and saved Seek searches can use one or more emojis as their hero emoji.

The hero emoji is taken from the first emoji - or the first group of emojis - before the first space in the name.

If multiple emojis appear together without a space, they are treated as one hero group.

Adding a space stops the hero group.

Examples

🚀 Urgent tickets
Hero: 🚀

🚀🔥 Urgent tickets
Hero: 🚀🔥

💳🧾 Billing review
Hero: 💳🧾

⚠️ High priority
Hero: ⚠️

📦 Returns - EU
Hero: 📦

Where emojis appear

Emojis added to names appear in:

• List (folder and view icons)

• View header / screen title

• Sidebar

• Navigation areas where the item is referenced

This makes emoji usage consistent across the app.

Tips for using emojis

Use emojis to represent meaning, not decoration. Consistent patterns help teams scan faster.

Common patterns teams use:

• Priority → 🚨 ⚠️ 🔥

• Workflow stage → 📥 🧠 ✅ 📤

• Topic → 💳 Billing, 📦 Returns, 🛠 Technical

• Team ownership → 🎧 Support, 🧾 Finance, 🧑‍💻 Engineering

Avoid placing spaces between multiple hero emojis unless you intentionally want only the first emoji to be used.

Finding emojis quickly

You can search inside the emoji picker using keywords such as:

• warning

• star

• dollar

• clock

• bug

This helps you quickly find consistent icons for your naming system.

TICKET HANDLING

This section covers what it’s like to work tickets from inside a view: how the list behaves, how selection works, and how previews help you move faster.

Ticket list basics

When you open a view (or a saved Seek search opened as a view), you’ll see a ticket results list. This list is where you’ll do most of your day-to-day scanning and sorting.

Typical things you’ll see in the list:

• a row per ticket

• key columns (like Subject, Requester, Status, Updated, etc.)

• quick actions depending on your setup

Selection checkboxes

Checkboxes let you select tickets for bulk edit.

• Select a single ticket by ticking its checkbox.

  

• Select multiple tickets by ticking several rows.

  

• Select all tickets on the page by ticking the top checkbox.

  

• Your selected tickets stay selected until you clear them, change view, or refresh (exact behavior depends on what you do next).

  

Good to know

• Some bulk actions may be hidden or restricted depending on admin settings and your Zendesk role/group permissions.

• If you’re missing an action you expect, check the Admin section (or ask your admin).

Pagination

If a view has more results than can fit on one page, you’ll use pagination to move through pages of tickets.

• Use pagination controls to move forward/back.

• If you’re working in bulk, double-check you’re acting on the tickets you actually intended (especially if you moved pages).

Tip: If you need to take action on more than one page of results, see Bulk edit for options like Select all pages.

Previewing tickets

Previews are for triage. They’re how you quickly check what’s going on before deciding whether you need to open the ticket fully.

Regular preview

Regular preview gives you a quick look at the ticket on hover so you can confirm you’re in the right place.

Use it to:

• sanity-check the ticket subject/requester

• spot recent activity at a glance

• decide what to open next

Enhanced preview

Enhanced preview is built for speed when you’re working through a queue.

You can typically use it to:

• scan the conversation quickly (so you understand the context without opening Zendesk’s full ticket view)

• view key ticket details in the same place

• take common actions right away when you’re confident (without losing your place in the list)

If agent collision indicators are enabled, you can quickly see whether someone else is already working on the ticket.

Full opacity avatar: the agent is actively viewing the ticket right now

Lower opacity avatar: the agent has the ticket open, but it’s not the active tab

This is especially useful when you’re triaging a queue and want to avoid replying or updating a ticket someone else is already handling in Zendesk.

Admins can control who sees previews and whether enhanced preview is available in Admin > View options. 

Bulk edit

Bulk edit lets you apply the same action to multiple tickets at once. 

The exact set of actions you see depends on what your admin has enabled, plus your Zendesk role and permissions. On Lovely Views, check Admin > Selected tickets:

Before you run a bulk action:

• Double-check your selection (it’s easy to grab one extra ticket without noticing).

• If you’re mid-investigation, consider bookmarking first so you can come back to the same set later.

Clear

Use Clear to quickly deselect any currently selected tickets.

This is handy when:

• you selected the wrong tickets and want to start over

• you used Select all pages and want to back out safely

• you’re about to run a different bulk action and want to avoid acting on the previous selection by accident

Good to know:

• Clear only resets your selection. It doesn’t undo any bulk action you’ve already run.

• If your bulk edit bar/menu is showing options you don’t want to accidentally click, Clear is the fastest way to “reset the state.”

Edit

Use Edit to update multiple tickets in one go.

Typical bulk edits include things like:

• status changes

• assignee/group updates

• tags

• fields your admin has made available

Merge

Use Merge to combine multiple tickets into one, so you can handle duplicates as a single request and keep the work in one place.

Good for:

• duplicate requests from the same customer
• repeat submissions for the same issue
• multiple tickets that should share one outcome and one reply

Before you merge

• Double-check your selection. If you picked the wrong tickets, use Clear before continuing.
• Know what you want the final ticket to be. Depending on the merge method, you’ll either merge into an existing ticket or create a new merged ticket.

If you click Merge, you will be presented with two options:

Standard merge

Standard merge works like Zendesk’s usual merge flow.

What happens:

• You pick a target ticket.
• The other selected tickets become source tickets and are closed/merged into the target.

Steps:

1. Select ticket/tickets.
2. Click Merge.
3. Choose Standard merge
4. Pick a target ticket:

   • choose one of the tickets you selected

     

   • or use Search for a ticket and search by ticket ID, keyword, or phrase
     (results only show valid, not-closed tickets).

     

5. Clicking a ticket will designate it as the target ticket that the other tickets will be merged into. Clicking the ticket a second time will de-select it as the target. Once a target is selected, the comment boxes will be shown.
    
6. Review the comments:
   • one comment can be added to the source tickets
   • one comment can be added to the target ticket
   • comments are auto-generated, but you can edit them
   • if you change the target ticket, the comments regenerate and any edits are lost
   • you can also choose not to add a comment to either side (if your dialog includes those checkboxes)
7. Click Confirm and merge.
8. Lovely Views shows a loading state, then closes the dialog and refreshes the view/search results.

Custom merge

Custom merge lets you merge the tickets into a new, unified ticket, with control over what data is used as the “base” and whether comments from the selected tickets are copied over.

Steps:

1. Select ticket/tickets.
2. Click Merge.

3. Choose Custom merge

   

4. Choose how the merged ticket should be built (your account may show some or all of these):
   • None: create a new merged ticket without copying ticket data
   • Latestt: use the newest ticket as the base
   • Rolling: start with the least recently updated ticket, then apply updates from newer tickets in order

   • Specify by ticket ID: pick the exact ticket to use as the base

     

5. Follow the prompts to confirm what will be included, then run the merge.

If you don’t see Standard merge or Custom merge

Merge options and availability vary by account.

If Merge is missing entirely, or you only see one merge method, it’s usually because of:

• Zendesk role permissions
• group/role access rules
• an admin setting (for example, forcing a merge method)

Merge-related admin settings 

Lovely Views include admin controls for merging, such as:

• Requester must be the same when merging tickets
• Custom merge method
• Force custom merge method onto agent
• Add temporary tag while merging

Mark as spam

Use Mark as spam to flag obvious spam tickets in bulk.

Good to know:

• Spam behavior follows Zendesk rules. If you’re unsure, test on a single ticket first.

Open

Use Open to quickly open selected tickets.

This is handy when you’ve filtered down to a short list and want to work through them one by one without going back and forth.

Mark as read/unread

Use this to manage what you consider “needs attention”.

• Mark as unread is useful when you want a ticket to stay visible in your “unread” flow.

• Mark as read is useful once you’ve checked it and don’t want it flagged anymore.

Admins have control on how this feature works, including highlighting unread tickets and unread mode settings.

Bookmark

Bookmarks are personal, so bulk bookmarking is a great way to build a “come back to this” list fast.

Use this when:

• you’re triaging and want to follow up later

• you’re waiting on replies and want a quick place to check progress

Hover over the left side of a ticket list to reveal and click the Bookmark icon:

Clicking the Bookmark icon turns it purple, indicating the ticket is now in your Bookmarks view:

You can also use the bulk action option for bookmarking:

Add bookmarks - This will add a bookmark icon next to the ticket for you, and the ticket will also be added to your personal Bookmarks view for easy access.

Remove bookmarks - This will remove the bookmark icon next to the ticket, and the ticket will also be removed from your personal Bookmarks view.

Delete

Use Delete carefully. If it’s available in your account, it will follow Zendesk’s permissions and rules.

If you don’t see Delete, that’s normal in many setups, as this option is only available if your role allows for ticket deletion.

Select all pages

Select all pages lets you apply a bulk action to the entire result set, not just the current page.

This is powerful and also where people get burned, so it’s worth slowing down:

• confirm the view/search is truly narrowed down to what you mean

• sanity-check the count before applying an action

Once the Select all pages button is clicked, it will show the total number of tickets selected (for example, 366 tickets selected - ALL TICKETS on all pages). You can then click any of the bulk action buttons to apply: Clear, Edit, Merge, Mark as spam, Open, Mark as read/unread, Bookmark, or Delete (if your role allows for it).

Warning: When using the Select all pages feature, be mindful of the bulk actions you apply. Since this feature affects all tickets within the current view, any changes will be applied to a large number of tickets. Ensure that the action you intend to perform is appropriate for all selected tickets to avoid unintended consequences.

When tickets change outside Lovely Views

Tickets can change while you’re working, either because another agent updated them, an automation ran, or the ticket moved in or out of a view. Lovely Views can show those changes, but it helps to understand the difference between counts and what you’re actually seeing in a results list.

Counts vs content refresh

Counts are the numbers you see next to sections, folders, and views in the List. They’re a quick snapshot.

Content is the actual ticket list you’re looking at inside a view (or a saved search opened as a view).

Because those are two different things, you can get situations like:

• a view count changes, but the ticket list you’re currently looking at doesn’t update yet

• the ticket list updates after a refresh, but the folder or section count still looks stale until you refresh counts

• you open a view from the List, and it’s showing the last loaded results until you refresh the view

What to do

• If the number looks wrong, use Refresh counts in the List.

  

• If the tickets shown look wrong, use Refresh this view in the view header.

  

• If you’re unsure which one you need, refresh the view first. It’s the quickest way to confirm what’s actually in the queue right now.

Optional: auto-refresh (admins)

If your team wants Lovely Views to stay fresher without constant manual refresh, an admin can enable auto-refresh for the current view and/or auto-refresh for view counts (with a configurable interval). See Admin > View.

Ticket no longer available messaging

Sometimes a ticket you can see in Lovely Views can’t be opened or loaded anymore. When that happens, you’ll see messaging like “Ticket no longer available”.

This usually happens when:

• The ticket was deleted in Zendesk.

• The ticket was merged into another ticket (the original may no longer exist on its own).

• Your access changed (role, group, brand, or view permissions), so the ticket is no longer available to you.

• The ticket moved out of the current view/search, and you’re looking at an older list that hasn’t refreshed yet.

What to do

1. Refresh this view to reload the latest results.

2. If you were trying to return to the ticket from Bookmarks or Activity, refresh that tab too.

3. If it keeps happening across multiple tickets, it’s usually permission-related. Ask your admin to confirm your role/group/brand access. 

HOME

Home is your personal default starting point in Lovely Views. Set it once, and you’ve got a reliable “take me back to my main queue” shortcut.

Set a Home view/search

You can set Home from something you already use, including:

• a standard view

• a saved search (behaves like a view when opened)

Common places you’ll see Set as Home:

• From the List: open the item’s kebab menu (more actions), then choose Set as Home view

  

• From the main workspace: open the view options, then choose Set as Home view

  

• From a saved search results screen: open the options, then choose Set as Home view

  

What the Home button does (and where it opens)

Home takes you back to your chosen “default” work queue. Where it opens depends on where you click Home.

In the main workspace

Home is a tab.

• Clicking Home opens your Home item in the main workspace.

• This is true whether Home is set to:

  • a regular view, or

    

  • a saved search (that opens as a results list)

    

In the topbar panel

Home can appear in two different ways depending on what your Home item is.

If Home is set to a saved search

• Home appears as a tab in the panel.

• Clicking it opens the Home saved search in the panel (so you can work it without switching to the main workspace).

If Home is set to a regular view

• Home appears as a button in the panel (not a tab).

• Clicking it opens the Home view in the main workspace, with the Home tab active.

Home behavior across tabs

If you’re in List, Bookmarks, Activity, or Seek, clicking Home brings you back to your Home view.

If you’re already in your Home view, clicking Home simply keeps you there (it’s a “return to base” button, not a refresh button).

If you need to update the ticket results you’re looking at, use Refresh this view inside the view.

Home interaction with other features

Home plays nicely with the rest of the navigation, but a few things are worth knowing:

Home vs Favorites

• Something can be both Home and a Favorite.

  

• Setting one does not automatically set the other.

  

Home and folders

• Your Home item can live anywhere in the List (folders, Personal, etc.). Home will still point to it.

  

Home and saved searches

• If your Home item is a saved search, it opens like a view with a ticket results list.

• You can jump back to it the same way you would a view, using Home.

  

VIEWS

The Views tab is where you actually work your queue. It shows the ticket results for a Zendesk view (and it can also show a saved Seek search when you open one from the List).

Open a view

You can open a view in a few places:

• From the List: click a view name (or a folder, then a view).

  

• From Favorites: click the favorite item.

  

• From Personal: click your personal view.

  

• From Seek (saved searches as views): click a saved search, and it opens in Views as a results list.

  

When a saved Seek search opens in Views, it behaves like a view (ticket results list), but you can still edit it like you would in Seek.

View header tools

At the top of the Views tab, you’ll see tools that control what you’re looking at and how it’s displayed. Most teams use these constantly.

Filters

Filters let you narrow down what you’re seeing inside the current view results.

A few practical notes:

• Filters affect what you see right now, not the underlying Zendesk view rules.

• Clearing filters returns you to the full results for that view.

• If the view updates (refresh/auto-refresh), your filters typically stay applied so you don’t lose your place.

Refresh this view

Refresh this view reloads the ticket results for the view you’re currently looking at.

Use it when:

• You know something changed (status, assignment, new ticket added to the view) and you want the latest list.

• A ticket disappears or changes position and you want to confirm the current state.

This is different from Refresh counts in the List, which updates the numbers next to views and folders. Counts and view content don’t always update at the same time.

Refresh view automatically

If auto-refresh is available for your account, it keeps the view results updating while you work.

Good to know:

• Auto-refresh is meant to keep the list current, not to interrupt what you’re doing.

• If you’re mid-action (selecting tickets, reviewing a preview, typing), it’s still worth doing a manual Refresh this view after you finish, if you need to confirm the latest state.

(Admins can configure whether auto-refresh control appears or not.)

Wrap text in table

Wrap text controls how long fields display in the ticket list.

• On: you’ll see more of long subjects or fields, but rows get taller.

• Off: the list stays compact, but long text truncates.

Use whatever makes scanning easier for your team.

Unread tickets only

Unread is a focus tool to help you spot what needs attention.

• Turn it on when you want the view to show only tickets that have unread updates for you.

• Turn it off to go back to the full list.

Unread behavior depends on how your account is set up and how unread is tracked, so if something feels off, check the unread settings section later in the guide.

Manage views

Most view management actions live in the view header (Options / kebab menu) and others in the right-click / context menu on a view in the List. What you see can vary a bit depending on your role and what your admin allows.

Favorite

Favoriting keeps a view within easy reach.

• Add a favorite to make it appear in Favorites in the List.

  

  

• Remove it any time. This won’t change the underlying Zendesk view, it only changes your shortcuts.

  

Tip: Favoriting is best for a small set of daily views so Favorites stays quick to scan.

Set as Home view

Sets the view as your Home view.

• Once set, clicking Home takes you straight back to that view.

  

• If your Home view is also a favorite, it can show in both places. That’s normal.

  

Export as CSV

Exports the tickets currently shown in the view to a CSV.

Good to know:

• What gets exported depends on how exports work in your build (for example, visible columns vs a default set).

• Filters you’ve applied may affect what’s exported.

Extra view settings

Extra view settings are per-view controls for how the ticket list is displayed and sorted. They’re useful when one view needs a different layout than your global defaults.

What you can set here:

Tickets per page
Set how many tickets to show per page for this specific view (5–200). If you leave it blank, Lovely Views uses your global default.

Group by
Group the ticket list by a field (for example, Submitter). You can also choose Ascending or Descending.

Order by (sorting)
Choose the main sort order for the view, plus up to two extra sort levels (Order by (2) and Order by (3)). Each sort level can be set to Ascending or Descending.

Rename

Renames the view label you see in Lovely Views. Rename is useful for cleaning up naming conventions or making views easier to scan.

If you’re renaming to standardize team naming:

• Start with the “what” (for example: New tickets, Waiting on customer, Urgent follow-ups).

• Avoid overly long labels. If it wraps or truncates, it’s doing too much.

Move to

Moves the view into a different folder (or subfolder).

• Use this when you’re reorganizing your Views section so the list stays usable.

• If you can’t move a view, it’s usually a permissions limitation.

Edit

Opens the view’s configuration so you can adjust what it contains.

A couple notes:

• Editing a shared view affects the view definition on Zendesk, so it is an admin-level action.

• If you’re editing a saved Seek search that’s opened as a view, this takes you into the Seek-style editor for that saved search.

Clone

Creates a copy of the view so you can make a variation without starting from scratch.

Use it when:

• you want “the same view, but with one extra condition”

• you’re making a personal version of a shared view (if your workflow supports that)

Delete

Deletes the view.

• This is a destructive action. If you don’t see Delete, that’s usually intentional (for example, agents not having the Delete option for shared views).

• If you delete something by mistake, you may need an admin to restore it (if restoration is possible in your Zendesk setup).

Show standard view

Shows the original Zendesk view in the standard Zendesk interface.

Use it when:

• you want to compare behavior

• you’re troubleshooting something that might be Zendesk-side

• you need to double-check a view rule or permission in the default UI

This doesn’t change anything, it’s just a quick way to jump to the Zendesk version of the same view.

FOLDERS

Folders are how you keep the Views section readable once your team has more than a handful of views. Think of them like a simple filing system: a few clear buckets, with subfolders only where it actually helps.

Expand and collapse folders

Folders can be expanded to show what’s inside, or collapsed to reduce clutter.

• Expand a folder to see its subfolders and views.

  

• Collapse it to shorten the list and focus on what you need right now.

  

• If you’re searching in the List, Lovely Views may auto-expand folders to show matching results.

  

• You can expand all folders within a section to see their contents at a glance. This is useful if you have multiple nested views and want to access them quickly without clicking each folder individually.

  

• You can also collapse all folders within a section. This closes all expanded folders keeping your list compact and organized. This helps reduce clutter when working with a large number of views.

• 

Create and manage folders

Use folders to group views by how your team actually works, not by every tiny category.

Common folder approaches that stay usable:

• by team (Support, Billing, Escalations)

• by workflow stage (New, Waiting, Follow-ups)

• by priority (Urgent, Today, This week)

Tip: If people don’t agree where a view belongs, that’s often a sign the folder structure is too detailed.

Move views into folders

When you move a view, you’re just changing where it sits in your folder structure.

• Use Move to from the view menu.

• Pick an existing folder, or create a new folder when it genuinely adds clarity.

• If a view “disappears,” it’s usually been moved into a collapsed folder (search the List to find it fast).

Merge folders

Merging is useful when you end up with two folders that are basically the same thing.

• Choose the folder you want to keep.

• Merge the other folder into it.

• Subfolders and views should end up under the surviving folder.

Best practice: Merge early. A tidy structure beats “we’ll clean it up later.”

Rename folders

Renaming is the quickest win for readability.

For folders:

• Keep names short and scannable.

• Use the same style across folders (for example, all nouns or all verb phrases).

Folder best practices

A folder structure that stays useful usually follows these rules:

• Keep it shallow: 1–2 levels deep is plenty. Subfolders are fine, but don’t build a maze.

• Aim for “scan speed”: If you can’t find your view in 2–3 seconds, simplify.

• Limit “misc”: If a folder becomes a dumping ground, split it or rename it into a real category.

• Agree on ownership: If your team has lots of view editors, decide who’s responsible for keeping folders tidy.

• Use Favorites for exceptions: If a view is important but doesn’t fit neatly anywhere, favorite it instead of forcing the folder structure.

If your team’s view list has grown messy over time, start by merging duplicate folders and renaming the top-level folders. You’ll feel the improvement immediately, even before you touch any individual views.

BOOKMARKS

A private “save for later” list, so you can keep triage moving without losing track of tickets.

Where to find Bookmarks

You can open Bookmarks in a few places, depending on where you’re working:

• Main workspace (opened from Zendesk’s left sidebar icon): click the Bookmarks tab in the tabs row.

  

• Topbar panel (opened from Zendesk’s topbar icon): click the Bookmarks tab/icon in the panel.

  

• From the List: open Extra, then select Bookmarks.

  

What Bookmarks shows

Bookmarks is your personal follow-up list.

It shows tickets you’ve bookmarked so you can quickly jump back to them later, without needing to remember ticket IDs or keep tabs open.

A few important notes:

• Bookmarks are private. Other agents won’t see what you’ve bookmarked.

• Bookmarking doesn’t change the ticket. It won’t add tags, update fields, or notify anyone.

• Bookmarks can disappear if the ticket changes in Zendesk, like if it’s merged, deleted, or you no longer have access.

Ways to bookmark

You can bookmark a ticket from a few places, depending on what you’re doing at the time.

Topbar Bookmark button

Use this when you’re already looking at a ticket (or you’ve selected one) and want the fastest “save for later” option. Admins may disable this feature.

Tip: If you bookmark something by accident, hit the same button again to remove it.

Sidebar Bookmark button

If your build shows Lovely Views actions in the Zendesk sidebars, you may also see a Bookmark option there, usually when you’re viewing a ticket.

This is handy when you’re working from the standard Zendesk ticket view and want to bookmark without switching tabs.

View Bookmark button

When you’re scanning tickets in a view results list, you can bookmark straight from the ticket row (where the bookmark control is shown).

This is ideal when you’re triaging and want to flag a few tickets to come back to later, without opening each one.

Preview Bookmark button

When you’re using ticket preview, you can bookmark from the preview actions (where those controls are shown).

This is ideal when you want a bit more context than the row shows, but you still don’t want to fully open the ticket.

Bulk bookmarking

If bulk edit has been enabled by your admin, you can bookmark multiple tickets at once.

Typical flow:

1. Select multiple tickets in a view (checkboxes).

2. Choose Bookmark from the bulk actions.

3. Those tickets show up in Bookmarks.

Remove bookmarks

You can remove a bookmark the same way you added it:

• Click the Bookmark control again (topbar, sidebar, row icon, or preview action).

  

• If you bookmarked in bulk, you can also bulk remove bookmarks from the bulk edit menu.

  

Search and sort in Bookmarks

Bookmarks includes tools to help you find what you need quickly, especially when your list grows.

Common things you can do here:

• Search within Bookmarks to filter down the list (for example by subject or ID).

  

• Expand or collapse ticket records (via topbar).

Refresh behavior in Bookmarks

Bookmarks usually updates as you bookmark or remove bookmarks, but there are times you may need to refresh the list, like:

• you bookmarked tickets in another tab and don’t see them yet

• tickets were merged or deleted in Zendesk and the list needs to catch up

• you changed accounts, permissions, or session state and the list looks stale

Use the reload/refresh control in Bookmarks to fetch the latest state.

Show button in the top bar panel

If your team wants agents to bookmark the currently viewed ticket from the top bar panel header, enable:

Admin > Bookmarks > Bookmark button in topbar

This shows a bookmark button in the topbar header, so agents can view and change the bookmark status of the currently viewed ticket.

ACTIVITY

Activity is your “recently opened” area in Lovely Views. Use it when you need to jump back to tickets you were just working on, without hunting through views or keeping extra tabs open.

What Activity shows

Activity helps you keep track of what you’ve been working on recently.

It shows tickets you’ve opened and viewed so you can jump back quickly when you’re bouncing between issues, waiting on replies, or checking multiple tickets for the same customer.

A few things to know:

• Activity is personal to you. It reflects your own recent ticket activity.

• It’s meant to be a “recently used” list, not a shared queue like a view.

• If a ticket is merged, deleted, or you lose access to it, it may disappear from Activity or show as unavailable.

Search and sort in Activity

Activity includes quick tools to help you find something you just had open.

Common things you can do here:

• Search within Activity to narrow the list (for example by subject or ticket ID).

  

• Group tickets ("ticket tabs" or currently open tickets vs "previously viewed tickets").

  

• Expand or collapse ticket records so you can scan more items at once, or open them up for more detail.

  

   

Enable or disable Activity

Activity can be turned on or off in Admin > Activity.

Turn this on to show the Activity tab and start tracking tickets you currently have open and previously viewed, or off to remove the tab.

SEEK

Need to find something fast, or build a search you’ll reuse? That’s what Seek is for. Seek is Lovely Views’ advanced search tool. Use it when a standard view isn’t flexible enough.

Seek lets you build searches using combinations of things like:

• ticket fields (including custom fields)

• tags

• requester, organization, assignee

• groups, brands, forms

• status, type, priority

• dates and “updated/created” style filters

• keywords (subject and conversation text)

You can use Seek for one-off digging, or build searches you’ll want to reuse.

Open Seek

You can start Seek in a few places:

• New search (topbar button): starts a fresh search.

  

• Seek tab: opens Seek in its dedicated workspace.

  

• Seek section in the List: this is where you’ll see:

  • the default template

  • any saved templates

  • any temporary search tabs you’ve opened (these can disappear after a reload)

When you run a search, you’ll see results right away and can keep working without leaving Lovely Views.

Seek setup and usage

Use the Seek user guide for information on:

• building searches from scratch

• templates (create, save, edit, manage)

• choosing conditions and field behavior

• saving searches for reuse

ADMIN

Admin is where you control how Lovely Views looks and behaves for you, and (if you’re an admin) what’s available to your team. It's also your central hub for app information, announcements, and updates.

About/News is the default page that first appears, and you can select and open up the other pages via the menu on the left.

There are two main sections:

• Personal preferences (admin and agent): your own setup (things like color scheme and how Lovely Views behaves).

  

• Preferences (admin only): team-wide controls (visibility, guardrails, and what actions are available).

  

About/News

This area is for quick product info, including:

• what version you’re running

  

• Lovestock & Leaf resources (support, docs, and related resources)

  

• Zendesk links

  

• the latest Lovestock & Leaf updates, with the most recent news showing at the top

  

• Lovely Views articles and announcements

• Lovely Views release notes 

• any known Lovestock & Leaf issues or incidents and their causes, along with status updates and date and time of fix

  

New settings

This is the “recently added” area. If you’ve just updated Lovely Views and something feels different, check here first.

It’s also a good place to confirm what’s new in your build before changing other settings.

PERSONAL PREFERENCES

These settings affect your Lovely Views experience only. They’re typically tied to the browser/device you’re using, so you may notice differences between (for example) Chrome vs Safari, or laptop vs another machine.

Common things you’ll control here:

• what the interface shows by default

• how return to Lovely Views behaves

Display

Use Display to control how Lovely Views looks for you.

These settings are personal and apply only to:

• your user account

• the browser + device you’re currently using

If you use Lovely Views in another browser or on another device, you’ll need to set your Display preferences there too.

Apply appearance settings to

Choose whether you want one display setup everywhere, or different setups in different parts of Lovely Views.

• All locations: One set of display settings applies across Lovely Views.

• Individual locations: You can control the look and feel separately for the topbar and the navbar.

If you select Individual locations, you’ll see separate settings for the Topbar and Navbar.

Topbar appearance

Controls whether the topbar follows Zendesk’s theme or uses a forced mode.

• Match Zendesk Support Zendesk: Topbar follows Zendesk (light/dark).

• Light mode: Forces the topbar into light mode.

• Dark mode: Forces the topbar into dark mode.

Topbar dark mode theme

Controls which dark theme style the topbar uses when Topbar appearance is set to Dark mode (or when you’re matching Zendesk and Zendesk is in dark mode).

• Darker dark: Highest contrast, darkest background

• Standard dark: Default

• Lighter dark: Softer dark background

Navbar appearance

Same idea as Topbar appearance, but for the navbar.

• Match Zendesk Support: Navbar follows Zendesk (light/dark).

• Light mode: Forces the navbar into light mode.

• Dark mode: Forces the navbar into dark mode.

Navbar dark mode theme

Same idea as Topbar dark mode theme, but for the navbar.

• Darker dark

• Standard dark

• Lighter dark

Tip: If you want Lovely Views to automatically follow your Zendesk theme, set Display to Match Zendesk Support, then choose your preferred Dark mode theme for when Zendesk is in dark mode.

Behavior

Behavior settings control small “how it behaves” details while you work in Zendesk.

Return to Lovely Views

When this is enabled, Lovely Views will try to automatically bring itself back into view when it makes sense, so you don’t have to keep reopening it.

When you might leave this on

• You work out of Lovely Views most of the day and want it to stay “present” as you move around Zendesk.

• You prefer less clicking between tickets, views, and the panel.

When you might turn this off

• You prefer to open Lovely Views only when you need it.

• You find it distracting if the app reappears while you’re focused elsewhere in Zendesk.

Tip: If Lovely Views isn’t showing where you expect, double-check this setting first, especially if you recently changed browsers or devices.

Admins can make this setting available/unavailable for agents via Preferences > General.
 

Auto-open on startup

Show Lovely Views app when Zendesk starts up, so it's the first thing you see.

Admins can make this setting available for agents via Preferences > General and selecting Allow agents to choose.

PREFERENCES

Admin preferences control what Lovely Views looks like for your team, what actions are available, and how much flexibility agents have.

If you’re not an admin, you’ll still be able to open Admin, but you’ll only see the sections meant for personal preferences and general info.

General

General settings control the overall Lovely Views setup for this Zendesk instance (things like which version runs, where the app appears, and a few global behaviors). Role and group access is handled in Zendesk Admin Center, not here.

Title

This allows you to customize the name of the Lovely Views app as it appears within your Zendesk environment. This feature is particularly useful for branding purposes.

App version

Choose which Lovely Views version this installation should run (for example 4.x).
Useful if you’re switching between major versions for rollout or testing.

Good to know: after changing the version, you typically need to hard refresh Zendesk for the change to fully apply.

Auto-open on startup

Controls whether Lovely Views opens automatically when Zendesk loads.

• Never
  Lovely Views does not open automatically. Agents open it manually when needed.

• For all agents
  Lovely Views opens automatically for everyone when Zendesk starts.

• Allow agents to choose
  Each agent can decide for themselves whether Lovely Views opens on startup.

When this is useful

• Enable auto-open if Lovely Views is your team’s primary workspace.

• Leave it off if agents only use it occasionally or prefer Zendesk’s default views first.

Auto-open default setting for agents

This setting only appears when Allow agents to choose is selected for Auto-open on startup.

Choose whether auto-open feature is disabled or enabled for all agents by default.

Use 12 hour (AM/PM) for times

Switches time formatting between 12-hour (AM/PM) and 24-hour time. This option caters to personal or regional preferences for time format, ensuring that agents can work with the time display that is most intuitive and clear for them. When this setting is activated, all time-related information presented in Lovely Views will adjust to the 12-hour format by default.

Disable keyboard shortcuts

Turns off Lovely Views keyboard shortcuts (if your team is accidentally triggering them, or if they conflict with other tools).

Show day of the week in dates

Adds the weekday to dates (for example, “Mon”, “Tue”) so it’s easier to scan timelines at a glance.

Enable app on user sidebar

Shows Lovely Views in the user sidebar (when viewing a user profile).
Turn this on if your team uses Lovely Views tools while checking user context.

Enable app on organization sidebar

Shows Lovely Views in the organization sidebar (when viewing an org profile).
Turn this on if your workflows involve org-level context and navigation.

Always return to Lovely Views when all ticket tabs are closed

When enabled, closing the last ticket tab brings agents back to Lovely Views automatically (regardless of where that last ticket tab was opened from).
Turn this on if you want Lovely Views to be the “home base” after ticket work.

Return delay

This setting only appears when Always return to Lovely Views when all ticket tabs are closed is enabled.
You can set up a delay for the action, from 0 to 8 seconds.

Return to Lovely Views workaround

A safety switch for Zendesk layouts where “return to Lovely Views” can be unreliable. When enabled, Lovely Views adds a small delay before returning.

Tip: only enable this if agents are actually experiencing the “doesn’t return” issue.

Option to disable “Return to Lovely Views”

Makes “Return to Lovely Views” available as a personal preference for agents (so they can enable or disable it themselves).

• On: agents get their own toggle (in their personal preferences).

• Off: the behavior is controlled only by the admin setting.

Disable “Return to Lovely Views” on Play

This setting only appears when Option to disable “Return to Lovely Views” is enabled.

If an agent clicks Play in Lovely Views, the “Return to Lovely Views” action is automatically disabled.
This helps avoid the app constantly pulling focus back while the agent is intentionally working through tickets using Play.

List

List settings control how views, folders, and personal sections are structured and shown inside Lovely Views. These options let admins fine-tune navigation so agents can scan, find, and switch views faster.

Additional view folder separator

Defines the character used to create folder structures from view names.

By default, Lovely Views recognizes :: as a folder separator.
Example:
Support :: Billing :: Open tickets

You can add an additional separator, such as /, if your team prefers a different naming style.

Good to know:

• Both separators will be recognized if an additional one is set.

• This only affects how views are grouped in Lovely Views.

• Standard Zendesk views will still show the full name as text.

'Suspended tickets' view available

Controls who can see the special Suspended tickets view in Lovely Views.

Options:

• To admins and agents that have all tickets access

• To only admins

• To nobody

This does not change Zendesk permissions. It only controls visibility of this view inside Lovely Views.

'Deleted tickets' view available

Controls who can see the special Deleted tickets view in Lovely Views.

Options:

• To admins and agents that have all tickets access

• To only admins

• To nobody

This does not change Zendesk permissions. It only controls visibility of this view inside Lovely Views.

Disable the Misc folder

By default, views that don’t match any folder structure are placed into a Misc folder.

When enabled:

• The Misc folder is removed.

• Ungrouped views appear at the root level instead.

Rename the Misc folder

Allows you to change the name of the Misc folder to better match your team’s terminology.

Example:

• “Other”

• “Unsorted”

• “General”

Only applies if the Misc folder is enabled.

Display the Misc folder / root level views at bottom

Controls where the Misc folder or root-level views appear in the list.

When enabled:

• Misc or root-level views are shown at the bottom of the list.

When disabled:

• They appear in the default position based on sorting.

Folder arrangement

Controls how folders are positioned relative to views inside the same parent folder.

Options:

• Folders mixed in with the views

• Folders all at the top

• Folders all at the bottom

This helps teams that prefer a strict folder-first or view-first layout.

Rename the Personal section

Allows you to rename the Personal section shown in the List.

This section contains personal views, searches, and items created by the agent.

Example alternatives:

• “My work”

• “My views”

• “Personal queue”

Place Personal section below Views

Controls whether the Personal section appears above or below shared Views.

When enabled:

• Personal appears below Views.

When disabled:

• Personal appears above Views.

This is helpful if you want shared team views to take priority.

Disable the My profile folder

The My profile folder contains four built-in profile views:

• Requested

• Assigned

• CC’d

• Followed

When enabled:

• The My profile folder is hidden from the List.

This does not remove the views themselves, only their grouped display.

Rename the My profile folder

Allows you to rename the My profile folder to better match your internal language.

Example:

• “My tickets”

• “My queue”

Only applies if the My profile folder is enabled.

Enable Download view list CSV feature

Controls who can export the visible view list and counts as a CSV file.

Options:

• All admins & agents

• Admin only

• Disabled

This export reflects what the user can currently see in the List.

Enable Show only my views toggle

Adds a Show only my views toggle to the List menu.

This allows agents to quickly hide shared views and focus only on their own.

Important notes:

• Always available for admins.

• For agents, availability can be restricted by role or group.

• The toggle appears in the three-dot menu.

Enable favorites

Allows agents to mark views or searches as favorites for faster access.

When enabled:

• Agents can star views and searches.

• Favorites appear in quick-access locations depending on layout.

When disabled:

• Favorite controls are hidden.

View

View settings control how views behave in Lovely Views, including how many tickets load, whether previews are available, how ticket rows are displayed, auto-refresh behavior, unread highlighting, and a few quality-of-life controls for agents.

Tickets per page

Sets how many tickets show per page in the view ticket list.
Range: 5 to 200
Default: 30
Higher numbers are better for scanning and bulk work, but can feel heavier in very busy views or on slower devices.

Enable tickets per page customization

When enabled, each agent can choose their own “tickets per page” value (instead of everyone using the admin-set value). This is handy if your team has mixed preferences or performance varies across devices.

Show ticket preview

Controls whether ticket previews are available when hovering over a ticket in a view. If your team triages heavily from views, this is usually worth keeping on.

Options:

• All admins & agents

• Admins only

• Disabled

Enable enhanced ticket previews

Enables richer previews that show more context and can surface extra details and actions, so agents can understand the ticket faster without opening it fully. 

If you are troubleshooting preview performance or want a simpler experience, try turning this off.

Default: On

Conversation summaries in previews

Shows an AI-generated summary in the ticket preview.

This is best treated as a quick snapshot. Agents should still rely on the actual ticket content for decisions and accuracy, especially in complex tickets.

Default: On

Number of lines to display per ticket row

Controls text wrapping in ticket rows:

• 0 = unlimited lines (wrapping allowed)

• 1 = single line (no wrapping, long lines truncated)

Single line keeps lists dense and scannable. Unlimited lines helps teams who rely on subject text for context.

Show First button

Shows a “First” button in the view controls.

Show Go to Play button

Shows a “Go to Play” button in the view controls.

If your team does not use Play, turning this off reduces clutter.

Enable Guided mode

Designed for restricted workflows (for example, agents whose role is set to Play views only). When enabled, those agents may not be able to see the full list of tickets in the view.

This can be useful for onboarding or tightly controlled workflows, but will confuse teams if enabled unintentionally.

Show user profile pic in views

Shows the user profile picture next to a user’s name where applicable.

Helps quick recognition but slightly increases visual noise.

Disable enhanced sorting (experimental)

When enabled, Lovely Views uses Zendesk’s default sorting method instead of enhanced sorting.

This is a good troubleshooting switch if the ordering in Lovely Views does not match Zendesk for a specific view, or if a complex sort/group setup behaves unexpectedly.

Display description

Controls how view descriptions are displayed (if a description exists).

Options:

• Hide

• Show (shows under the view name)

• Show in tooltip (adds an info icon and shows the description on hover)

“Show in tooltip” is usually the best balance. It keeps the list clean but still gives helpful context when needed.

Auto-refresh rate

How often the current view refreshes.

Options: 1, 2, 3, 4, 5 minutes

Default: 3 minutes

Faster refresh can feel more live, but it can be distracting and create extra load.

Auto-refresh count rate

How often view counts refresh.

Options shown: 1, 3, 5, 10 minutes

Default: 3 minutes

If your team relies on counts for routing work, a shorter interval helps. Otherwise, keeping this moderate avoids unnecessary churn.

Cache time view count

How long view counts are cached.

Options shown: 1, 3, 5, 10 minutes

Default: 5 minutes

Higher cache values reduce load but counts may feel less up-to-date.

Display auto-refresh control

Shows an auto-refresh control next to the view name so agents can toggle auto-refresh.

Useful for teams who sometimes want auto-refresh (triage) and sometimes want it off (focus work).

Highlight unread tickets

Highlights tickets that are unread in the view.

This feature requires a hidden “unread tickets” data field to store unread state per user. 

Unread mode setting

Controls when a ticket becomes “unread”.

Options:

• Any change: ticket becomes unread when any change happens (including non-comment updates)

• Comment only: ticket becomes unread only when a new comment arrives

“Comment only” is usually less noisy. “Any change” is better if your team wants to notice all activity, not just replies.

Use Zendesk tag sorting method

When grouping or sorting with dropdown fields, use Zendesk’s sorting method for consistent ordering.

This is mainly about matching how Zendesk orders values so lists look familiar.

Default: On

Allow agents to close tickets

Allows agents to set tickets to Closed from preview and bulk edit (where available). Role/group restrictions can be applied.

Only enable this for roles/groups that should be allowed to close tickets, since Closed status often affects reporting and workflow.

Enable subject link

Makes ticket subjects clickable and supports right-click actions like “Copy link address.”

Turning this off makes subjects plain text, which reduces accidental clicks but also removes quick link sharing.

Selected tickets

These settings control what agents can do after selecting one or more tickets in a view (bulk edit behavior and merge behavior).
 

Disable bulk edit

When enabled, bulk edit won’t be available.

Useful if you want to prevent accidental mass changes.
 

Don’t change group default setting

Sets the default state of the “Don’t change group” option for the Assignee field in bulk edit (Checked/Unchecked).

Set to Checked if you want to reduce accidental routing changes during bulk updates.

Requester must be the same when merging tickets

When enabled, only tickets with the same requester can be merged (default: OFF).

Turn this on if your team has strict requester rules and wants to avoid merging unrelated customers into one thread.

Custom merge method

Controls how ticket data is copied into the new merged ticket:
Latest (default): copies ticket data from the most recently updated ticket
Rolling: copies from the least recently updated ticket, then replaces it as newer updates appear
None: no ticket data is copied to the new ticket

"Latest” is usually the safest default. “None” is useful if you want the merge to be more “neutral” and avoid carrying over fields/tags unintentionally.

Force custom merge method onto agent

When enabled, agents can’t choose their own merge method.

Turn this on if you want consistent merge outcomes across the team.

Add temporary tag while merging

Adds a temporary tag (merge_underway) to the new ticket while the merge is in progress, then removes it when finished. The joined_comments tag is always added immediately.

This is mainly for admins who want to prevent extra trigger notifications during merges (for example, by adding trigger conditions that behave differently when merge_underway is present).

Agent comments are internal by default

When enabled, the bulk edit dialog opens with the comment box set to Internal note. When disabled, default comment visibility follows your Zendesk setting “Agent comments via web are public by default.”

Strongly recommended if your team mostly adds internal notes during bulk updates. It reduces the risk of posting an internal message publicly, but agents should still double-check before submitting.

Enable Select all pages feature

Allows selecting all tickets across pages after selecting tickets. Options: All admins & agents, Admin only, Disabled.

This can enable very large bulk actions. If you enable it, consider restricting it to admins.

Allow to change requesters

Controls who can change requesters (Admins only / All admins & agents / Disabled).

This is a high-impact action. Most teams keep this to Admins only unless there’s a clear business need.

Bookmarks

These settings control small bookmark-related UI options in Lovely Views.

Bookmark button in topbar

Adds a Bookmark button to the topbar header so agents can check and change the bookmark status of the ticket they’re currently viewing.

When you’d use this: Turn it on if your team keeps Lovely Views pinned in the topbar and bookmarks tickets often. Turn it off if you want a cleaner topbar or your team mainly manages bookmarks from the view or via ticket sidebar.

Activity

These settings control what appears in the Activity area and whether agents can see signals like “someone else is viewing this ticket.”

Activity settings control how the Activity tab behaves for agents and what it can display.

Show Activity tab in topbar

Shows the Activity tab in the topbar so agents can see tickets they have open now and recently.

Show agent collision indicators

Shows an eye icon in ticket lists when another agent is viewing the ticket. (Uses the refresh rate below.)

Great for reducing duplicate replies and “two agents working the same ticket” situations.

Agent collision refresh rate

How often collision status is refreshed (minimum: 5 seconds).

Lower values feel more real-time but increase API calls. If agents see Zendesk “Rate limit reached” warnings, increase this value.

Show My ticket tabs view

Adds a view in the Extra section that shows all tickets currently being viewed by the agent.

Show Current ticket activity view

Adds a view in the Extra section that shows user activity on tickets. Admins have access by default unless restrictions are set.

You can restrict this setting by Role(s) and/or Group(s) if you only want certain users to see broader activity.

Ticket sidebar

These settings control whether Lovely Views can be used in Zendesk’s ticket sidebar, and whether agents get ticket navigation buttons there (so they can move through tickets without going back to the list).

Enable app on ticket sidebar

Turns the Lovely Views app on or off in the Zendesk ticket sidebar. If this is off, agents will not be able to use Lovely Views from the ticket sidebar.

Always show ticket nav in ticket sidebar

Shows the ticket navigation controls in the ticket sidebar.

If this is disabled, the navigation controls only appear when the ticket was opened using the First button.
(Ticket nav refers to the <<, <, >, and >> buttons.)

If agents often open tickets from lots of different places (search, links, native views), disabling “Always show ticket nav in ticket sidebar” can reduce confusion, because navigation will only appear when Lovely Views has a clear “view context” (after using First).

Enable First button

Shows the << button in the ticket sidebar. Opens the first ticket in the current view.

Enable Previous button

Shows the < button in the ticket sidebar. Opens the previous ticket in the current view.

Enable Next button

Shows the > button in the ticket sidebar. Opens the next ticket in the current view.

Enable Last button

Shows the >> button in the ticket sidebar. Opens the last ticket in the current view.

Backup and restore

Use this section to export your Lovely Views configuration as JSON (backup) and re-import it later (restore). This is especially useful before big changes, troubleshooting, or moving configuration between environments.

Backup

Copy all JSON shown in the Backup field and save it somewhere safe (plain text storage). If your configuration is ever lost or corrupted, you can restore it by pasting this JSON into the Restore field.

Restore

Paste a previously saved JSON configuration into the Restore field and click Restore.
Important: Restoring overwrites your current configuration. Always take a fresh backup first so you can roll back if needed.

Only restore JSON you trust. If the JSON is incomplete or from a different setup/version, you may end up with missing or unexpected settings.

Where preferences are stored

Lovely Views saves user preferences so things like Favorites, Home, and other personal settings persist across sessions.

In most accounts, preferences are stored using Zendesk custom objects created by the Lovely Views app.

What to know:

• You may notice a Lovely Views custom object in Zendesk Admin Center > Objects and rules > Custom objects because custom objects are visible in the Zendesk admin UI.

• The app uses custom object records to store user preference data reliably.

• Each custom object record has a size limit, so preference data may be stored in multiple records (“chunks”) behind the scenes.

• Deleting these records can reset user preferences.

If custom objects aren’t available in an account, Lovely Views falls back to storing preferences using the legacy user data storage method.

EXPORT AND REPORTING

Lovely Views lets you export a simple CSV of your view list. This is mostly useful for housekeeping, audits, and planning changes to your view structure.

Export as CSV

Use this when you want an offline copy of your current view structure, for example:

• documenting your folder and view setup before a cleanup

• reviewing naming consistency across teams

• sharing a snapshot with someone who isn’t in Zendesk

• spotting duplicates or “old” views that should be archived

What happens:

• Lovely Views sends a CSV file to your email.

  

• The export reflects the view list that Lovely Views can currently see at the time you download it.

What’s included (and what’s not)

Included:

• your folder structure (folders and subfolders)

• view names

• basic structure/ordering information (enough to understand how the list is organized)

Not included:

• the underlying Zendesk view definitions (conditions, columns, sorting, permissions)

• ticket results from inside a view

• personal items that aren’t part of the exported view list (for example, personal-only lists or per-user data)

• anything tied to live state (like current ticket counts)

If you need the actual view logic (conditions/columns), that’s still managed through Zendesk’s view configuration.

Exporting issues

Nothing downloads

• Try again after a hard refresh of Zendesk.

• Check whether your browser blocked the download (some settings/extensions will do this).

The list looks outdated

• Reload Lovely Views, then export again.

• If you made changes very recently, make sure Lovely Views has picked them up before exporting.

Folders/views seem missing

• Confirm you have access to those views in Zendesk (permissions, roles, groups, brands).

• If the view doesn’t appear in Lovely Views, it won’t appear in the export.

CSV formatting looks messy

• Open the file in Google Sheets or Excel (some preview tools display CSVs oddly).

• If names contain commas, that can make the preview look strange, but Sheets/Excel usually handles it correctly.

TROUBLESHOOTING

This section covers the most common “wait, why isn’t this doing what I expect?” moments in Lovely Views, plus what to check first.

Counts not changing when expected

If the number next to a view or folder doesn’t change right away, it usually means you’re looking at a count snapshot, not live results.

Try this:

• Click Refresh counts on the section, folder, or view you care about.

• If you need the ticket list itself to update (not just the number), open the view and use Refresh this view.

Also worth checking:

• If tickets were merged, deleted, or permissions changed, counts can lag until you refresh.

• Some updates in Zendesk aren’t immediately reflected until a refresh (especially if the ticket changed outside what you’re currently looking at).

Refresh counts vs Refresh this view

These do different jobs:

• Refresh counts updates the numbers you see in the List (folders, sections, views).

• Refresh this view refreshes the ticket results inside the open view.

Common example:

• You see “12” next to a view (count), but the list inside the view still shows the older set of tickets.
  Use Refresh this view.

Missing views or folders after search

If you search in the List and something “disappears,” it’s usually one of these:

• The search is filtering the List and hiding anything that doesn’t match.

• The item is in a collapsed folder you haven’t expanded yet (search will usually auto-expand matches, but not always perfectly if the structure is large).

• You don’t have access to that view in Zendesk (role/group/brand permissions).

Try:

• Clear the search box completely.

• Collapse and re-expand the relevant folder.

• Reload Lovely Views if you suspect the list didn’t sync properly.

Home/Favorites oddities

Things that often surprise people:

• Home is a “default landing spot.” Favorites are a set of shortcuts. They’re related, but not the same thing.

• A view can be both Home and a Favorite. That’s normal.

• If Home “looks wrong,” set it again from the view menu, then reload once to confirm it stuck.

If Home keeps resetting, jump to Preferences not saving below.

Bookmarks not showing expected tickets

If a ticket you bookmarked isn’t showing in Bookmarks:

• The ticket may have been deleted or merged in Zendesk.

• Your access may have changed (permissions/brand/group), so Lovely Views can’t load it anymore.

• Bookmarks are personal, so make sure you’re checking under the same user.

Try:

• Use the Bookmarks search to look it up by ID/keyword.

• Reload Bookmarks (or reload Lovely Views) and check again.

Activity not showing expected tickets

Activity is meant to help you get back to what you were just working on.

If it feels incomplete:

• Activity only shows tickets you’ve recently opened/viewed (it’s not meant to be a full audit log).

• If you’re signed in on multiple devices/browsers, Activity may look different depending on where you were working.

Try:

• Use the Activity search.

• Reload Lovely Views.

Preferences not saving

If your Favorites/Home/settings keep disappearing, it usually means your preferences aren’t being saved successfully.

First, try:

• Hard refresh Zendesk, then set the preference again.

If it still doesn’t stick, the most common causes are:

• A temporary save failure (network or Zendesk side)

• The account is using a storage method that isn’t currently available

Where preferences are stored

Lovely Views saves user preferences in one of two places:

• Custom Objects (preferred): saved in a Lovely Views custom object record (and split into chunks when needed).

• Fallback: if Custom Objects aren’t available, Lovely Views uses the user data field.

Important: deleting Lovely Views Custom Object records can reset user preferences.

Common Zendesk limitations

Lovely Views builds on Zendesk rules. It does not override Zendesk behavior such as:

• who can see which views/tickets (roles, groups, brands)

• automations, triggers, SLAs, and view definitions

• what happens when a ticket is deleted or merged

If something is permission-based or automation-based in Zendesk, Lovely Views will follow it.

FAQs

Quick answers to common questions about how Lovely Views behaves, what to expect, and why something may look different in your setup.

Are bookmarks private?

Yes. Bookmarks are personal to your user. They don’t change the ticket and don’t affect other agents.

Why are some actions missing for me?

Most actions are controlled by:

• your Zendesk permissions (role/group/brand)

• what your admin has enabled for your role/group in Lovely Views preferences.

Does Lovely Views change my Zendesk views or permissions?

No. Lovely Views uses your existing Zendesk views and permissions. It changes the workspace experience (navigation, layout, actions), not Zendesk’s underlying rules.

Why does a saved Seek search open like a view?

Because saved Seek searches are meant to behave like repeatable work queues. When you select one from the List, it opens in the Views tab as a ticket results list. You can also edit it like you would in Seek.

Where are my preferences saved?

Lovely Views saves preferences using Custom Objects where available. If Custom Objects aren’t available, it falls back to the user data field.

If preferences aren’t sticking, see Preferences not saving.

GETTING SUPPORT

If you get stuck, the fastest path is to send us a few key details up front. That way we can reproduce what you’re seeing instead of going back and forth. Reach out to our support team at support@lovestockleaf.com. 

What to include in your support request

• What you were trying to do (1–2 sentences)

• What happened vs what you expected

• Where you were working

  • Navbar (left sidebar) or Topbar (right-side panel)

  • Which tab: List, Views, Seek, Bookmarks, Activity

• Which item it affected

  • View name (and folder path if relevant)

  • Ticket ID(s) if it’s ticket-specific

• Whether it affects one person or multiple people

• Your browser and version

  • Example: Chrome 123, Safari 17, Firefox 122

• Approximate time it happened (and your timezone)

• Any steps you can repeat (even if it’s “happens every 2–3 times”)

Screenshots and recordings

• A screenshot showing the tab + the action you clicked

• A short screen recording if it’s timing-related (refresh, counts, “disappearing” items)

• If it seems like a saving issue, include the moment you set the preference (Home/Favorite/etc.) and what happens after a reload

If it’s urgent

If it’s blocking work (can’t load views, actions not working, data not saving), say that clearly and include:

• how many agents are impacted

• whether it’s total outage or partial

• any workaround you’ve found (even if it’s “reload fixes it for 5 minutes”)

Quick self-check

• Hard reload Zendesk (not just refresh)

• Try a different browser or an incognito/private window

• Confirm whether another agent can reproduce it

• If it’s permission-related, check whether the user’s role/group/brand access changed recently