When Chili Piper round robin isn't assigning meetings to available reps, the cause is almost always a broken calendar sync, a misconfigured queue rule, or reps failing eligibility conditions. Check calendar connections first, then verify queue membership, distribution weights, working hours, and routing rules. Most teams get this wrong by blaming the algorithm when the real issue is stale OAuth tokens or overly strict rules.
Start With Calendar Sync — The #1 Culprit
Chili Piper can't book a rep who looks unavailable, and a rep looks unavailable when their calendar sync is broken. When a Google or Microsoft OAuth token expires or a user changes their password, Chili Piper stops reading free/busy data. The system treats that rep as fully booked and skips them in rotation.
Go to Admin Center > Users and look for red sync warnings or "reconnect calendar" flags. Have the affected rep disconnect and reconnect their calendar in their personal settings. For Microsoft 365, confirm the calendar isn't being blocked by a Conditional Access policy — this trips up a surprising number of enterprise deployments.
Confirm Free/Busy Permissions
Even with a connected calendar, if the rep's free/busy visibility is restricted at the Google Workspace or Microsoft admin level, Chili Piper may read every slot as busy. Check that calendar sharing permissions allow at least free/busy access for the Chili Piper service account.
Verify Queue Membership and Status
A rep can be fully available and still get skipped if they're not actually in the routing queue. Open the specific Queue tied to your form or handoff, then confirm:
- The rep is added as a queue member and their status is Active, not paused
- Their distribution weight isn't set to 0 (a weight of 0 removes them from rotation entirely)
- They haven't hit a daily or weekly meeting cap you configured under distribution limits
Paused reps are common after PTO. Someone toggles a rep off and forgets to re-enable them. If assignments cluster on two or three people, check whether everyone else is silently paused.
Check Working Hours and Time Zones
Mismatched working hours quietly break assignment. If a rep's working hours in Chili Piper are set to a different time zone than their actual location, the router may think they're offline during the prospect's requested window. Confirm each rep's working hours and time zone match their calendar's time zone. This matters most for distributed teams booking across regions — the same problem that hurts teams trying to improve pipeline velocity without adding headcount.
Audit Routing Rules and Eligibility Conditions
Routing rules decide which queue a lead hits and which reps qualify. Over-scoped rules are the second most common failure after calendar sync.
If you route by territory, industry, or company size, a lead that doesn't match any rule either falls through or lands in a queue with no eligible reps. Test with the Preview or Debug tool in the router — it shows exactly which rule fired and which reps were considered. If the debug output shows zero eligible reps, your conditions are too tight or your CRM field values don't match your rule values (e.g., "USA" vs "United States").
Match CRM Field Values Exactly
Chili Piper routing reads Salesforce or HubSpot field values literally. A rule expecting Enterprise won't match a record storing enterprise or ENT. Normalize your field values or use "contains" logic where your data is inconsistent.
Distribution Type Matters
Chili Piper offers several distribution methods, and picking the wrong one changes assignment behavior.
| Distribution Type | Behavior | Common Issue |
|---|---|---|
| Round robin | Even rotation across reps | Skips reps with sync or cap issues |
| Weighted | Distributes by assigned weight | Weight of 0 excludes a rep |
| Availability-based | Books whoever has open slots first | Favors reps with emptier calendars |
| Account-based | Routes to existing account owner | Fails if owner field is blank |
If you use account-based routing and the owner field is empty on a record, Chili Piper can't resolve an owner and either errors out or falls back to a default queue. Confirm your fallback logic exists.
Clear Booking Conflicts and Buffer Rules
Aggressive buffer times and minimum-notice settings shrink availability. If you set a 60-minute buffer around every meeting plus a 24-hour minimum booking notice, reps with busy calendars show almost no open slots. Loosen buffers to test whether availability rules — not the round robin itself — are the constraint.
Reproduce and Isolate the Problem
Don't guess. Reproduce the booking as a test prospect and watch the router debug log step by step. Chili Piper's routing documentation explains how to read distribution logs and confirm which rep was selected and why others were excluded. Isolate one variable at a time: reconnect a calendar, check a single queue, test one rule. Fixing everything at once hides which change actually solved it.
For recurring assignment failures across a growing team, the root cause is often data hygiene rather than tooling. The same principle applies when deciding when to move from rule-based to predictive models — clean, consistent inputs matter more than the routing engine.
Key Takeaways
Check calendar sync first — expired OAuth tokens and blocked free/busy access cause most skipped reps. Confirm queue membership, active status, and non-zero distribution weights. Verify working hours and time zones match each rep's location. Audit routing rules with the debug tool and normalize CRM field values so rules actually match. Loosen aggressive buffers and minimum-notice settings if availability looks artificially empty. Always reproduce the issue with a test booking and isolate one variable at a time rather than changing everything at once.