> ## Documentation Index > Fetch the complete documentation index at: https://docs.lumisreach.com/llms.txt > Use this file to discover all available pages before exploring further. # Round-Robin Distribution > Distribute calls and bookings evenly across your team. Automatically distribute calls and appointments across team members. Keep workloads balanced. *** ## What is round-robin? Instead of all calls going to one person, round-robin distributes them: ``` Call 1 → Alice Call 2 → Bob Call 3 → Carol Call 4 → Alice (back to start) ... ``` This ensures fair distribution and prevents burnout. *** ## Distribution methods ### Simple round-robin Each person gets the next call in sequence: * **Pros:** Perfectly equal distribution * **Cons:** Doesn't account for availability ### Availability-based Only routes to available team members: * **Pros:** Respects calendars and working hours * **Cons:** Some may get more if others are busy ### Weighted round-robin Some team members get more: ``` Alice: 40% (senior, higher capacity) Bob: 30% Carol: 30% ``` * **Pros:** Account for experience/capacity * **Cons:** Requires more setup ### Least recent Routes to whoever hasn't had a call in longest: * **Pros:** Natural balancing * **Cons:** May not respect preferences *** ## Setting up round-robin Go to Settings → Team → Create Team Select who should be in the rotation Pick your distribution style Route calls to this team instead of individual *** ## Configuration options ### Working hours Respect each member's schedule: * **Only route during working hours** * **Skip members who are marked away** * **Account for lunch breaks** ### Capacity limits Set maximum appointments per person: ``` Alice: Max 8 calls/day Bob: Max 6 calls/day Carol: Max 10 calls/day ``` Once capacity is hit, skip to next person. ### Priority routing Some calls go to specific people first: ``` VIP customers → Senior team member first New leads → Sales team Support → Support team ``` *** ## Round-robin for bookings When customers book appointments, distribute across team: 1. **Show combined availability** - All team members' open slots 2. **Customer picks time** - Any available slot works 3. **Assign automatically** - System picks who gets it Or let customers choose: 1. **Show team members** - Display available people 2. **Customer picks person** - They choose who they want 3. **Book directly** - Goes to chosen calendar *** ## Monitoring distribution Track how calls are distributed: | Team Member | This Week | This Month | All Time | | ----------- | --------- | ---------- | --------- | | Alice | 12 calls | 48 calls | 520 calls | | Bob | 10 calls | 45 calls | 498 calls | | Carol | 11 calls | 47 calls | 512 calls | Look for imbalances and adjust weights if needed. *** ## Handling unavailability When someone is unavailable: * **Skip them** in the rotation * **Try next person** automatically * **Queue for later** if no one available * **Notify admin** if all unavailable *** ## Use cases ### Sales team Distribute leads evenly: ``` New lead comes in → Assign to salesperson → They follow up → Track who converts best ``` ### Service technicians Balance service calls: ``` Customer books → Assign to available tech → Based on location, skill, capacity ``` ### Support team Route support calls: ``` Support call → First available agent → Based on who answered least recently ``` *** ## Best practices 3-7 people per rotation works best. Larger teams make it harder to track. Check distribution reports. Adjust weights if someone's overloaded. Mark team members away when they're out. The system will skip them. If your team spans zones, set working hours per member. *** Configure team distribution Learn about team management