Route and handle tickets with board rules
A board’s rules do the routine dispatch work for you. An urgent ticket goes to the Escalation board as Pending, a Team Green company’s tickets go to the Green board, a vendor’s automatic notice is cancelled, and a client’s reply puts the ticket back in the queue. Each rule is one or more triggers, a match and one to six actions. You need the Admin access level.
Add a rule
Section titled “Add a rule”- In Ticket Automation, open Boards, and click the name of the board the tickets are on, such as Service, to expand it.
- Under Rules, click Add a rule, and give it a name.
- Under When, tick the events it fires on (see Triggers). It fires on any of them. A new rule starts with New ticket ticked.
- Add the conditions under If. Every condition must hold for the rule to match. A condition that lists several values holds when the ticket has any of them.
- Optionally, write a sentence under And the AI agrees that (see The AI condition).
- Choose what happens under Then: Move to board, Set status, Set priority and Set team, Apply template, Set custom field, and a named owner or resource, for a rule whose only trigger is Client replied the reply actions, or, when the AI sees the company’s other tickets, Bundle into the related ticket. A move needs a status of the board it moves to. Closed statuses, such as Completed or Canceled, are offered and marked as closing the ticket.
- Click Save rule.
Switch Rules on for the board when you are ready. The board’s row then reads, for example, “Rules: 3”. Rules run only while the board itself is switched on.
Describe a rule in a sentence
Section titled “Describe a rule in a sentence”Instead of picking each part, you can say what the rule should do and let the AI fill in the editor.
- A new rule: under Rules, click Describe a new rule, type a sentence, and click Fill in the rule. The editor opens with the rule filled in.
- A rule you are editing: type in Change this rule in a sentence at the top of the editor, such as also cover “cheers”, and click Change. The rule keeps its name, its switch and its place unless the sentence changes them.
For example:
- Move Priority 1 tickets to the Escalation board as Pending.
- When a client just says thanks on a ticket waiting on them, don’t change the status.
- When a client just says thanks on a resolved ticket, clear the customer responded and leave as resolved.
Nothing is saved until you click Save rule. Read the rule first: its line in words, each condition, and above all its AI condition, which decides which tickets it acts on. A note above the fields says what the AI assumed. A new rule is added at the bottom of the list, so check its place too (see Order matters). The plain “thanks” rule, for example, must sit above a rule that requeues on any reply.
How it builds the rule:
- It uses exact conditions (statuses, priorities, phrases, sender domains and so on) wherever they can do the job, and writes an AI condition only for the part that needs judgement, such as “asks for nothing more”.
- Every value comes from your PSA. When a word could mean more than one value, or matches none, it asks you instead of guessing (“Which status do you mean by waiting?”). Edit the sentence and ask again.
- When you ask for something rules cannot do, such as emailing the client, it says so and what rules can do. When only part of the sentence is possible, it fills in that part and says what it left out.
The AI sees your sentence, the rule you are changing and the names of your PSA’s boards, statuses, priorities, teams, types and sources. It does not see any ticket, and a company or contact in the rule you are changing is not sent by name. It uses the PSA’s own AI key, or Nilear’s when the PSA has none.
Templates, custom fields and named members
Section titled “Templates, custom fields and named members”These actions work with any trigger.
| Action | What it does |
|---|---|
| Apply template | Sets the type, subtype, item, priority and team the ConnectWise ticket template names, then adds its tasks. A task whose text the ticket already has open is not added again. The rule’s own Set priority and Set team win over the template’s. The template’s status, board, summary, description, company, contact and billing are not used: the status and board are the rule’s own actions, and the rest are the client’s words and your billing setup. |
| Set custom field | Sets one of the ticket’s custom fields to the value you give, and leaves its other custom fields as they are. The value input follows the field: text (up to 1,000 characters), a number, a date, ticked or not, or one of the field’s options. Leave it empty to clear the field. A date is written as that day in your ConnectWise’s time zone. |
| Make a member the owner | Sets the ticket’s owner to the member you pick. A rule cannot also have Make the last technician the owner. |
| Add a member as a resource | Adds a schedule entry for the member with no date or time, unless they already are a resource of the ticket. |
- Which templates are offered: those for the board the ticket ends on (the Move to board board, or this one), and those for no board. Choosing another Move to board drops a template of the board left behind. A template whose type, subtype, item or team is not on the board the ticket ends on is not applied, and the rule’s note says why.
- Members are your PSA’s active members. A member who later leaves, a template that is deleted, or a custom field
that is removed marks the rule as needing attention. Until you fix it, that action is not done, the rule’s other
actions still are, and the note ends with a line such as
Not done: Owner: Dana Lee is no longer an active member. - Each change is made once. If ConnectWise is slow and the rule is retried, nothing is written twice.
- In Preview, nothing changes, and the note lists what would:
Template → Security incident (type Incident, subtype Security, 3 tasks),Next Steps → Review,Owner → Dana Lee,Resource → Dana Lee. - If templates or custom fields cannot be read, the editor says so, and those actions are not offered. The PSA’s ConnectWise API member needs to be allowed to read service templates and custom fields.
ConnectWise’s own Apply Template on a ticket can also change the summary, the initial description and billing. A board rule’s Apply template never does.
Reply actions
Section titled “Reply actions”A rule whose only trigger is Client replied can also use these actions, under Then. Tick another trigger and they are removed from the rule.
| Action | What it does |
|---|---|
| Keep the status | Clears Customer Responded at once, so a ConnectWise workflow that changes the status when a client responds does not act. If the reply itself changed the status (the email connector reopening a closed ticket), the status is set back at once. About 3 minutes after the reply it looks again, and sets the status back if a workflow changed it anyway, with a note saying so. It replaces Set status and Move to board. |
| Make the last technician the owner | Sets the ticket’s owner to the last technician. |
| Add the last technician as a resource | Adds a schedule entry for the last technician with no date or time. ConnectWise already adds a new owner as a resource, so with Make the last technician the owner they are not added twice. |
| Schedule the last technician today | Adds a schedule entry for the last technician dated today, with no time. |
| Close open appointments | Deletes the ticket’s appointments that have not started, and marks those already under way done. Resources with no date are left alone. |
The last technician is the member who last wrote a note on the ticket before the reply, or entered time on it, whichever is later. NilearX’s own API member never counts. If there is none yet, those actions change nothing.
A rule can have up to six actions. In Preview, the note lists what the reply actions would do, and nothing changes on the ticket or its schedule.
Bundle into the related ticket
Section titled “Bundle into the related ticket”When the AI sees the company’s other tickets, a rule can bundle the ticket under the earlier ticket the AI names, as Bundle does in MTX. Tick Bundle into the related ticket under Then. It is the rule’s only action.
- Child status: the status the bundled ticket is set to. The editor picks the board’s status named like “Child Ticket”, “Combined Ticket” or “Bundled”, and you can choose another. A closed child status closes the ticket, and ConnectWise then closes its open tasks. If NilearX’s API member may not close tickets, ConnectWise refuses a closed child status: the bundle stands, and the note says the status was left as it was.
- What happens, in Live:
- The ticket is bundled as a child under the ticket the AI named. If that ticket is itself a child, the ticket goes under its parent instead.
- The child is set to the child status.
- The parent is marked Customer Responded, so its technician sees that the client wrote in again. A ConnectWise workflow that reacts to Customer Responded then acts on the parent, as if the client had replied there.
- A note on the child reads, for example,
Bundled into #5601; Status → Child Ticket; Customer Responded set on #5601.
- What stays with the bundle: the child’s notes, email contacts and time, as with any ConnectWise bundle. Nothing else on the parent changes.
- When nothing is bundled:
- The AI names no earlier ticket. The rule does not match, and the next rule is tried.
- The named ticket is closed, or the new ticket already has children or is already a child. No later rule acts on the ticket for that event.
- In Preview: nothing is bundled or changed. The note says what the rule would do.
- Undoing a bundle: in ConnectWise, open the parent’s bundled tickets and remove the child.
On a new ticket, a bundle in Live stops the board’s automations from running on it: the repeat is worked on its parent.
Rules on a project board
Section titled “Rules on a project board”A project board has rules like a service board, with the same triggers and conditions, and the board’s own statuses, types, subtypes and items. Four actions are not offered there, and a rule using one is refused when saved:
- Set team: a ConnectWise project ticket has no team.
- Move to board: a project ticket’s board is its project’s.
- Bundle into the related ticket: ConnectWise cannot attach a ticket to a project ticket.
- Apply template: ticket templates are for service tickets.
The reply actions work on project tickets: the last technician is found from the project ticket’s notes and the time charged to it, and appointments are the project ticket’s own schedule entries.
Order matters
Section titled “Order matters”For each event, the board’s rules with that trigger are tried from the top, and only the first that matches acts. Put the most specific rules first. Use the arrows to move a rule up or down, and the switch beside a rule to stop it without deleting it.
Triggers
Section titled “Triggers”| When | Fires |
|---|---|
| New ticket | When a ticket is created on this board. |
| Moved onto the board | When a ticket is moved onto this board from another board, by anyone. |
| Field changed | When a ticket on this board has its priority, status, type, subtype, item, summary or company changed. A rule fires only when a field its own conditions read changed: a rule on Priority is not tried when someone edits the summary. |
| Client replied | When a contact writes a note on a ticket on this board, closed tickets included, so a rule can reopen one. When the email connector reopens a closed ticket with the reply, a Status condition still sees the status the ticket had before, such as “Resolved”. |
A rule with several triggers is tried on each of them, in its place in the list. One rule with New ticket and Field changed acts on tickets created urgent and on tickets changed to urgent alike.
Other edits, such as a contact or description change, or a change to a company’s own types, do not fire a rule. The next change or move that is reported does.
A change counts whoever made it, NilearX included. If Assign Priority raises a new ticket to urgent, a Field changed rule on Priority can then move it.
Conditions
Section titled “Conditions”| Condition | Tests |
|---|---|
| Priority, Status, Source, Type, Subtype, Item | is any of, is none of (Type, Subtype and Item also: is empty) |
| Company type | is any of, is none of. A company with several types matches when any of them is listed. |
| Company, Contact | is any of, is none of, searched by name (Contact also: is empty) |
| Sender email, Sender domain | is any of, is none of: whole addresses or domains, such as vendor-alerts.example. The sender is the ticket’s contact, or for a reply the contact who wrote it. |
| Summary, Description | contains any of, contains none of: phrases, ignoring case |
| Reply | contains any of, contains none of: phrases in the client’s reply. Only when Client replied is the rule’s only trigger. |
The AI condition
Section titled “The AI condition”A rule can add one sentence the AI judges, such as “the client reports a suspected security breach”, or for a reply “the client confirms the problem is fixed”.
- The AI is asked only when every other condition of the rule holds, and no earlier rule matched. A rule with only an AI condition is judged on every ticket that reaches it.
- It uses the company’s AI key (Add your AI key), and each ticket it is asked about counts toward the board’s limit of 200 automated tickets an hour.
- Rules with no AI condition need no key and cost nothing.
- If the AI cannot be asked, because the company has no working key, the ticket is not acted on by that rule or by any rule after it for that event, so a later rule never acts in its place.
What the AI sees
Section titled “What the AI sees”Under the AI condition, choose what the AI is given:
- Only this ticket, the default: its summary, description, company, contact, priority, type, subtype, item and source, and for a reply the reply’s text.
- This ticket and the company’s other tickets: also the same company’s open tickets, on any board, and those closed in the last 7 days, that were entered before this one. At most the 30 newest, each with its summary, board, status, priority, type, contact, dates and the start of its opening text.
The second choice makes the AI’s prompt larger and costs one more ConnectWise read, made only when the AI is asked. It
still counts as one ticket toward the board’s hourly limit. The AI may name the earlier ticket its answer relies on; the
rule’s note then ends with Related ticket: #<number>, so a technician can check it. If ConnectWise refuses that read,
for example because NilearX’s API member may not run reports, no rule acts on the ticket for that event.
Try a rule before switching it on
Section titled “Try a rule before switching it on”Try this rule, under the rule in the editor, shows what the rule would have done on the board’s recent work. It works on the rule as it is in the editor, saved or not, and changes nothing.
- A rule for New ticket, Moved onto the board or Field changed is tried on up to 30 open tickets on the board that were updated in the last 7 days, the most recently created first. It is tried against each ticket as it is now, so a Field changed rule is tried as if one of the fields it tests had just changed.
- A Client replied rule is tried on the latest reply from a client on up to 25 of the board’s tickets updated in the last 7 days, closed ones included.
- The AI condition is judged only for tickets that pass the other conditions, for at most 10, with the company’s own AI key, as the rule itself would be. The others are counted as not judged, with the reason: the limit was reached, the company has no working key, or the try ran out of time. A try does not count toward the board’s hourly limit.
The answer reads, for example, “3 of 25 would match”. Each match shows the ticket and, for an AI condition, the AI’s reason. When a rule higher on the list would match the same ticket, it says that rule would act first, or may act first when that rule has an AI condition of its own: rules are tried in order, and only the first that matches acts.
Below the matches, Did not match counts the tickets by the first condition that ruled them out. “Status is Waiting on Client failed for 18” means 18 of the tried tickets were not Waiting on Client: widen that condition if they should have matched. “The AI condition failed for 9” means the AI judged 9 tickets and said no; read the AI condition again if some of them should match.
Change the rule and the answer is marked out of date; try it again. A try is a quick check, not a replacement for Preview: keep a new rule in Preview and read its notes before going Live.
Preview and Live
Section titled “Preview and Live”Rules follow the board’s mode (Choose Preview or Live):
- In Live, the rule’s actions are made in one update of the ticket, and an internal note headed Nilear AI applied a rule says what changed and which rule did it.
- In Preview, nothing on the ticket changes, and a note headed Nilear AI suggests a rule’s changes says what the rule would have done. A rule suggests at most once per ticket, or per reply.
Leave a board in Preview for a week before going Live with any rule that closes tickets, and read its notes.
Rules and the board’s automations
Section titled “Rules and the board’s automations”On a new ticket, the board’s rules run before its automations. If a rule moves the ticket to another board or closes it, the board’s automations do not run on it. A moved ticket is automated on the board it lands on only by that board’s moved-in automations. A priority a rule sets is kept: Assign Priority treats it as a priority someone chose.
ConnectWise’s own workflow rules keep running beside the board’s rules. Jobs about time passing, such as escalating an untouched ticket or closing Completed tickets after some days, belong there (Board rules and ConnectWise workflow rules).
ConnectWise workflow rules on the board
Section titled “ConnectWise workflow rules on the board”On a project board this section says ConnectWise workflow rules are read for service boards only, and none is listed or offered for converting.
Under the board’s rules, ConnectWise workflow rules on this board lists the active workflow rules ConnectWise runs on this board’s tickets: those set to this board, and those set to every board. Click it to open it. Each shows:
- how often ConnectWise runs it, such as daily or every 12 hours;
- each event, in ConnectWise’s own words, and whether it acts once or repeats;
- each action, such as “Change Ticket Status → Closed” or “Send Email → Assigned Resources”.
The list only shows them: change them in ConnectWise, under System > Setup Tables > Workflow Rules. It is read when you open the board and kept for up to an hour, so a change you just made in ConnectWise may need Refresh.
“Also changed by ConnectWise” on a rule means an active workflow rule changes one of the fields the rule sets: status, board, priority, team, owner or resources. The editor shows the same warning as you choose actions. It never stops you saving: many overlaps are intended. For example, a reply rule that sets Completed and a workflow rule that closes Completed tickets after 5 days each do their own job. Look at the workflow rule’s event and action, and ask whether either would undo the other. A rule raising the priority and a workflow rule lowering it again would.
If the section says NilearX cannot read the workflow rules, the PSA’s ConnectWise API member needs Inquire on System > Table Setup in its security role. Without it the board’s rules work exactly as before; only the list and the warnings are missing. Board rules and ConnectWise workflow rules explains which jobs belong where.
Move a ConnectWise workflow rule to a board rule
Section titled “Move a ConnectWise workflow rule to a board rule”Under ConnectWise workflow rules on this board, each workflow rule’s event says whether it can become a board rule:
- Convert to a board rule opens the rule editor with the rule filled in, unsaved, named after the workflow rule. The notes above the fields say which actions were left out, such as Send Email, and that the board rule acts within seconds of an event rather than at ConnectWise’s next run. Check it, then Save rule.
- Stays in ConnectWise says why it cannot. A board rule acts once, when something happens to a ticket, so a workflow rule that tests time (how old the ticket is, time since the last update or a response, its SLA, its schedule, budget or business hours), or that repeats every few hours or days, belongs in ConnectWise. So does one that only sends notifications.
- Draft with AI is offered when a condition has no exact board-rule equivalent, such as a team or a custom field, and nothing about the event is about time. It describes the event and its actions to the rule builder, which drafts a rule, asks, or says what rules cannot do, as for a sentence of your own.
What converts:
| In the workflow rule | In the board rule |
|---|---|
| Priority, Company, Company type, Source, Status, Contact is | is any of; “and not” gives is none of |
| Summary LIKE a phrase | Summary contains any of; “and not” gives contains none of |
| Ticket does not have a Type, Sub Type or Item | Type, Subtype or Item is empty |
| Ticket is open | nothing: rules act on the board’s tickets |
| Change Ticket Status, Change Board (with its status), Change Ticket Priority, Assign Team | Set status, Move to board and Set status, Set priority, Set team |
| Apply Template, Assign Resource (a named member) | Apply template, Add a member as a resource (and Make a member the owner when the workflow makes them the owner) |
A workflow event that runs once becomes a rule for New ticket, and also Field changed when one of its conditions is on a field whose change can fire a rule. Two conditions on the same field, a condition joined by “or”, and Update Custom Field, whose field and value ConnectWise does not give out, do not convert. A workflow rule’s location and department are named in the notes: a board rule has neither, and applies to every ticket on its board.
NilearX never changes the workflow rule. Until you switch it off in ConnectWise, both act on the board’s tickets. Follow this order:
- Convert the workflow rule, check the draft, and save it.
- Leave the board in Preview and read the rule’s notes for a few days.
- Switch the board to Live.
- Switch the workflow rule off in ConnectWise, under System > Setup Tables > Workflow Rules.
Changed again after this rule shows any change the workflow rule makes after the board rule, while both are on.
Changed again after this rule
Section titled “Changed again after this rule”A rule is only useful if what it sets stays set. For 30 minutes after a rule changes a ticket in Live, NilearX watches the fields it wrote: status, board, priority, team, owner, type, subtype and item. When someone else changes one of them, the change is recorded against the rule, with who made it: a ConnectWise workflow by name, a member, the email connector, or ConnectWise itself. NilearX’s own changes are not counted, nor are changes after the 30 minutes, and only the first change of each field is.
The rule’s line then reads, for example, “Changed again after this rule: 4 times in 7 days”. Click it to see the count by who, and the latest ten: the ticket, the field, the value the rule set, the new value, who and when. Nothing is written to the ticket, and records are kept 30 days. Custom fields and resources are not watched.
What to do about it:
- A ConnectWise workflow is named. The rule and the workflow rule disagree about the field, and the workflow wins each time. Look at that workflow rule’s actions under ConnectWise workflow rules on this board, and decide which of the two should own the field: change or switch off the workflow rule in ConnectWise, or drop that action from the board rule. Board rules and ConnectWise workflow rules explains which jobs belong where.
- Members are named. People keep correcting the rule’s choice. A member’s change may be ordinary triage, but if it happens often the rule is probably too broad: try it on the board’s recent tickets, and narrow its conditions.
- The email connector is named. A client’s email changed the field, usually the status. For a reply, Keep the status may be what you want.
When Keep the status sets a status back after a workflow changed it, that change is counted too, with the workflow’s name.
Loops are stopped
Section titled “Loops are stopped”A rule never acts twice for the same event. Rules never move a ticket back onto a board a rule moved it off in the last 30 days, move one ticket to another board more than five times in 24 hours, or change one ticket more than ten times in 24 hours. A rule a limit stops does nothing, and no later rule acts in its place. Moves and changes made by people do not count.
If a ConnectWise workflow rule on the same board also changes tickets, make sure the two do not undo each other: see Board rules and ConnectWise workflow rules for which jobs belong where and what to check.
Examples
Section titled “Examples”Urgent tickets to Escalation, created urgent or changed to urgent: on the Service board, tick New ticket and Field changed, Priority is “Priority 1 - Emergency”, Move to board Escalation, Set status Pending.
A company type to its own board: New ticket, Company type is “Team Green”, Move to board Green, Set status New.
Cancel vendor auto-replies: New ticket, Sender domain is vendor-alerts.example, AI condition “the email is an
automatic notice that needs no work”, Set status Canceled.
Cancel tickets the client already reported: New ticket, AI condition “the client already reported this same problem in an open ticket”, This ticket and the company’s other tickets, Set status Canceled. Only earlier tickets are shown, so of two tickets about the same outage the first stands. Leave the board in Preview for a while first and read the suggestions, with their related tickets, before switching it to Live.
Bundle repeat reports: the same rule with Bundle into the related ticket instead of Set status, and the board’s “Child Ticket” status. Each repeat is bundled under the first report, and its technician sees Customer Responded on it. Run it in Preview first, as above.
Complete a ticket when the client confirms the fix: Client replied, Status is “Waiting on Client”, AI condition “the client confirms the problem is fixed and nothing more is needed”, Set status Completed. A second rule below it, Client replied, Status is “Waiting on Client”, Set status Requeued, puts any other reply back in the queue.
Leave the status alone on a plain “thanks”: Client replied, Reply contains “thanks”, AI condition “the client only thanks us and asks for nothing more”, Keep the status. Put it above any rule that requeues on a reply.
Keep a resolved ticket resolved on a “thanks”: Client replied, Status is “Resolved”, Reply contains “thanks”, AI condition “the client only thanks us and asks for nothing more”, Keep the status. If the email connector reopens the ticket with the reply, the rule still matches, clears Customer Responded and sets it back to Resolved.
Hand the ticket back to its technician: Client replied, Status is “Waiting on Client”, Make the last technician the owner, Add the last technician as a resource, Close open appointments.
Handle a security alert: New ticket, AI condition “the ticket reports a suspected security breach”, Set priority Priority 1 - Emergency Response, Apply template Security incident, Make a member the owner Dana Lee. The ticket gets the template’s type, subtype and tasks, the rule’s own priority, and Dana as its owner.
