Create the rollout
Name the change, label the current and new experience, and choose the starting split.
Zendesk Marketplace App
Rollout Control for Zendesk.
Test Zendesk workflow changes on a controlled slice of tickets before turning them on for everyone.
Rollout Control helps support teams ship changes more safely. Start with a small group of eligible tickets, compare the control and treatment paths, then ramp up when the workflow is ready.
Free plan available. Pro supports ramp-up and multiple active rollouts.
Overview
A safer way to change support workflows.
Big Zendesk changes usually happen all at once. A new macro, AI summary, survey, escalation path, routing rule, or agent process goes live, and the team finds out later if it worked.
Rollout Control gives admins a cleaner middle step. Create a rollout, define which tickets are eligible, choose how many should receive the new experience, and keep the rest on the current path as the control group.
Limit who enters
Use brand, group, form, channel, required tags, or excluded tags to keep the test focused.
Track the result
Rollout Control writes consistent fields and tags so the enrollment can be filtered in Zendesk Explore.
Screenshots
Built for the Zendesk admin flow.
Rollout Control runs from the Zendesk nav bar for admins and shows ticket enrollment status in the ticket sidebar.
See every rollout in one place.
Track active, paused, draft, and completed rollouts from a simple admin dashboard.
Build the test without code.
Choose the treatment percentage, name both experiences, and preview the tags and fields that will be written.
Give agents clear status.
The ticket sidebar shows whether a ticket is enrolled and whether it landed in control or treatment.
Features
Made for controlled support operations changes.
Rollout Control is useful when you want to test a new process without guessing, over-launching, or relying on agents to remember who should follow which path.
Control and treatment groups
Keep today’s workflow as the control and send a defined percentage of tickets to the new experience.
Deterministic ticket splits
Tickets are assigned by ticket ID, so the same eligible ticket always lands in the same group.
Eligibility rules
Target rollouts by brand, group, form, channel, required tags, or excluded tags.
Ramp-up controls
Start small, then increase the treatment percentage when the change is performing well.
Explore-ready tracking
Use generated tags and ticket fields to filter enrolled tickets, control tickets, and treatment tickets.
Pause and complete
Pause a rollout, resume it, or mark it complete without changing existing assignments.
Import and export
Export rollout configuration as JSON or import a saved setup into the create flow.
Health checks
Check required fields, custom objects, managed triggers, webhook setup, and account readiness.
No external backend
Rollout Control is designed to run inside Zendesk and write enrollment data back to your own tickets.
Plans
Start simple. Upgrade when rollout volume grows.
The free plan is meant for basic validation. Pro is for teams that need more control over rollout size and multiple tests running at once.
Free
Run one active rollout at a time with a 50/50 split between control and treatment.
Pro
Use flexible treatment percentages, ramp up over time, and manage multiple active rollouts for different workflows.
Use cases
Good for changes you do not want to ship blind.
Rollout Control is not trying to replace your reporting stack. It gives Zendesk admins a practical way to separate tickets into clean groups so changes can be measured instead of debated.
AI summaries
Send a small percentage of eligible tickets through a new AI summary process before rolling it out broadly.
Escalation paths
Test a new escalation flow with selected ticket types, groups, or brands.
Surveys and QA
Compare survey timing, QA prompts, or follow-up workflows without changing every ticket at once.
Macros and routing
Validate updates to agent guidance, routing behavior, or internal process steps on a controlled group first.
Privacy
Designed to stay inside Zendesk.
Rollout Control runs within the Zendesk App Framework and uses Zendesk data only to manage rollout configuration, enroll eligible tickets, and show ticket enrollment status.
It does not sell customer data, use customer data for advertising, or share customer data with unauthorized third parties.
An admin API token may be requested only when an action needs to write enrollment data back to tickets in your own Zendesk account. The app does not use that token for external systems.