Behavior
- Assigns each call to a route based on the configured percentage distribution
- Percentages must sum to 100 (validated at save time)
- Routes are processed probabilistically — over time, traffic distribution matches the configured percentages
Configuration
| Parameter | Type | Default | Description |
|---|---|---|---|
routes | array | 2 routes at 50/50 | List of route definitions (see below) |
Route definition
Each entry inroutes:
| Field | Type | Description |
|---|---|---|
label | string | Display label for the route |
percentage | number | Percentage of traffic (0–100). All routes must sum to exactly 100. |
Output handles
Output handles are dynamic — each route generates its own handle:| Handle | Description |
|---|---|
| [Route Label] | Call was assigned to this route |
| Handle | Percentage |
|---|---|
| Route A | 50% |
| Route B | 50% |
Use cases
A/B testing
A/B testing
Split traffic 50/50 between two different greeting scripts or menu structures to measure which performs better.
Gradual rollout
Gradual rollout
Route 10% of calls to a new AI Agent flow and 90% to the existing IVR. Increase the percentage as confidence grows.
Load distribution
Load distribution
Split calls across three regional support centers: 40% North America, 35% Europe, 25% Asia.