Skip to content

Board rules and ConnectWise workflow rules

ConnectWise has its own workflow rules (in ConnectWise, System > Setup Tables > Workflow Rules), and most boards that use board rules already have some. Both can change a ticket’s board, status and priority, but they are built for different jobs. Use each for what it does well, and check that the two do not write the same field in different directions.

Board rules ConnectWise workflow rules
When they run Within seconds of an event: a new ticket, a ticket moved onto the board, a field change or a client’s reply In batches, on the schedule each workflow rule sets: every so many minutes, hours or days, at any time, in office hours or in SLA hours. A new ticket is noticed at the next batch.
What they test The ticket’s fields, phrases in its summary, description or the client’s reply, the sender, and an AI condition that judges what the ticket or reply says, optionally against the company’s other tickets Mostly time and state: how old the ticket is, how long since it was updated or responded to, SLA progress, past-due schedules, budget hours, business hours, and fields such as priority, company or summary
How often they act Once per event Once, or again every so many minutes, hours or days while the condition holds
What they do Set status, move to a board, set priority and team; on a client’s reply, keep the status, give the ticket back to its last technician, close appointments; bundle a repeat into the earlier ticket Change status, board or priority, assign a resource or team, apply a template, update a custom field, and send emails, push notifications and activities
How you check them Preview notes on each ticket before going Live, and a note on each change in Live ConnectWise’s Test button, which counts the tickets an event matches now

Board rules for anything decided at the moment something happens, especially when it depends on what the ticket or reply says:

  • routing a new ticket by its company, type, sender or wording;
  • cancelling automatic notices from a vendor;
  • putting a ticket back in the queue when the client replies, or leaving it alone on a plain “thanks”;
  • completing a ticket when the client confirms the problem is fixed;
  • bundling a repeat report into the client’s earlier ticket.

ConnectWise workflow rules for anything about time passing, and for telling people:

  • escalating a Priority 1 ticket nobody has touched for two hours;
  • reminding the owner of a ticket waiting on them for days;
  • warning before an SLA is missed;
  • closing Completed tickets after a number of days with no update;
  • emailing or notifying a member, a team or the client.

A board rule acts once, at an event. It cannot wait two hours and check again, so a job that needs time belongs in a workflow rule.

Both engines change the same tickets, and each sees the other’s changes as ordinary edits:

  • A workflow rule can change a field a board rule just set, or the other way round. Before switching rules on, look at the board’s active workflow rules in ConnectWise. For each field a rule sets (status, board, priority, team), check whether a workflow rule changes it too, and decide which one owns it.
  • ConnectWise reacts to a client’s reply on its own: a client’s email sets Customer Responded, and many boards have a workflow or status setting that changes the status when it is set. That is why the reply action Keep the status clears Customer Responded, and looks again a few minutes later. See Reply actions.
  • On a project board, Nilear does not read ConnectWise’s workflow rules or mark overlaps with them: check them in ConnectWise yourself.
  • Rules never undo their own changes in a loop (Loops are stopped), but they cannot stop a workflow rule from undoing them. If a ticket’s status keeps changing back, look for a workflow rule on that field.

A Service board wants tickets completed when the client confirms the fix, and closed for good five days later:

  1. A board rule, Client replied, Status is “Waiting on Client”, AI condition “the client confirms the problem is fixed and nothing more is needed”, Set status Completed. It acts within seconds of the reply, because only an AI can tell a confirmation from “it’s still broken”.
  2. A ConnectWise workflow rule on the same board: “Ticket is in Completed status and Last Updated more than 5 days ago”, run daily, action Change Ticket Status to Closed. It is about time passing, which a board rule cannot wait for.

Each does its own job on a different field change: the rule sets Completed, the workflow rule later sets Closed. If the client writes again within the five days, the ticket is no longer untouched, and the workflow rule waits.

  • Look at the board’s active workflow rules: expand the board on the Boards page and open ConnectWise workflow rules on this board (how it works), and note the fields their actions change. A rule they overlap is marked “Also changed by ConnectWise”.
  • For each board rule, make sure no workflow rule changes the same field the other way.
  • Start in Preview: the Preview notes show what the rules would do, while the workflow rules keep running as before.