Auto-attendant/CCR administration

[dc2008]

Hello, I was hoping to get some input on the best practices to configure and administer the auto-attendant for the BCM50. Our company is in the process of deploying BCM50's to our regional offices. We currently have 7 locations setup and have about 42 more to go. One unexpected problem is the auto-attendant. We had a company standard recording for both the company greeting and the CCR but our regional offices are requesting more personalized greetings with the associates names listed in CCR tree instead of just their job title like we had planned. We like the personalized greeting idea but we are concerned that this will be an administrative nightmare by having to re-record the messages constantly due to employee turn-over and job title changes. Does anyone have a similar setup? If so how do you maintain them?
Thanks for the help!

 

[Deweyhumbolt]

You build an Info mox, not an Info Path, and attach it to the CCR tree as a Leave Message Path. It will require them to press * in front of the person they want, as in "For Lindsey Lohen, press * (star) 221". But it's a message they can record as easily as their own mbox, plus it's password protected.

Adversity is Opportunity

 

[DBrewsky]

You can also create a lower level sub-menu. Record the names and their extension (won't need a * here before the extension). Since it's a menu, you will also need to have at least one option programmed (not necessarily given to the customer). This option can be "To repeat this menu, press 8", or "To return to the main menu press 5". Then you setup an info path with return to where ever your "options" say and you're on your way.. But, as a menu level you need at least to have one option programmed...

Also, another method is for the caller to press # to enter the dial-by-name directory. Instead of "spelling" a name, they can press # again and listen to the first person, then press the proper option to go to the next name on down the list....

 

[Deweyhumbolt]

PRI's should be set one as Primary and the other two as Secondary. Master is only for Point-to-Point. This will allow one PRI to get timing from the CO and the other two to clock off of it.

Adversity is Opportunity

 

[Deweyhumbolt]

Sorry, right post, wrong thread.

Adversity is Opportunity

 

[vztech]

Dc you can try as Dewey suggested but I had an issue trying this myself one time.

When the caller hit *XXX it would just repeat the menu.

It's only dialtone-VZ