setup more than one auto attendant?

[ausername]

Hey guys,

I`m currently in the planning phase of a new system we`re trying to put in place and I need your expertise on the matter.

I work at the main office where we have an auto attendant configured.  We make use of day / night mode.  During day mode, calls are being routed via ACD paths.  During night mode, calls are being handled by the auto attendant.  The auto attendant will list options to the caller and based on the caller`s needs, he`ll input a number and the call will be routed to the right person.


We have a second office that we`ve identified that could benifit from its own auto attendant functionalities.

The business needs the second office are different than the main office.  The auto attendant greeting message in place at the main office does not apply to the environement of the second office.

Is it possible to have multiple auto attendant?



Additional details:

- The second office would operate with a day/night mode aswell.  Users would make the switch manually via their desk phones.
- The second office`s auto attendant day greeting message would be different than it`s night mode auto attendant greeting message.
- The main office auto attendant greeting does not apply to the second office.


I`d really appreciate if you guys could help me understand what we should be looking at to put in place for this.

Thanks alot!

[ausername]

halp?!

[bluewhite4]

Really the big question is, are you using embedded voicemail?

Also, are both sites on their own controllers or do they share a controller?

[ausername]

Really the big question is, are you using embedded voicemail?

Also, are both sites on their own controllers or do they share a controller?

yup, we have embeded voicemails and we share the same controller

[bluewhite4]

Then, no. This isn't going to be possible.

[smittydog27]

I'm new here (and also to the 3300).  We have similar situation where we have 50 additional branches hanging off our 3300.  Each branch has their own AA with a different message and routing rules.  This allows us to set up each branch up individually.  (we have a ring all group and AA group for every branch)

Each branch has it's own ring all group.
Users & Devices:Group Programming:Ring Group:ADD:
Ring Group: (already built for branch) (created as 5 digit extension)
Sec element: (server)
Call ring timer:(set as desired)
Then add members to the group:Records to Add: (# of phones in the branch)
                                                                 Members: (starting ext #)

Hope this helps,
Steve

[lundah]

The problem is you can't have multiple day-night schedules on a single embedded VM instance.

[Dutch]

When configs involving ACD get a bit more complex I usually vouch for looking into using CCM/IVR for in depth routing during day/night and Multi site in order to keep things simple while having a (depending on license) diverse toolbox to service the various needs.

[ausername]

What I ended up doing was creating a new tenant and then build an auto attendant with voicemail menu nodes. 

During day mode,  calls are coming in a trusted service level line(this saves me a license) number 6880 and the day routing sends the calls to an ACD path. 

During night mode, the routing for line number 6880 gets send to our voicemail dialing path number.  I have a voicemail mailbox number 8669 that has an extension number of 6880.  This voicemail box is a menu node that list french and english.  Each options has a sub tree which is also a menu node that has 4 options.