Hunt Groups

It is best practice to have a single primary hunt group, to which all agents are assigned by skill number, and to use this primary hunt group alone for Recorder monitoring of agent events, rather than updating the group numbers in the data source whenever hunt group changes are made. (This is particularly important if you are using the Monitor Only Logged In Extensions feature available in the CT adapter, as the Recorder Integration Service can’t tell if one hunt group or agent out of many required are missing.)

1. Obtain a full list of hunt groups from the Communication Manager using the following command:

   list hunt-group

   A list such as the following will appear: