A morning triage console for your unassigned Freshdesk queue

Build me a morning triage console my support team opens at the start of every shift to clear the unassigned Freshdesk queue in one pass. It is a working surface, not a report: everything a triager needs to route a ticket happens on this one screen.

The main view is the queue. Use Freshdesk Filter Tickets to pull open tickets that are either unassigned or have had no agent response yet, sorted oldest first. Each row shows the requester name and email, the subject, how long the ticket has been waiting since it was created, the current priority, the current group, and a short preview of the customer's first message. Pull the ticket body with View Ticket, or the first inbound entry from List Ticket Conversations, and truncate it to a couple of lines with the full text available on hover or in a side drawer. The age column is the anchor of the whole screen, so make it visually prominent.

Down the right side, show an agent load sidebar. Build it from List Agents and List Groups, and get each agent's current open ticket count by querying their open tickets with Filter Tickets. For every agent show their name, the group or groups they belong to, and their open ticket count, sorted with the busiest first. Anyone well above the team average gets a visual flag so the triager can see at a glance who is already buried before handing them more work. The sidebar is what makes this better than the native views: load and queue side by side.

From any row I can act without leaving the page. Give me an inline priority selector, a group picker populated from List Groups, and an owner picker populated from List Agents, each writing through Update Ticket and refreshing the row and the sidebar counts when it lands. I can also tick checkboxes on multiple rows, and a bulk action bar appears letting me apply the same priority or the same group to the whole selection through Bulk Update Tickets. That call runs asynchronously and returns a job to poll, so show a pending state on the affected rows and refresh them once the job finishes.

Add a Triage these button that acts on the selected rows and kicks off a background agent. For each selected ticket the agent reads the full thread with List Ticket Conversations, considers the subject matter against the group list and the current per-agent open ticket counts, and produces a proposal: a priority, a group, an owner, and a one line reason explaining the choice, for example that it is a billing question and that this agent has the lightest load in the billing group. It also drafts a suggested first reply to the customer and posts that draft to the ticket as an internal private note using Add Note to Ticket, marked private so only agents can see it, addressed to whoever ends up owning the ticket. The agent must never send a public reply to the customer and must never post a customer-visible conversation entry.

Every agent output is a proposal until a human accepts it. Proposals come back into the app and render on the matching row as a suggestion chip showing the proposed priority, group and owner plus the one line reason, with Apply and Dismiss buttons. Only when someone clicks Apply do you write the change through Update Ticket. Dismiss clears the suggestion and leaves the ticket untouched. While the background agent is running, show per-ticket progress so the triager knows which rows are still being worked on, and keep the rest of the console usable.

Whenever a ticket gets an owner, whether from the inline picker, a bulk update or an applied suggestion, notify the new owner in Slack. Match the Freshdesk agent's email to their Slack account with the Slack Bot Look Up User by Email operation, open a direct message with Open a Conversation, and send the message with the Slack Bot Send a Message operation. The message includes the ticket subject, the requester, the priority it was set to, how long it has been waiting, and a direct link to the ticket in Freshdesk built from the account subdomain. If no matching Slack user is found, still complete the assignment and flag the missing notification on the row rather than failing the whole action.

Bake in the rules that make it usable every morning. An aging threshold, default four hours and editable in a settings panel, highlights anything waiting longer than that, with a stronger treatment for tickets past double the threshold. A group filter at the top of the queue narrows everything to one team's work. Persist the threshold and the last selected group filter per viewer so each triager gets their own view back when they reopen the app. Show a small header summary of how many tickets are waiting, how many are past the threshold, and how many have been routed in this session.