Atera Ticket Automation Rules for Auto Assigning Tickets with Round Robin and Technician Groups

How an Atera rule hands a ticket to a technician

Every automatic assignment in Atera comes from a ticket automation rule. You build them under Admin, Support and ticketing, Ticket automation rules, and you can create as many as you want. Each rule has a name, a description, a trigger, an Enable rule box and an Always run box, then a list of conditions and a list of actions.

The trigger decides which event wakes the rule up. For assignment the one that matters is New ticket created, with Ticket assignment changed and Ticket group assignment changed useful for notifications and escalations. The others cover status changes, closed or resolved tickets, low survey ratings, replies from the requester or contact, escalation by the AI assistant, and approval status changes.

Conditions filter which tickets the rule touches. The ones people route on most are Source (email, portal, alert), Customer, Site, Ticket form, Title, Impact and Priority, Product family, From user email, any custom field, and the AI Auto ticket tag. You can also check the event time against a business hours calendar. Leave conditions empty and the rule applies to every ticket on that trigger.

The action that assigns is Set field value. It can set the Technician field to a named person or to Auto Assignment, set the Technician group, and change priority, status, type, impact or the ticket form. Other actions send emails, send a survey, create a child ticket or fill a custom field with Copilot.

A typical routing setup for a small MSP

1. A rule on New ticket created with Customer equals your largest client sets that client group, then Auto Assignment.
2. A rule with Source equals Alert sets the monitoring group and raises priority.
3. A catch all rule with no conditions sets Technician to Auto Assignment for everything else.

That works as long as the rules sit in the right order and the flow settings are right, which is where most broken Atera routing comes from.

Round robin with Auto Assignment and the permission behind it

Atera has no dedicated round robin page. Rotation is a value: in a Set field value action on the Technician field, you choose Auto Assignment, and Atera assigns technicians in round robin order. Atera also ships it as one of four preset rules, next to reopening resolved tickets on a reply, the new ticket email, and reassigning tickets of a disabled technician when they reopen.

The rotation is not everyone in the account. Only technicians whose access role has Include in auto-assignment turned on take part. You set it under Admin, Users and security, Access roles, on the Ticketing tab of the role. This is the most common reason a new technician never receives an automatic ticket: their role was cloned from one without the permission, or they still sit on the Beginner role Atera gives every new technician until an admin changes it.

Two quick checks settle most rotation complaints:

• Open each role your technicians use and confirm the permission is on for the roles that should take tickets and off for managers and billing staff.
• Open Admin, Users and security, Technicians and check the Availability column. Anyone on Out of office is skipped until someone switches them back.

Remember that every person who logs in to the Atera console needs a technician license whatever their role, so a dispatcher or service manager who only routes tickets is a full seat. Excluding them from the rotation is a permission setting, not a license saving.

Why the group has to come first in the rule

Technician groups let you split the rotation: tier 1, tier 2, a project team, an HR queue for new hire forms. Groups can be used as a trigger, a condition, or the value of an action, and a technician can belong to several groups. A group can also be Private, so only its members can see its tickets, even people with permission to see tickets assigned to others.

The trap is action order. Atera documents it in plain terms: the group assignment action must be entered first, followed by any other action. If you put the technician auto assignment first, it assigns a technician from any group. Then the group action runs, and if that technician is not a member, the ticket technician becomes unassigned. With the group first, auto assignment rotates only among members of that group.

Group membership changes have the same side effect. Removing a technician from a group unassigns them from the tickets that are assigned to that group and to them. Deleting a group unassigns every ticket assigned to it. If you reorganize groups on a Friday afternoon, expect a list of tickets with a group and no person on Monday.

First match wins, Always run, and the Not Equals trap

Atera evaluates rules in order, and the default flow is strict. If no rule has Always run selected, the first rule whose conditions match is executed and every later rule is ignored, even when its own conditions match. If some rules have Always run, then after the first rule executes, only the later rules with Always run are performed. Several Always run rules can fire on the same ticket.

That has a practical consequence for routing. A broad rule near the top, for example one that sends all email tickets to tier 1, will catch the email tickets from your VIP client before the client rule further down ever sees them. Either move the specific rule above the broad one or give the specific rule Always run and make sure the two do not fight over the same field.

Conditions have their own logic. A condition marked Must match is mandatory. Without Must match, at least one of the conditions needs to be true. Atera warns about one case in particular: two Not Equals conditions in the same rule, such as Source Not Equals Phone and Source Not Equals AI Assistant. A ticket created by hand in the console is not from the AI assistant, so one condition is true and the rule runs anyway. Atera advises separate rules for each condition instead of stacking Not Equals.

Two more rules of the engine matter when you debug. One rule cannot trigger another, because rules react to ticket events or time, not to each other. And changing a rule does not touch existing tickets; it only applies to events that happen after the change.

Why equal turns stop being fair in an Atera help desk

Round robin in Atera is fair in the way a deck of cards is fair. Every included technician gets the next ticket in turn. Atera describes no input for how many tickets a person already has open, how long those tickets take, or what the person is good at. In an MSP that is where the trouble starts.

• The long ticket problem. A server migration and a password reset count as one turn each. The technician who drew the migration keeps receiving password resets at the same rate as everyone else.
• The forgotten toggle. Out of office technicians are skipped, but the status is a manual switch on the profile or in the admin list. Someone who is sick and did not flip it stays in the rotation, and their tickets wait until a client calls.
• The return pile. When a technician comes back, the rotation does not know they have nothing open. They get one turn like everyone else while the people who covered for them are still buried.
• After hours. A rule can check the event time against a business hours calendar, but the rotation itself does not know who is on shift. Night tickets rotate onto people who are asleep unless you build a separate rule set for after hours.

