System Workflows, Workforce
Automation
The ready made workflows that keep agent status and sessions in step.
What They Are
UNICONNECT AI ships workflows that run on their own. They carry a System badge on their cards in Configuration → Automation. Three of them look after the workforce side: they keep a user's status in step with calls and with the telephone system, and they update the status when a user's sessions end.
| Workflow | When it runs | What it does |
|---|---|---|
| Sync call status to user percent status | When a call status changes | Keeps the agent's presence status in step with the call, for example Talking while a call is connected. |
| Sync 3CX status to user percent status | When the presence on 3CX changes | Keeps the platform status in step with the telephone system. |
| End All User Active Sessions | When all of a user's sessions end | Updates the user's status so the Workforce Monitor no longer shows them as active. |
Info: System workflows carry a System badge on their cards and run without anyone starting them. The statuses they set, such as Talking, need to exist and be active in Status Management.
What You See
- Status changes you did not make. When User A answers a call, the presence moves to Talking, and after the call it follows the call status. The change comes from a system workflow, not from a person.
- Offline after a disconnect. When all of an agent's sessions end, the status follows.
- Matching statuses. A status set on 3CX appears on the platform and the other way round.
Working with Them
- Read before you edit. Open a workflow in the designer and read its Details and History tabs first.
- Add your own beside them. For rules such as a notification when an agent exceeds a limit, build a separate workflow. See Workflow Builder.
- Check History after a change. The History tab lists runs, so you can see that a workflow fired.
Important: Changes to a System workflow affect every user. Save a change only when you understand what the workflow feeds.