Weight

Weight fields control how agents are prioritized during task assignment. Each agent has a numeric weight value, and the field’s mode determines whether higher values mean more or fewer assignments. This gives you flexible control over distribution patterns like seniority-based routing or workload balancing.

Creating a Weight Field

1. Navigate to the Fields tab in your group
2. Click Add a New Field

Click to enlarge

3. Select Weight as the field type
4. Enter a Display Label (e.g., “Seniority” or “In Progress Tasks”)
5. Choose a Weight Mode (Prioritize or De-prioritize)
6. Click Save

Understanding Weight Modes

Weight fields have two modes that determine how the numeric value affects agent prioritization:

Click to enlarge

Click to enlarge

Prioritize Mode

Higher weight values mean the agent receives more assignments. Use this when you want certain agents to handle more tasks based on their seniority, expertise, or capacity.

Example: A senior team member with weight 5 will be selected more often than a junior member with weight 2.

De-prioritize Mode

Higher weight values mean the agent receives fewer assignments. Use this when you want to balance workload based on current task counts or other load indicators.

Example: An agent with 8 in-progress tasks will be selected less often than an agent with 2 in-progress tasks.

How It Works When Adding Agents

When you add an agent to the group, the Weight field appears as a numeric input. Enter the initial weight value for each agent.

Click to enlarge

Use Cases

Workload Balancing

Use De-prioritize mode to distribute tasks fairly based on current workload. Agents with more in-progress tasks get a higher weight value, making them less likely to receive new assignments.

This is the approach used in the ClickUp Workload Balancing guide, where an automation periodically counts each agent’s active tasks and updates their weight accordingly.

Seniority-Based Routing

Use Prioritize mode to route more tasks to experienced team members. Assign higher weight values to senior agents who should handle a larger share of incoming work.

Example values:

• Junior agent: weight 1
• Mid-level agent: weight 3
• Senior agent: weight 5

Dynamic Priority with API

Weight values can be updated programmatically via the EnforcedFlow API. This enables dynamic routing based on real-time data:

• Task counts: Update weights based on current workload (as shown in the workload balancing guide)
• Availability: Temporarily increase weight for agents who are busy or unavailable
• Performance metrics: Adjust routing based on response times or customer satisfaction scores

The API endpoint to update an agent’s weight:

PUT /api/v1/advanced-round-robin/{groupId}/agents

{
  "filter": {
    "meta": {
      "your_agent_identifier": "agent-id"
    }
  },
  "data": {
    "fields": {
      "your_weight_field": 5
    }
  }
}

Using with Integrations

Weight fields work seamlessly with Zapier, Make, and n8n integrations. The Workload Balancing guide demonstrates a complete implementation using Zapier to:

1. Assign tasks to the agent with the lowest workload
2. Periodically update weight values based on each agent’s active task count

For Make and n8n users, refer to the API request formats in the workload balancing guide’s API section.