ConnectWise Auto Assign Tickets: ConnectWise Manage Auto Assign, Round Robin, and Workflow Rules
Auto assign in ConnectWise PSA (still called ConnectWise Manage by most MSPs) is three separate features: the Auto Assign tab on each service board, round robin teams, and workflow rule actions. Each one has a condition that switches it off without an error. This page lays out what each mechanism does according to the ConnectWise documentation, the order problems show up in on a real dispatch board, and where a separate assignment engine earns its keep.
In short
ConnectWise PSA auto assigns tickets from the Auto Assign tab of the Service Board setup table, which can assign a specific member, a role, a whole team, or a round robin team to new tickets entered manually, by the Email Connector, or through the portal. The documentation warns that auto assign only works on new tickets created on that board and does not work on a ticket moved from another board. Round robin picks the next member with an empty block on their calendar, books 30 minutes for the ticket, and sends everything to a Round Robin Catchall status when nobody is free. Workflow rules can assign later, but in the cloud they run at most every 10 minutes.
Why it fits
This page is for an MSP service manager, dispatcher, or ConnectWise PSA administrator who still assigns tickets by hand from the board every morning, whose round robin sends work to the one tech with an empty calendar, or whose escalated tickets land on a second board with no owner. It assumes ConnectWise PSA is already live and the service boards exist.
A ticket moved to a board is never auto assigned
The Auto Assign tab carries a warning in the ConnectWise documentation: it only works on new tickets created on that board and does not function on a ticket moved from a different board. An MSP that triages on a front line board and then moves tickets to Tier 2 or Projects gets no automatic owner on the second board, ever.
Round robin reads calendars, not workload
Round robin checks whether a member has an empty calendar block when the ticket is created and books a 30 minute slot for it. A tech who keeps a tidy calendar full of schedule entries is skipped, while a tech who never schedules anything looks permanently free and absorbs the queue.
Assign Team on a normal team assigns everyone
The workflow action Assign Team assigns one person only if the team is marked round robin. The documentation says that if the team is not listed as a round robin team, all team members will be assigned by the action. One unticked box turns every matching ticket into a ticket owned by six people.
Auto assign sends no email to the tech
ConnectWise notes that auto assigning a resource does not send the resource an email notification. Unless a status notification or a workflow rule covers it, the assigned tech finds out from the board, which is how an urgent ticket can sit with a named owner for an hour.
Workflow rules run on a timer, not on the event
Cloud partners have workflow rules limited to running every 10 minutes, and the rules do not run on child tickets. A rule meant to reassign a priority 1 ticket can take ten minutes to notice it, and a spawned child ticket is never touched by it.
Nobody free means a catchall status, not an owner
If every round robin member is out, tickets go to the status set as the Round Robin Catchall for that board. The In/Out board is no longer part of the logic, so a tech on vacation must block their calendar or they keep receiving tickets.
Side by side
Every way a ConnectWise PSA ticket gets an owner, and where each one leaks
| Mechanism | What it assigns | When it runs | Skipped when | Where it leaks |
|---|---|---|---|---|
| Auto Assign tab, specific member or role | The named member, or members holding the role | On ticket creation, per entry source you tick (manual, Email Connector, legacy portal) | The ticket was moved from another board, or the company has auto assign turned off | Every ticket goes to the same person, with no email to tell them. |
| Auto Assign tab, round robin team | One member of the round robin team | On ticket creation, when a member has an empty calendar block | All members are booked or out, so the ticket drops to the Round Robin Catchall status | Reads calendar gaps, not open tickets. Ties go to the longest tenured member. |
| Team with Default ticked | The service team on the ticket | On ticket creation | Another default applies first | Sets the team field only. A team is not a person. |
| Workflow rule, Assign Resource | The member named in Assign Who | On the rule schedule, every 10 minutes at most in the cloud | The ticket is a child ticket, or the rule went inactive after an edit | Editing an event or action switches the rule to inactive until it is tested again. |
| Workflow rule, Assign Team | One member if the team is round robin, every member if it is not | On the rule schedule | Same as Assign Resource | A non round robin team puts every member on the ticket. |
| Email Connector SetTeam tag | One member, when the tag names a valid round robin team | When the email is parsed | The tag names a team that is not round robin | Depends on the sender or a parser writing the tag correctly. |
| Dispatch Portal and manual pick | Whoever the dispatcher chooses | When a person acts | The dispatcher is busy or out | The fallback most MSPs actually run on, and the one this page is about replacing. |
Two facts explain most dispatch complaints on this table. Auto assign fires only at creation on the board where the ticket was born, and round robin measures a free calendar slot, not how much open work a tech is carrying.
In detail
What the ConnectWise documentation actually says about ticket assignment
The Auto Assign tab: three entry sources and one warning
The Auto Assign tab lives on each service board, under System, Setup Tables, Service Board. ConnectWise describes its job in one line: it is used to automatically assign resources to a service ticket upon creation. The fields are check boxes for where the ticket came from. You can auto assign new tickets entered manually, tickets entered by Email Connector, and tickets entered through the Customer Portal, plus an option to make the assigned resource the ticket owner.
The portal box has a trap of its own. The documentation says it only works with tickets from the legacy portal, and that to auto assign tickets from the new portal you must tick the entered manually box instead. An MSP that moved clients to the new portal and left only the portal box ticked stops assigning portal tickets on the day of the switch, and nothing on the board says why.
The warning that matters most sits at the top of the page: Auto Assign only works on new tickets created on this board. It does not function on a ticket moved from a different board. Most MSPs route by moving tickets. A help desk board catches everything, a triage tech reads it, and the ticket moves to Network, Projects, or Tier 2. Every one of those moves produces a ticket with no owner on the destination board, no matter how that board is configured. The fix inside ConnectWise is a workflow rule on the destination board that watches for unassigned tickets, with the timing limits covered below.
Two quieter notes finish the page. Auto assign can be disabled per company with the Allow Service Boards to Automatically Assign Resources check box on the company Options tab, which is easy to inherit from an old migration and hard to spot. And auto assigning a resource does not send the resource an email notification.
How ConnectWise round robin actually picks the next tech
Round robin is configured in three places. On the board Teams tab you tick Round Robin on the team whose members should rotate. On the Auto Assign tab you pick that team under Resources to Assign. On the Statuses tab you choose the Round Robin Catchall status, where tickets go when nobody can take them.
The selection logic is the part most admins never read. ConnectWise says round robin looks for the member office hours per their calendar settings, falls back to the company calendar when a member has none, and checks the member calendar to confirm if they have an empty block at the time the ticket gets created. It then schedules a 30 min interval on their calendar for the ticket. If the calendar is booked with tickets, schedule entries, or activities, round robin will not schedule over or double book. In a tie, the documentation says PSA chooses the member with the longest tenure, meaning the lowest member record ID.
That design produces a pattern dispatchers recognize without knowing the cause. The techs who schedule their work carefully look busy and get skipped. The tech who works out of the ticket list and never books time looks free all day and receives a disproportionate share. A new hire with a blank calendar gets flooded in week one. None of this is a bug. Round robin measures calendar gaps, and a calendar gap is not the same thing as spare capacity.
Two more lines change how you run it. The In/Out board is no longer used in the round robin logic, so a tech on leave must block their calendar or keep receiving tickets. And round robin is available for service boards only, not project boards. The Auto Assign tab also carries a daily cap: after a set number of tickets per round robin member per day, it stops assigning to that member.
Skills in round robin: the Manage Lab dependency
ConnectWise can combine round robin with skills, but only through a switch many admins never find. On the board Types tab, each service type can carry a Skill Category Mapping and a Skill Mapping. The documentation adds a condition to both fields: the Round Robin Manage Lab must be activated in order for this field to appear. Manage Labs is found under System, Setup Tables, Manage Labs, and ConnectWise partners have described its features as technical previews that should be tested before production use.
Once active, the behavior is simple. When a new ticket of that type is auto assigned, the next available round robin member whose member page carries the matching skill category and skill is assigned. That means skills are set per service type, not per ticket, so a Network type ticket that is really a firewall ticket goes to whoever holds the Network skill. Skill data also lives on member pages, which drift as people learn and leave.
If the lab is not on, the fields are not there, and a team that watched a demo of skills based round robin can spend an afternoon looking for a setting that does not exist in their instance. Testing it is also harder than it sounds: ConnectWise lists Sandbox only in the Premium package, so a Basic or Standard partner tests routing changes on live tickets.
Workflow rules as a dispatcher: the 10 minute limit and the inactive switch
Workflow rules are how most MSPs fill the gaps auto assign leaves, especially the moved ticket gap. A rule is an event and an action, and service ticket actions include Assign Resource and Assign Team. The Assign Team definition is the one to read twice: if the team is listed as round robin, only one resource will be assigned by the action in round robin fashion, and if the team is not listed as a round robin team, all team members will be assigned by the action.
Timing is the second constraint. ConnectWise states that the cloud partners workflow rules are limited to run every 10 minutes, with 5 minutes as the minimum recommended frequency on premises. A priority 1 ticket can therefore sit unowned for up to ten minutes before a rule even looks at it. Rules set to run during My Company Office Hours will not fire after hours, and rules set to SLA Hours follow the SLA on the ticket.
Three more details from the setup table documentation cause real outages. Workflow rules do not run on child tickets, so a parent ticket that spawns work for several techs gets no automated assignment on the children. Editing the events or actions automatically switches the rule to inactive, and it has to be tested and activated again, so a quick edit on Friday afternoon can leave the rule off all weekend. And workflow rules sort alphabetically, which is why seasoned admins prefix their names.
The dispatch problems MSPs describe, mapped to their cause
Most assignment complaints on a ConnectWise board trace back to one of five causes, and each cause has a different fix.
- Escalated tickets have no owner. The ticket was moved to the board, and auto assign ignores moved tickets. Add a workflow rule on the destination board, or assign at the moment of the move.
- One tech gets most of the round robin tickets. That tech has the emptiest calendar. Either every tech books their time, or round robin stops being a fair split.
- A tech on vacation still receives tickets. The In/Out board is not read. Block the calendar.
- Six people are on one ticket. A workflow rule used Assign Team on a team that is not marked round robin.
- Portal tickets stopped getting assigned. Clients moved to the new portal, which needs the entered manually box.
A sixth complaint has no configuration fix: the right tech was never chosen at all, because nothing in ConnectWise looks at how many open tickets a tech holds, their SLA exposure, or which client contract they know. That is still a dispatcher reading the board, and for an MSP past a few hundred tickets a month it is a full time seat.
Where Assigner fits beside ConnectWise PSA, and where it does not
Every native mechanism above shares one design choice. It decides once, at creation or on a timer, using a calendar gap or a fixed name, and it never records why it chose that person. Assigner is built for the decision in the middle. It reads each new or moved ticket, applies rules your team writes, and picks one owner by live availability, current open workload, skills, and client or contract, using round robin, weighted rotation, load balancing, or priority order. Every assignment carries a plain reason, such as next in rotation among the three network techs on shift with fewer than eight open tickets.
What it does not replace is worth saying plainly. ConnectWise stays your system of record for tickets, time, agreements, and billing, and Assigner does not touch finance or agreements. If your board is small, every tech keeps a calendar, and nothing moves between boards, native round robin may be all you need. Assigner earns its place when tickets move between boards, when calendars are not a reliable signal of capacity, or when a dispatcher spends the first hour of each day deciding who takes what.
Pricing is published: $12 per user per month billed yearly, or $15 billed monthly, with a free demo that runs the real assignment engine on sample tickets. Start with the demo, or see how it handles MSP ticket assignment across client contracts and SLAs.
Questions buyers ask
Frequently asked questions
How do I auto assign tickets in ConnectWise Manage?
Open System, Setup Tables, Service Board, pick the board, and use the Auto Assign tab. Tick the entry sources to cover (manual, Email Connector, legacy portal), then choose Resources to Assign: a specific member, a role, a team, or a round robin team. It applies only to new tickets created on that board, not tickets moved in from another board.
Why is ConnectWise not auto assigning tickets?
The most common cause is that the ticket was moved from another board, and the documentation says auto assign does not work on moved tickets. Other causes: the company has Allow Service Boards to Automatically Assign Resources turned off, the ticket came from the new portal while only the portal box is ticked, or every round robin member had a full calendar.
How does round robin work in ConnectWise PSA?
Round robin checks each team member calendar for an empty block at the moment the ticket is created, assigns the next free member, and books a 30 minute slot for the ticket. It never double books. Ties go to the member with the longest tenure, and if nobody is free the ticket moves to the Round Robin Catchall status.
How do I set up a round robin team in ConnectWise?
On the service board Teams tab, open or create the team and tick Round Robin, then assign members. On the Auto Assign tab, select that round robin team under Resources to Assign. On the Statuses tab, pick a Round Robin Catchall status. ConnectWise also advises logging out and back in after editing the Teams tab so the change takes effect.
Does ConnectWise round robin use the In/Out board?
No. The documentation says the In/Out board is no longer used in the round robin logic. Availability comes from the member calendar and office hours, falling back to the company calendar. To stop a tech on leave from receiving tickets, block the days off on their calendar.
Can ConnectWise auto assign tickets based on skills?
Yes, through round robin, once the Round Robin Manage Lab is activated. Service types on the board Types tab can then carry a skill category and skill mapping, and the next available round robin member with matching skills on their member page is assigned. Skills are set per service type, not per individual ticket.
How do I assign a ticket with a ConnectWise workflow rule?
Create a service ticket workflow rule with an event, such as a ticket entering a status with no resource, and an Assign Resource or Assign Team action. Test every event, then Activate. In the cloud rules run at most every 10 minutes, and they do not run on child tickets.
Why did my ConnectWise workflow rule assign the whole team?
The Assign Team action only assigns one person when the team is marked round robin. The documentation says that if the team is not listed as a round robin team, all team members will be assigned by the action. Tick Round Robin on the team, or use Assign Resource instead.
Does auto assign notify the technician in ConnectWise?
No. ConnectWise states that auto assigning a resource does not send the resource an email notification. Cover it with a status notification or a workflow rule that emails the assigned resource, or the tech learns about the ticket only when they next look at the board.
Can I limit how many tickets round robin gives each tech per day?
Yes. The Auto Assign tab has an option to stop assigning service tickets after a set number per round robin team member per day. It caps the count, not the effort, so ten password resets and ten server rebuilds count the same.
Does ConnectWise round robin work on project boards?
No. The Teams tab documentation says the round robin feature is only available for service boards and not project boards. Project tickets need a workflow rule with Assign Resource, a default on the project, or a person assigning them.
Which ConnectWise PSA package includes auto assign?
The Auto Assign tab documentation applies to PSA Basic, PSA Standard, and PSA Premium, and workflow automation is listed in the Basic package. Routing is not a tier decision. Sandbox, useful for testing routing changes safely, is listed only in Premium.
Keep reading
Related ticket routing pages worth reading next:
- MSP ticket assignment - Routing tickets by skill, client contract, SLA priority, and tech availability.
- ConnectWise PSA pricing - Basic, Standard, and Premium, third party per user figures, and what routing costs inside PSA.
- Round robin ticket assignment - How fair rotation should behave when people go offline or fill up.
- ServiceDesk Plus auto assign technician - Another help desk whose load balancing counts only one status.
- Support ticket routing - The general model for routing tickets by skill, workload, and availability.
- Round robin vs load balancing - Why a turn based split and a workload based split give different results.
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.