ACD and attendant console
Set up the attendant console: overview and wizard
Create a console with the wizard in five steps and maintain it in tabs afterwards.
In EasyUC: Calling Features → Calls → Attendant Console
Images come from the EasyUC lab. Names and example values provide orientation. A different interface language is indicated beside the relevant image.
What it is for
The Attendant Console is the attendant console of EasyUC. A console bundles the reception: queues, attendants with their devices, the busy lamp field and the behaviour by day and night. Calls reach a queue through a script. There an attendant answers them and transfers them.
EasyUC itself keeps every call that comes through the console on a CTI port. Hold, transfer, consultation and undo therefore work from the console, independent of the device. Cisco devices with CTI control can additionally be answered by click.
You set up a new console with a wizard in five steps. Afterwards you maintain the same content in tabs and see in the checklist whether everything is ready.
Prerequisites
- Licence module
acd. For Cisco devices and CUCM calls additionallycucm, for Teams devices and Teams callsteams. - Permission:
ROLE_APP_ACD_WORKSPACEandROLE_APP_ACD_ATTENDANTto view, additionallyROLE_APP_ACD_ATTENDANT_EDITto change. Administrators withROLE_APP_ADMIN,ROLE_OWNER,ROLE_ADMINorROLE_SUPER_ADMINhave all rights of the area. - A CTI application user and a Call Control Group with free CTI ports (chapter "Call Control Groups and CTI ports").
- A script with a number per queue (chapter "Create a script with a number"). The queue can also be saved without a script and completed later.
- At least one phonebook if attendants are to search for contacts (chapter "Phonebooks for agents and the attendant console").
Step by step: New console with the wizard
Step by step: Maintain an existing console
Step by step: Delete a console
Fields and options
| Field / action | Meaning and use |
|---|---|
| Call control (overview) | State of the runtime: running, delayed or no free CTI port, disrupted: not reachable, calls continue on the phones, not active: call control is running, the console is disabled, not connected yet. Next to it Free CTI ports: … of …. |
| Routes (overview) | Per pairing of call source and device type: available, disrupted, not active, not connected, follows with round 2c, unknown, call control not reachable. |
| Key figures per console | Signed in, Ready, Waiting, Longest wait, plus the current operating mode. Without a connection to the runtime: No live data (call control not reachable). |
| Setup: … of 5 steps done | Progress of the wizard with a percentage bar. |
| Save and continue / Save and exit / Leave | Buttons of the wizard. A step with errors is not saved; notices (yellow) allow you to continue. |
| Current operation | Day, Night or Special with its source. Switch with Automatic or the operating mode; Valid until selects the duration. See chapter "Opening hours and operating modes". |
| Delete console | Removes queues, keys and assignments. Attendant logins, their devices and the agents are kept. |
| Sign-in address | Below the overview you find the address at which attendants sign in: https://<server>/admin/attendant. |
Check the result and narrow down errors
- The tile of the console shows the operating mode and live figures. The Checklist tab shows only green points or Everything is ready.
- The attendant console is not available on this server yet. It needs an update of admin-api; until then nothing can be saved. The server is older than the user interface.
- Please check … marked fields. A step contains errors. The fields are marked.
- This step has errors and will not be saved. Leave anyway? Prompt when leaving the wizard.
- This tab has unsaved changes. Discard them? Prompt when switching tabs.
- The preview is not available on this server yet. or The preview could not be opened. Allow the browser to open a new window and try again.
- Saving failed. possibly with an error ID: Note the ID for your system support.