Hi Everyone,
We're in the middle of converting users from Audix to Modular Messaging (3.0). We have many phantom voice mail accounts that are options off of various auto attendants (application in MM). Because there is no physical phone for these phantom mailboxes, users are required to check for messages from other users' phones.
If a phantom mailbox user tries accessing MM from a users phone that has a mailbox associated with that extension, the system requests a password (thinking that the user of the extension is loggin in).
Instead of pressing * # to have the system prompt them for a mailbox number and password, the person tries entering their phantom mailbox password. This of course gives them an "invalid login" reply from the system. Eventually they lock up the account because they feel that re-trying the same incorrec digits will eventually work. Isn't that the definition of insanity?
I've tried to teach the user community that they need to press * then # to get the system to prompt them for a mailbox number, but we're talking about the average user who isn't interested in listening to prompts or remembering clever key sequences like * #.
The old tried and true Intuity Audix would prompt for an extension and then password every time. Ah, the good old days. Can MM be made to behave like Audix, or ... can an application be written to prompt users for thier mailbox, then prompt them for thier password, then log them in to their account and bypass the system auto attendant?
Has anyone else run in to this problem, or am I just having a bad week?
Any suggestions?
Thanks,
Scott
We're in the middle of converting users from Audix to Modular Messaging (3.0). We have many phantom voice mail accounts that are options off of various auto attendants (application in MM). Because there is no physical phone for these phantom mailboxes, users are required to check for messages from other users' phones.
If a phantom mailbox user tries accessing MM from a users phone that has a mailbox associated with that extension, the system requests a password (thinking that the user of the extension is loggin in).
Instead of pressing * # to have the system prompt them for a mailbox number and password, the person tries entering their phantom mailbox password. This of course gives them an "invalid login" reply from the system. Eventually they lock up the account because they feel that re-trying the same incorrec digits will eventually work. Isn't that the definition of insanity?
I've tried to teach the user community that they need to press * then # to get the system to prompt them for a mailbox number, but we're talking about the average user who isn't interested in listening to prompts or remembering clever key sequences like * #.
The old tried and true Intuity Audix would prompt for an extension and then password every time. Ah, the good old days. Can MM be made to behave like Audix, or ... can an application be written to prompt users for thier mailbox, then prompt them for thier password, then log them in to their account and bypass the system auto attendant?
Has anyone else run in to this problem, or am I just having a bad week?
Any suggestions?
Thanks,
Scott