Freshdesk Ticket Views Explained (Default, Shared & Custom)

The three kinds of view (and where they live)

Every ticket view in Freshdesk lives on the Tickets tab, and they're grouped into folders in the view switcher at the top-left of the ticket list. Per Freshworks' Understand the Ticket List View documentation, there are four folders:

• Default — the system views Freshdesk ships with, available to everyone.
• Personal — custom views you've built and kept to yourself.
• Shared — custom views someone has shared with all agents.
• Favourites — up to five views you've starred for one-click access.

That structure is the whole mental model. Freshdesk hands you a set of sensible defaults, you build your own on top, and you promote the useful ones to the whole team. Everything below is just filling in those three layers.

The default (system) views you already have

Before you build anything, it's worth knowing what's already there, because the defaults cover most of what a working agent needs day to day. Out of the box, Freshdesk's system views include:

1. New and my open tickets — the landing view most agents start on.
2. My Open and Pending Tickets — your active workload.
3. My Overdue Tickets — anything of yours past its SLA deadline.
4. Open Tickets in My Groups — the shared pool your team pulls from.
5. Urgent and High-Priority Tickets — the queue that shouldn't wait.
6. All unresolved tickets — the manager's-eye view of open work.
7. Tickets I raised, Tickets I'm mentioned in, Tickets I'm watching — your personal threads through the queue.
8. Spam and Trash — the two you rarely open on purpose.

These are read-only in the sense that you can't delete them, but you can open one and re-filter it on the fly — which is exactly how you build a custom view, as we'll see next.

Building a custom view with the filter panel

Here's the mechanism people most often get confused about. In Freshdesk you don't start from a blank "new view" form — you start from an existing view, open the filter/view builder panel, narrow the list until it shows what you want, and then save that as a new view. Per Freshworks' How do I create a custom ticket view guide, the flow is:

1. Go to the Tickets tab and open any view (the default New and my open tickets is fine).
2. Open the filter panel on the right and set your conditions.
3. Watch the ticket list update live as you filter.
4. Click Save as at the top of the page.
5. Name the view, choose its visibility, and save.

The filter panel is where the real power sits. You can slice on Agents and Groups (including Unassigned, which is how you build a triage queue), Priority, Source, Type, and Status, on any custom ticket fields you've created, on contact and company attributes, on the channel the ticket arrived through (Email, WhatsApp, Portal, Facebook, Instagram, Web Chat), and on date filters for Created, Closed, Resolved, and Resolution-due-by. Recent versions also expose a Sentiment filter so you can surface the frustrated conversations first. Layer a few of these and you get views like "unassigned WhatsApp tickets created today" or "high-priority tickets from VIP companies awaiting a reply."

Personal vs shared: the visibility choice

When you hit Save as, Freshdesk asks who the view is for, and this single choice is the difference between a personal shortcut and a team-wide standard:

• Just me saves it as a Personal view — it appears only in your Personal folder. Use this for the idiosyncratic slices only you care about.
• All agents saves it as a Shared view — it lands in everyone's Shared folder. Use this for the queues the whole team should work from the same way: the triage pool, the escalations lane, the VIP queue.

The reason to be deliberate here is consistency. If "unassigned tickets to be triaged" is a personal view that only one agent has, triage depends on that one person showing up. Promote it to a shared view and triage becomes a place everyone can stand. There's a related idea in Freshdesk's shared ownership model, where tickets shared with you and tickets you've shared out surface through their own views — so collaboration and views are tightly linked.

Layout and export: making a view actually usable

A view isn't just which tickets — it's also how they're presented, and Freshdesk gives you controls in the list header for that. You can switch the Layout between Card (the default, priority-forward look), Table (choose your own columns, with Contact and Subject pinned), and Inbox (an email-style reading experience). Table layout is the one power users tend to live in, because you can add exactly the columns your workflow needs and scan dozens of tickets at a glance.

Alongside layout sit the bulk action and Export controls. Select tickets with the checkboxes and you can bulk-update Status, Priority, or assignment across the whole filtered set — which pairs beautifully with a tightly scoped view. And once you've filtered a view down to the exact segment you care about, you can export it for reporting or a spreadsheet audit. A well-built view plus a bulk update is often the fastest way to clear a backlog category in one pass.

The honest limits — where a saved filter stops

Freshdesk's views are genuinely well-designed: fast, flexible, and free of the tag-soup that plagues other help desks. But it's worth being clear about what a view fundamentally is — a filter. It surfaces and sorts tickets; it does not work them. A view can put every unassigned WhatsApp ticket in front of you in priority order, but a human still has to open each one, read it, understand the intent, and write the reply.

A view also can't reason about content. It filters on structured fields — status, priority, group, channel, dates — so a ticket only lands in your "billing" view if it's already been tagged or typed as billing. It can't read a free-text message that never mentions the word "billing" and route it correctly on meaning alone. And because Favourites caps at five and view lists grow over time, big teams eventually accumulate dozens of overlapping views that no one fully trusts — a filter is only as good as the discipline behind naming and pruning it.

This is the seam where an AI agent layer fits, and it's worth understanding the broader category of AI agents for customer service before reaching for one. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace Freshdesk, its views, or your queue. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your views already organise. Where a view can only surface the unassigned-triage pool, Macha can read those tickets by intent and draft or post grounded replies — the practical mechanics of which we walk through in how to automate Freshdesk with AI. It can pull an order or account status through a custom tool that turns a REST API into something the agent can call, rather than leaving an agent to go look it up. And it pairs naturally with the reply infrastructure you already lean on, like your canned responses, by grounding answers in real context instead of a static snippet.

The clean division of labour: keep Freshdesk's views as the source of truth for how work is organised and prioritised, and layer an agent on top for the part a filter can't do — actually reading and resolving the tickets a view piles up. (To be precise: Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution or deflection — the pricing page breaks that down.)

FAQ

Where do I find ticket views in Freshdesk? On the Tickets tab. The view switcher at the top-left groups them into four folders — Default (system views), Personal (your own), Shared (team-wide), and Favourites (up to five starred views).

How do I create a custom ticket view? Open any view on the Tickets tab, use the filter panel to narrow the list to what you want, then click Save as at the top of the page, name it, and choose its visibility. You build from an existing filtered view rather than a blank form.

What's the difference between a personal and a shared view? When you save a view, Just me keeps it in your Personal folder (only you see it), while All agents promotes it to the Shared folder so the whole team can use the same queue. Use shared views for triage pools, escalations, and VIP queues.

Are custom views available on every Freshdesk plan? Custom views aren't available on the Sprout/Free tier, but they are on Growth, Pro, and Enterprise (and the classic Blossom, Garden, Estate, and Forest plans), as well as Freshdesk Omni. Confirm the exact behaviour against your own plan.

Can I add AI on top of Freshdesk views without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing views and queue — it doesn't replace them. It reads the tickets your views surface, drafts or sends grounded replies, and routes by intent, while Freshdesk stays the system of record for how work is organised.

Ready to let your agents clear the queue instead of just filtering it? Start a free trial of Macha and connect it to your Freshdesk in minutes.