Gorgias Auto Assign and Ticket Assignment Rules for Ecommerce Support Teams
Gorgias can send a ticket to the right team with a rule and then hand it to the available agent with the fewest tickets. For a store with one or two agents per queue that is enough. The trouble starts when you have a returns specialist, a part time weekend crew, a VIP queue, or agents who are signed in but already deep in a refund dispute. This page shows exactly what native Gorgias assignment does, where it stops, and how a routing layer fills the gap.
In short
Gorgias auto assign sends team tickets to signed in agents who are set to Available, choosing the agent with the fewest tickets assigned. Rules decide the team, tickets are queued by priority and then by age, and per agent capacity limits stop assignment when everyone is full. It does not read skills, shifts or ticket size. A store that needs those adds a routing layer such as Assigner beside Gorgias.
Why it fits
For a head of support, an ecommerce operations lead or a Gorgias admin on a growing Shopify or multi store desk, who sees returns work piling on one agent, weekend tickets landing on someone off shift, or VIP orders sitting in the general queue. If one team with equal agents handles everything, native auto assign is fine and you should keep it.
Rules choose the team, auto assign chooses the person
A rule with the Ticket created trigger and a condition that the message is not from an agent can assign a ticket to a team. Once auto assignment is on, tickets for that team go directly to agents on it. Rules are your skill layer. Everything inside the team is load based.
Fewest tickets is the documented selector
Gorgias states that available agents with the fewest tickets assigned get tickets first. That is load balancing, not round robin. Two agents with one open ticket each are tied, and a ticket that needs a 40 minute exchange counts the same as a one line shipping question.
Capacity limits create a silent backlog
You can cap chat and messaging tickets separately from other text tickets, and voice is outside both. If every available agent is at the limit, tickets stay unassigned until someone becomes eligible. That is safe, but nobody is told that a queue is growing unless you build a view for it.
Availability is a status, not a schedule
Agents must be signed in and set to Available. Gorgias does not read a shift calendar or time off. An agent who forgets to switch to Unavailable at the end of the day keeps receiving tickets, and unassign on reply only helps when a customer writes back.
A routing layer adds the missing inputs
Assigner decides the owner from round robin, weighted rotation, load balancing, skills and live availability, using shift schedules and time off, and records why each agent was chosen. The native rules still tag and sort. The router picks the person.
Side by side
How each Gorgias assignment option picks the agent
| Option | Where it lives | How it selects | What it ignores |
|---|---|---|---|
| Rule that assigns a team | Rules, Ticket created trigger | The team you name for matching tickets | Which agent on the team takes it |
| Auto assign tickets | Workflows, Tools, Ticket assignment | Available agent with the fewest tickets | Skills, shifts, time off, ticket weight |
| Assign to last responding agent | Same settings page, for reopened tickets | The agent who last replied | Whether they are still the best person |
| Capacity limits per agent | Same settings page | Stops assignment at the limit you set | Which tickets are heavy |
| Unassign on reply or when unavailable | Same settings page | Returns a ticket to the queue | Who should pick it up next |
| Assigner beside Gorgias | Assigner Starter or higher | Round robin, weighted rotation, load balancing, skills, availability | Nothing hidden, each assignment records the reason |
Based on the Gorgias help center articles on auto assignment and on rules, read October 31, 2026. Plan and feature names change, so confirm in your own helpdesk.
In detail
Set up Gorgias assignment so it holds under load
Turn auto assignment on in the right place
Open Workflows, Tools, Ticket assignment. Auto-assign tickets applies to new tickets, and Assign ticket to last responding agent applies to reopened ones. Only the account owner and admins can change these settings, and the feature is available on all Helpdesk plans, so there is no upgrade to buy before you try it.
Build rules from the trigger down
Gorgias runs rules in trigger order: Ticket created, New message in ticket, Ticket updated, Ticket assigned to user, Ticket snooze delay ends, then Satisfaction survey responded. Rules with the same trigger run top to bottom as listed on the Rules page, so put the narrow ones first, such as wholesale and VIP, and the catch all last. You can create up to 70 rules, and AND and OR cannot be mixed in one IF, so nest a second IF for mixed logic.
Keep the Ticket created rule customer only
Add the condition that the message from agent is false. Without it, an outbound ticket an agent creates can be routed like a customer request and land on someone else. It is the most common reason a team sees tickets assigned to the wrong person right after creation.
Set capacity limits on purpose
Pick a chat and messaging limit that matches how many live conversations a person can hold, and a separate limit for email style tickets. Remember the reopened ticket option: you can let reopened tickets exceed capacity so a customer who writes back is not stuck in a queue behind new work. Review the unassigned view daily during sales events, because a full team shows up there first.
Know where the native model stops
Fewest tickets treats a gift question and a chargeback dispute as equal. It also knows nothing about languages, product lines, or who works Saturday. Teams usually solve that with more teams and more rules, which works until the rule list is hard to read. If you are past a dozen rules whose only job is to protect one specialist, the policy has outgrown the tool.
Where Assigner fits beside Gorgias
Assigner is a routing layer that sits beside the helpdesk. It chooses an owner using round robin, weighted rotation, load balancing, skills and live availability, with shift schedules and time off, and records the reason for every assignment so a lead can answer why a ticket went to a person. Plans start at $7 per user per month billed yearly. Treat the link between Gorgias and a separate router as configuration work, since Assigner offers generic intake options and this page does not claim a ready made Gorgias connector.
Test with a week of real tickets
Replay a recent week. Count how many tickets reached an agent who was off shift, how many specialist tickets went to a generalist, and the gap between your busiest and lightest agent at close of day. If those numbers are small, native assignment is doing its job. If not, you have a measured case for a router.
Questions buyers ask
Frequently asked questions
How do I auto assign tickets in Gorgias?
Go to Workflows, Tools, Ticket assignment and turn on Auto-assign tickets. Then create a rule with the Ticket created trigger that assigns each ticket to a team. Agents on that team who are signed in and Available receive tickets, fewest assigned first. Only the account owner and admins can change the setting.
Does Gorgias have round robin assignment?
The documented behavior is fewest tickets assigned among available agents, which is load based. It does not describe a strict rotation, weights or skills. If you need true round robin or weighted rotation, a routing layer such as Assigner supplies it beside Gorgias.
Which Gorgias plans include auto assign?
Gorgias states that auto assignment and rules are available on all Helpdesk plans. Plan price scales with ticket volume, not with a feature gate on assignment, so the question is policy fit, not an upgrade tier.
Why is Gorgias not assigning tickets to an agent?
Check that the agent is signed in and set to Available, that the ticket belongs to a team the agent is on, and that they are under their capacity limit. If every available agent is at the limit, tickets stay unassigned until someone becomes eligible.
In what order does Gorgias assign tickets?
Higher priority tickets go first, and among equal priorities the older ticket goes first. Creation time is the tiebreaker. Priority runs from critical to low, so set it with a rule if VIP or urgent work should jump the queue.
Can Gorgias assign tickets by skill or language?
Not inside a team. You can create a team per language or product and send tickets to it with rules, but the choice of agent within the team is by fewest tickets. For skills across one team, add a routing layer.
What happens to reopened tickets in Gorgias?
With Assign ticket to last responding agent on, a reopened ticket returns to whoever last replied. You can let reopened tickets exceed that agent capacity limit. Unassign on reply can free a ticket when the customer writes back while the agent is offline.
How many rules can I create in Gorgias?
Gorgias allows up to 70 rules, and active rules apply across all stores and channels in the helpdesk. Rules with the same trigger run top to bottom, and you can drag them to reorder.
What does Gorgias cost?
Gorgias prices by ticket volume. Monthly plans run from $10 to $900, with overage at $0.36 to $0.40 per extra ticket. See our Gorgias pricing guide for annual rates and break even points.
What does Assigner add beside Gorgias?
Assigner adds per person rules the native setting lacks: weighted rotation, skills, live availability from shifts and time off, and a recorded reason for every assignment. It is priced per user, from $7 per month billed yearly, with a five user minimum.
Keep reading
More on helpdesk assignment, rotation and pricing.
- Gorgias pricing per ticket - Plans, overage and break even points by monthly ticket volume.
- Support ticket routing - Route every request to the right agent by skill and load.
- Freshdesk ticket assignment - The same native versus routing layer question on Freshdesk.
- Zendesk omnichannel routing - How capacity based routing works on Zendesk.
- Round robin ticket assignment - Rotation policies compared with load based assignment.
Stop hand-sorting your incoming work
Let Assigner route it to the right available person by skill, workload, and availability, using rules you control. Nothing sits unassigned and no one gets cherry-picked. Every assignment shows why.