None of this is a bug. It is what a turn based rotation does. The fix is an assignment step that reads availability and open load at the moment the ticket arrives.

When Atera rules do not fire or tickets stay unassigned

Most routing problems in Atera come down to a short list. Work through it in this order before you rebuild anything.

1. Is the rule enabled? Edit the rule and check the Enable rule box. Disabled preset rules look identical to active ones in a quick scan.
2. Did an earlier rule match first? Without Always run, the first matching rule ends the flow. Look for a broad rule above the one that should have fired.
3. Are the actions in the right order? Group first, then technician, then notifications or status changes. Atera recommends assigning before notifying for reliable execution.
4. Is the technician eligible? Check the role permission Include in auto-assignment and the Availability status.
5. Was the ticket created before the rule? Rule changes only affect future events, so tickets already in the queue keep whatever they had.
6. Did a status edit expect a re-trigger? Rules fire on status transitions, not on edits, so editing a resolved ticket does not run the resolved rule again.

There is no rule level report in Atera. The way to see what a rule did is the activity log on the ticket itself. For a dispatcher trying to explain a week of uneven assignment, that means opening tickets one by one.

One SLA detail catches teams that rely on automatic replies: automated responses do not count toward first response. Only a reply from a technician stops that clock, which is another reason a ticket needs a real owner quickly.

How Assigner picks the technician beside Atera

Assigner is task assignment software that decides who takes each new ticket. It works beside Atera rather than replacing it: your rules can keep setting the client, the group and the priority, and Assigner makes the person decision. New tickets reach Assigner through its intake by email forward, webhook or API, Assigner picks one available technician and records why, and the decision goes back so the ticket gets its owner.

• Availability that is not a toggle. Working hours, shifts and time off decide who is eligible, so a sick day or an early finish does not leave a person in the rotation.
• Load before turn. Load balanced routing sends the ticket to the technician with the most room, with a cap per person so nobody is buried.
• Skills and clients. Route by client, site, ticket type or skill, so the network tickets for one client go to the people who know that network.
• A reason on every assignment. Each ticket carries the rule that chose the technician, for example client match plus lowest open load plus on shift. That is the answer a client or a technician wants when they ask why.
• One engine for every queue. The same rules can route help desk tickets, project tasks and sales leads.

Pricing is per user with a 5 user minimum: Starter $7 per user per month billed yearly ($15 monthly), Team $18 ($36), Business $36 ($72) and Enterprise $49 ($98). Load balanced routing starts on Team. Try the routing studio at the top of this page with your own team before you change a single Atera rule.

How do I auto assign tickets in Atera?

Create a ticket automation rule under Admin, Support and ticketing, Ticket automation rules. Use the New ticket created trigger, add any conditions, then add a Set field value action on the Technician field with either a named technician or the value Auto Assignment, which rotates tickets in round robin order. Save with Enable rule checked.

Does Atera have round robin ticket assignment?

Yes. Setting the Technician field to Auto Assignment in a rule assigns technicians in round robin order, and Atera ships a preset rule that does this for new tickets. Only technicians whose access role has Include in auto-assignment are in the rotation, and Out of office technicians are skipped.

Why are my Atera ticket automation rules not firing?

Usually one of four things: the rule is not enabled, an earlier rule matched first and this rule lacks Always run, the conditions do not match the event, or the ticket existed before you changed the rule. Rules also do not trigger each other. Check the ticket activity log to see which rule actually ran.

Can Atera assign tickets based on technician workload?

Atera documents no workload based assignment. The Auto Assignment value rotates in round robin order among eligible technicians and the documentation mentions no open ticket count or capacity. To route by workload you need an assignment step outside the native rules, such as a router that reads open load and availability.

How do Atera technician groups work in automation rules?

Groups can be a trigger, a condition, or an action value. To rotate inside a group, add the action that sets the Technician group first and the Auto Assignment action second. In the other order, Atera may pick a technician outside the group and then unassign them when the group is set.

Does an out of office technician still get tickets in Atera?

No, not from auto assignment. Technicians set to Out of office are excluded from the rotation. The status is a manual toggle on the profile or an admin dropdown under Admin, Users and security, Technicians, so if nobody flips it the person stays eligible. Rules that assign a named technician still assign them.

How much does Atera cost per technician?

On the IT department pricing page, Professional is $149, Expert $189 and Master $219 per technician per month billed annually, with Enterprise on quote. MSP plans start at $129 per technician per month billed annually for Pro. Every person who uses the Atera console needs a technician license.

What does Always run mean in Atera automation rules?

Always run lets a rule execute regardless of where it sits in the rule order. Without it, only the first rule whose conditions match runs. With it, after the first matching rule, any later rule marked Always run is also executed, and several Always run rules can fire on the same ticket.

How many ticket automation rules can I create in Atera?

As many as you want. Atera sets no limit on the number of rules. The practical limit is order and overlap: every broad rule placed above a specific one can stop the specific rule from running, so keep rules narrow and review their order whenever you add one.

Can Atera route tickets by customer, site or keyword?

Yes. Rule conditions include Customer, Site, Title, Source, Ticket form, Priority, Impact, Product family, From user email, custom fields and AI auto tags. A rule can match any of them and then set a technician or group. Auto tagging is listed on the Expert plan and above on IT department pricing.

Do Atera rules apply to tickets already in the queue?

No. Changes to a rule apply only to events that happen after the change. Tickets already in the queue keep their current assignment, so after fixing a rule you have to reassign the waiting tickets by hand or in bulk from the Tickets page.

How much does Assigner cost to route Atera tickets?

Assigner is priced per user with a 5 user minimum. Starter is $7 per user per month billed yearly with round robin and availability skip, Team is $18 and adds load balanced routing, Business is $36 and Enterprise $49. You license the technicians who receive work.