Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management |
| Access | Admin |
Removing somebody from Zendesk WFM, and why deactivating them in Support is usually the step that matters.
The order
- Reassign their open tickets in Support.
- Remove them from future schedules.
- Remove them from their team here.
- Deactivate them in Support.
Two products, two actions
Deactivating in Support ends their access. Removing them from a team here stops them appearing in schedules and skewing team figures.
Neither does the other, and doing only one leaves a loose end.
Take them out of the schedule first
Somebody scheduled who has left leaves a gap that looks covered. That is the version of this mistake that reaches customers.
Check the published period as well as future ones.
Keep the history
Their past activity is part of your historical data, and forecasting learns from it. Removing them from a team does not remove that, which is what you want.
Watch the team figures
Somebody left in a team with no activity drags team averages down. That is the quiet reason to keep membership current beyond tidiness.
Check seat usage afterwards
Where seats here are counted separately, removing somebody may free one. Worth confirming rather than assuming it followed from Support.
Put it on the leaver checklist
Alongside the Support steps. This is precisely the task that gets forgotten because it lives in a different product.
Comments
0 comments
Article is closed for comments.