Under GDPR, the shift trade feature processes personal data (agent names, schedules) that may constitute employee monitoring.
Before enabling the self-service shift trade module, consult with your Works Council (Betriebsrat) if you operate in Germany. Employee schedule visibility features require formal consultation under the Works Constitution Act.
Ensure the shift trade approval interface meets WCAG accessibility standards.
Our visually impaired supervisor uses a screen reader and reported that the ‘Approve’ and ‘Deny’ buttons in the WFM panel lack ARIA labels. The screen reader announces them as ‘button’ without context, making it impossible to distinguish between approve and deny without sighted assistance.
We tracked the impact of stuck shift trades on our SLA.
| Week | Stuck Trades | Unplanned Understaffing | SLA Impact |
|---|---|---|---|
| 1 | 3 | 2 agents | -1.2% SLA |
| 2 | 7 | 5 agents | -3.8% SLA |
| 3 | 12 | 8 agents | -6.1% SLA |
Each stuck trade means an agent doesn’t show up because they think the trade was approved, but their replacement doesn’t know they are supposed to cover.
If you use Microsoft Teams alongside GC for internal communications, shift trade notifications can be routed to Teams via a Power Automate flow.
When a trade request is submitted, our PowerShell webhook fires a Teams Adaptive Card to the supervisor’s Teams channel. The supervisor can approve directly from Teams without logging into the GC WFM module.
In CIC, shift trades were managed through the IC Business Manager thick client. The supervisor had to manually approve each trade in a modal dialog.
Genesys Cloud’s web-based approval workflow is cleaner, but it occasionally loses the approval state. We’ve seen trades stuck in ‘Pending’ for days because the supervisor clicked ‘Approve’ but the WebSocket event was dropped during a network hiccup.