Page History

...

1. Go to Priority Rules by clicking the priority rules link on the NextTicket screen.
2. Click the Advanced Rule button to open the Advanced Rule pop-up window.
   
3. Fill in the following fields for adding an advanced rule：
   
   1. You can use the toggle in front of the rule to enable or disable the added advanced rules.
   2. Rule Name - Enter a unique rule name.
   3. Rule Description - Enter a description for the rule. (Optional)
   4. Rule
    
   1. - Create conditions for the advanced rule. Add more groups or conditions if you need to. 
      

      Tip

      Condition fields for Advanced Rules in NextTicket Manager for ConnectWise Manage app: When configuring advanced rules, you can select Company Type as a condition. Using the Company Type condition allows you to adjust ticket prioritization by adding or subtracting corresponding points to tickets based on different company types. Image Added To provide you with greater flexibility when configuring advanced rules, you can also select pre-configured custom fields in the ConnectWise app's User-Defined Fields (UDFs) feature. Any changes you make to these custom fields in the ConnectWise app's company custom fields feature will be synchronized in real-time to MSPbots every hour and automatically reflected in the condition field list of the advanced rules. Image Added Condition fields for Advanced Rules in NextTicket Manager for AutoTask app: To meet your various personalized needs when configuring advanced rules, you can select pre-configured custom fields in the AutoTask app's User-Defined Fields (UDFs) feature. For example, custom fields from the contact modules. Any additions or deletions you make to custom fields in the AutoTask UDF feature will be synchronized in real-time to MSPbots every 5 hours and automatically reflected in the condition field list of the advanced rules. Image Added

      • You can also do the following actions in this section: 

        • If you want to duplicate a specific condition within this advanced rule, click the Clone Image Modifiedbutton. This will copy the condition and its associated score, placing it as a new condition under the existing rule. You can then modify the value and score of this new condition as needed. This simplifies the process of setting up similar conditions. 
          Image Modified

        • If you want to add an empty condition, click

   the

   1. • • the Add Image Modified icon and then configure the condition as needed.

        • Click the Delete Image Modified icon to delete the condition.
   
   TipWhen configuring the Advanced Rules for the NextTicket Manager for ConnectWise Manage app, you can select companyType as a condition. Using the companyType condition allows you to adjust ticket prioritization by adding add adding or subtracting corresponding points to tickets based on different company types.
   Image Removed
   2. The Advanced Rule feature supports positive and negative points.
      Image Modified
   3. If you want to ensure prompt handling of tickets that meet advanced priority rules, you can activate the For every switch that allows you to assign points based on time intervals. This helps improve the efficiency of ticket processing and prevents tickets from aging without being handled due to attribute reasons. You can configure the conditions for scoring based on time intervals to ensure that tickets are prioritized appropriately.
      Image Modified
      
      • For tickets that meet the advanced rule, points will be added starting from the following date conditions, and incrementally based on each Minute, Hour, Day, or Business Day, to elevate their priority.
        • NextTicket for ConnectWise Manage
          • required_date - The date when the ticket is required
          • estimated_start_date - The estimated start date for the ticket
          • last_updated - The date when the ticket was last updated
          • date_entered - The date when the ticket was entered
        • NextTicket for Autotask
          • completedDate - The date when the ticket was completed 
          • createDate - The date when the ticket was created 
          • dueDateTime - The deadline for the ticket 
          • firstResponseDateTime - The date and time of the first response to the ticket 
          • firstResponseDueDateTime - The deadline for the first response to the ticket 
          • lastActivityDate - The date of the last activity on the ticket 
          • lastCustomerNotificationDateTime - The date and time of the last notification sent to the customer 
          • lastCustomerVisibleActivityDateTime - The date and time of the last customer-visible activity 
          • lastTrackedModificationDateTime - The date and time of the last tracked modification 
          • resolutionPlanDateTime - The date and time of the resolution plan was created 
          • resolutionPlanDueDateTime - The deadline for the resolution plan 
          • resolvedDateTime - The date and time when the ticket was resolved 
          • resolvedDueDateTime - The deadline for resolving the ticket 
        • NextTicket for Halo

          • date_assigned - The date when the ticket was assigned 

          • date_occurred - The date when the ticket occurred 

          • deadline_date - The deadline date for the ticket.

          • fix_by_date - The date when the ticket is fixed.

          • last_action_date - The date of the last action on the ticket.

          • last_incoming_email - The date of the last incoming email related to the ticket.

          • respondby_date - The date when the ticket was responded to

          • start_date - The date when the ticket starts

          • target_date - The target date for the ticket 

        • The condition defaults to closed, with the unit as Day, and the since parameter is blank.

4. Click Save to keep the settings. 

...