Round Robin

Distribute ownership across team members in a balanced sequence

How Round Robin Works

Round Robin rotates assignment across selected teammates so no single owner receives all inbound work. In agents, this is useful when the model should decide when to hand off while the distribution itself stays fair and predictable. The tool tracks rotation state internally, ensuring each eligible team member is assigned in sequence before the cycle resets.

Configuration

Inputs

Prompt · string · required

Instructions that tell the agent when to use round robin.

Team member options · object · required

The pool of users eligible for assignment. The agent can choose dynamically depending on context.

Outputs

assigned_user_id · string · required

The selected teammate ID for this assignment decision.

assignment_index · number

The position used in the rotation cycle for the selected user.

assignment_success · boolean · required

Whether the round robin assignment completed successfully.

pool_size · number

Total number of eligible team members in the current rotation pool.

Use Cases

Inbound Lead Distribution

Condition: High-intent trial event with no existing owner
Action: Round robin assignment to onboarding specialists
Outcome: New leads are distributed evenly across the team

Support Escalation Routing

Condition: Support escalation detected by the agent
Action: Round robin assignment to on-call CSM queue
Outcome: Urgent work is balanced while preserving response speed

New Account Onboarding

Condition: Account created with no assigned CSM
Action: Round robin across onboarding team
Outcome: Every new customer gets a dedicated owner without manual triage

Regional Team Assignment

Condition: User timezone falls within EMEA business hours
Action: Round robin among EMEA-based team members
Outcome: Customers are matched with regionally appropriate owners

Best Practices

Pool Management

• Include only active teammates in the rotation pool.
• Remove unavailable or out-of-office users to avoid failed handoffs.
• Review the pool periodically to reflect team changes and new hires.

Integration with Other Tools

• Persist the selected owner in a user property with Set Custom Property so downstream tools and future runs can reference it.
• Pair with Assign CSM when you need to formalize the round robin result as a primary or secondary CSM relationship.
• Avoid re-assigning in every run unless your process requires it — check for an existing owner first.

Fair Distribution

• Keep pools focused by role or region rather than mixing all team members into one large rotation.
• Monitor assignment counts to verify the rotation is balanced over time.
• Use the assignment_index output to audit rotation fairness in reporting dashboards.