You can add and manage hunt groups in bulk using a hunt group CSV. This article covers the specific fields and values needed for the CSV upload of Webex Calling hunt groups.
Known limitations and requirements
-
Before uploading your hunt group CSV, make sure to read Bulk provisioning Webex Calling elements using CSV to understand the CSV conventions.
-
You can either export your current hunt groups, which allows you to add, delete, or modify your existing data set, or you can export a sample set of hunt groups. Once modified, the file can be uploaded through the bulk features.
-
It is important to know the mandatory and optional columns, and information that you’ll need to provide when filling out the CVS template. The specific fields for the hunt group CSV are found in the table below.
-
The maximum amount of hunt groups for each location is 1,000.
-
The maximum amount of rows is 1,000 (not including the header).
Exporting more than 1000 records will export the data in a zip file format. The zip file contains a single CSV with all the data and multiple files less than 1000 records. The files less than 1000 records are generated for the administrators to quickly import any updates, as importing is limited to CSV of less than 1000 records. -
Agents can be users or workspaces. For users, enter the user’s email address. For workspaces, enter the workspace name.
-
Each row can hold a maximum of 50 agents. See Add or edit more than 50 agents at a time for more information.
Use this table to see what fields are mandatory or optional, and what you’ll need to determine when adding or editing hunt groups in bulk.
Columns are either mandatory or optional fields. This varies depending on whether you are using the CSV to add a new hunt group or edit an existing hunt group. |
Column |
Mandatory or optional (Add a hunt group) |
Mandatory or optional (Edit a hunt group) |
Description |
Supported values |
||
---|---|---|---|---|---|---|
Name |
Mandatory |
Mandatory |
Enter the name of the of the hunt group. Hunt group names within the same location need to be uniquely identifiable. If the hunt groups are in a different locations, they can have the same name. |
Example: San Jose Hunt Group Character length: 1-30 |
||
Phone Number |
Mandatory (if extension is left blank) |
Optional |
Enter the hunt group phone number. You must have either a phone number or an extension. |
Only E.164 numbers are allowed for CSV import. Example: +12815550100
|
||
Extension |
Mandatory (if phone number is left blank) |
Optional |
Enter the hunt group extension. You must have either a phone number or an extension. |
Two to six digit extension. 00-999999 |
||
Location |
Mandatory |
Mandatory |
Enter the location to assign this call hunt group. |
Example: San Jose
|
||
Caller ID First Name |
Optional |
Optional |
Enter the first name to display for the hunt group’s calling line ID (CLID). The caller ID is used when call forward is enabled and calls are forwarded out. |
Example: San
Character length: 1-30 |
||
Caller ID Last Name |
Optional |
Optional |
Enter the last name to display for the hunt group’s calling line ID (CLID). The caller ID is used when call forward is enabled and calls are forwarded out. |
Example: Jose
Character length: 1-30 |
||
Language |
Optional |
Optional |
Enter the announcement language for your hunt group. |
Example: en_us |
||
Timezone |
Optional |
Optional |
Enter the hunt group time zone key. This time zone applies to the schedules applied to this hunt group. |
Example: America/Chicago Character length: 1-127 |
||
Call Routing Pattern |
Mandatory |
Optional |
Enter the hunt group routing pattern. Choose one of the supported policies. |
CIRCULAR, REGULAR, SIMULTANEOUS, UNIFORM, WEIGHTED |
||
Advance After Set Number of Rings Enable |
Optional |
Optional |
Enable or disable calls to advance after a set number of rings. If enabled, enter the number of rings in the next column. |
TRUE, FALSE |
||
Advance After Set Number of Rings |
Optional |
Optional |
Enter the number of rings to wait for the currently hunted agent to answer before hunting to the next available agent. |
Range: 1-20 |
||
Advance When Busy Enable |
Optional |
Optional |
If this is enabled, the hunt group won't ring agents when they are on another call. The call advances to the next agent in the hunt group. If the agent has call waiting enabled, and the call is advanced to them, then the all waits until the agent becomes idle again. |
TRUE, FALSE |
||
Forward After Rings Enable |
Optional |
Optional |
Enable or disable unanswered calls to be forwarded to a designated phone number after a set number of rings. |
TRUE, FALSE |
||
Forward Number |
Optional |
Optional |
Enter the phone number where unanswered calls are forwarded. |
Only E.164 numbers are allowed for CSV import. Example: +12815550100
|
||
Forward After Rings |
Optional |
Optional |
Enter the number of rings to wait before forwarding to the designed number. |
Range: 1-99 |
||
Forward After Rings Voicemail Enable |
Optional |
Optional |
Enable or disable unanswered calls forwarding to a voicemail after a set number of rings. |
TRUE, FALSE |
||
Divert When Unreachable Enable |
Optional |
Optional |
Enable or disable unanswered calls diverting to a defined phone number. |
TRUE, FALSE |
||
Divert When Unreachable Number |
Optional |
Optional |
Enter the phone number to divert calls to when unanswered. |
Only E.164 numbers are allowed for CSV import. Example: +12815550100
|
||
Divert When Unreachable Voicemail Enable |
Optional |
Optional |
Enable or disable unanswered calls diveting to a defined voicemail. |
TRUE, FALSE |
||
Distinctive Ringing Enable |
Optional |
Optional |
Enable or disable distinctive ringing for hunt group calls. If enabled, agents will hear distinctive ringing when they receive calls from the hunt group. If enabled, enter the type of distinctive ring pattern you’d like to assign in the next column. |
TRUE, FALSE |
||
Distinctive Ringing Pattern |
Optional |
Optional |
If distinctive ringing is enabled, choose the distinctive ringing ring pattern. Choose from one of the following options. |
NORMAL, LONG_LONG, SHORT_SHORT_LONG, SHORT_LONG_SHORT |
||
Hunt Group Enable |
Optional |
Optional |
Use this column to activate or deactivate the hunt group. |
ENABLED, DISABLED, enabled, disabled |
||
Alternate Number Distinctive Ringing Enable |
Optional |
Optional |
Enable or disable a distinctive ringing for alternate numbers. If enabled, enter the ring patter in the Alternate Numbers Ring Pattern column. |
TRUE, FALSE |
||
Alternate Numbers Action |
Optional |
Optional |
Enter ADD to add the alternate numbers you list in this row. Enter REMOVE to remove the alternate numbers you list in the row. If you enter REPLACE, you will remove all previously entered alternate numbers and replace with the alternate numbers you are adding in this row only. |
ADD, REMOVE, REPLACE |
||
Agent Action |
Optional |
Optional |
Enter ADD to add the agents you list in this row. Enter REMOVE to remove this agents you list in the row. If you enter REPLACE, you will remove all previously entered agents and replace with the agents you are adding in this row only. |
ADD, REMOVE, REPLACE |
||
Alternate Number(s) |
Optional |
Optional |
Enter the alternate number(s) to assign to the hunt group. |
Example: 1112223333
Character length: 1-23 |
||
Alternate Numbers Ring Pattern |
Optional |
Optional |
If distinctive ringing is enabled for alternate numbers, choose the distinctive ringing ring pattern. Choose from one of the supported options. |
NORMAL, LONG_LONG, SHORT_SHORT_LONG, SHORT_LONG_SHORT |
||
Agent1 ID, Agent2 ID… Agent50 ID |
Optional |
Optional |
Enter the agents you’d like to assign to the hunt group. Agents can be users or workspaces. For users, enter the user’s email address. For workspaces, enter the workspace name. |
Example: test@example.com Character length: 1-161 |
||
Agent1 Weight, Agent2 Weight... Agent50 Weight |
Optional |
Optional |
If the call routing policy for the hunt group is weighted, enter the agent’s percentage weighting. |
Range: 0-100 |
Each row can hold a maximum of 50 agents and their associated call routing weight percentage (if applicable). A hunt group can have a maximum of 1,000 agents assigned. To add or edit more than 50 agents, using the CSV file, follow these steps.
1 |
Enter the 50 agents, and their associated call routing weight percentage (if applicable), that you’d like to add or edit on the first row for the hunt group you’re adding or editing. |
||
2 |
On the next row, you only have to enter information in the following columns to add or edit additional agents:
You can leave all other columns blank. |
||
3 |
Continue to do this until you have added all of the agents you need to add or edit.
|
To add hunt groups in bulk, you’ll simply download and fill out a blank CSV template.
Call forwarding settings for a hunt group can’t be modified in bulk. To edit call forwarding for a hunt group, see Edit hunt group call forward settings. |
1 |
From the customer view in https://admin.webex.com, go to Services, and choose . |
2 |
Click . |
3 |
Select a location for the hunt group you'd like to add. |
4 |
Click Download .csv template. |
5 |
Fill out the spreadsheet. |
6 |
Upload the CSV file by dragging and dropping or clicking Choose a file. |
7 |
Click Upload. When successfully uploaded, you can click See Tasks Page for details to view the status of the changes. |
To modify hunt groups in bulk, you’ll simply download the current CSV data and make the necessary changes to the spreadsheet.
Call forwarding settings for a hunt group can’t be modified in bulk. To edit call forwarding for a hunt group, see Edit hunt group call forward settings. |
1 |
From the customer view in https://admin.webex.com, go to Services, and choose . |
||
2 |
Click . |
||
3 |
Select a location for the hunt group you’d like to modify. |
||
4 |
Click Download data.
|
||
5 |
Make the necessary changes to the spreadsheet. |
||
6 |
Upload the modified CSV file by dragging and dropping or clicking Choose a file. |
||
7 |
Click Upload. When successfully uploaded, you can click See Tasks Page for details to view the status of the changes. |