I’m looking for some practical suggestions on improving customer support response times without reducing the quality of support.
Our team receives a mix of simple questions, technical issues, and requests that require follow-up. Sometimes tickets remain open longer than expected because they need to be assigned to the right person or require information from another team.
What are some effective ways to organize ticket assignment, prioritization, and follow-ups in Freshworks? I’d also be interested in hearing how other teams use automation, workflows, or reporting to identify tickets that may be delayed.
Any recommendations or examples from your experience would be appreciated.
Thanks!
Best answer by Arputha G
Hi @jameswilliam
Greetings from Freshworks Community Team! I hope you are well.
To start with improving response times while maintaining quality in Freshdesk, we can focus on the key tasks below to automate: (1) getting tickets to the right group/agent immediately, (2) making priority and SLA for a ticket, and (3) systematising follow-ups so “waiting on customer/other team” doesn’t turn into silent ageing.
Sharing steps you can start with some of core actions:
1. Automate Assignment & Routing
Align Groups & Fields: Create functional Groups (e.g., Billing, L1, L2/Engineering) and standardize ticket fields (Issue Type, Product, Customer Tier, Urgency) to drive automation rules based on the values to the fields.
Set Ticket Creation Automation Rules to assign the group: Tickets can be auto-assigned to the relevant groups based on fields, keywords or even customer segments via Automation rules.
Agent assignment: Use any of the automatic ticket assignment methods to assign the ticket to an available agent within the group. We also have options to notify Supervisors after X minutes if a ticket is still unassigned (in case all agents are unavailable for ticket creation).
2. Standardize Priorities & SLAs
Define a Priority Matrix: Train agents to consistently apply P1–P4 tiers based on business impact and urgency under Admin > SLA policies. This helps align to the urgency of issues and work on resolving them for your customers.
Build Ticket List Views: Create daily agent ticket list views for Unassigned (>15m), SLA at Risk, Waiting on Customer (>3d), and Reopened Tickets and also monitor tickets via dashboards.
These are great points to start with - I hope this helps. We’d be most happy to continue the discussion further and help you with specific recommendations based on your use case. Please keep us posted on your thoughts!
Greetings from Freshworks Community Team! I hope you are well.
To start with improving response times while maintaining quality in Freshdesk, we can focus on the key tasks below to automate: (1) getting tickets to the right group/agent immediately, (2) making priority and SLA for a ticket, and (3) systematising follow-ups so “waiting on customer/other team” doesn’t turn into silent ageing.
Sharing steps you can start with some of core actions:
1. Automate Assignment & Routing
Align Groups & Fields: Create functional Groups (e.g., Billing, L1, L2/Engineering) and standardize ticket fields (Issue Type, Product, Customer Tier, Urgency) to drive automation rules based on the values to the fields.
Set Ticket Creation Automation Rules to assign the group: Tickets can be auto-assigned to the relevant groups based on fields, keywords or even customer segments via Automation rules.
Agent assignment: Use any of the automatic ticket assignment methods to assign the ticket to an available agent within the group. We also have options to notify Supervisors after X minutes if a ticket is still unassigned (in case all agents are unavailable for ticket creation).
2. Standardize Priorities & SLAs
Define a Priority Matrix: Train agents to consistently apply P1–P4 tiers based on business impact and urgency under Admin > SLA policies. This helps align to the urgency of issues and work on resolving them for your customers.
Build Ticket List Views: Create daily agent ticket list views for Unassigned (>15m), SLA at Risk, Waiting on Customer (>3d), and Reopened Tickets and also monitor tickets via dashboards.
These are great points to start with - I hope this helps. We’d be most happy to continue the discussion further and help you with specific recommendations based on your use case. Please keep us posted on your thoughts!