Embedded VM and night auto attendant 1

[EmuDan]

Is there any way to use a time profile to have calls automatically go to a night auto attendant, but then to be able to manually switch off the night attendant with a button the next morning? From what I've read, this doesn't seem possible in embedded voicemail.

Dan

I blame Avaya.

 

[AACon]

Time profiles will always override hunt group status (ie, set with a button), gotta use one or the other...if used the correct way.

Alternatively, if you only specify times you are closed, rather than times you are open, it could work.
You would say you are closed monday from midnight to 8, then from 5 to midnight, for each day (if 8-5 of course).
When closed, you would hit auto attendant night.
When open (after 8) you would go wherever.
Except, that wherever could be a group, that is *still* out of service/night mode, and going to a fallback to an auto attendant, so technically, you'd still be closed, until you hit that oos/night service button again.

So yes, okay, you can do it. But when it's 1PM and they aren't getting calls, and forgot to press the button, you'll hear about how difficult it is to use and how it should be automated. Been there.

-Austin
ACE: Implement IP Office

 

[TouchToneTommy]

You could use the time profile to send the calls to a sequential hunt group that has the user that is forwarded to the short code that invokes the Night Auto Attendant, then put a HG OOS button on a phone with the OOS Fallback to the Main hunt group. Enabling the button would cause the calls to ring to the Main hunt group until the time profile expires.

 

[EmuDan]

And when the time profile expires, it will just go to the Default for the incoming call route, which is also the Main hunt group. So then, the receptionist would just need to press the HG OOS button once more, any time after 9am to put the night group back in service.. got it.

Dan

I blame Avaya.