If left running overnight, Ignite becomes unresponsive or responds very slowly. It cannot receive ACD content or acknowledge and change agent or employee states.
Critical
Agents cannot take ACD calls while Ignite is in this state.
If Ignite is left running overnight, a server maintenance cycle could have taken place, leaving Ignite in a non-functional state. To resolve this issue, shut down and restart Ignite and sign in again.
We recommend you exit Ignite at the end of each agent's shift to avoid this issue. Following server maintenance, the next time Ignite is launched, any changes to the Enterprise Server configuration will be updated automatically.
To exit Ignite
You must exit Ignite to ensure Make Busy or Do Not Disturb statistics do not get created erroneously at the end of the agent's shift.
7.0