Difference between revisions of "Triggering Alternate Routing"
Jump to navigation
Jump to search
(One intermediate revision by the same user not shown) | |||
Line 8: | Line 8: | ||
*Enable Day & Night Mode, found under Call Routing=>Incoming | *Enable Day & Night Mode, found under Call Routing=>Incoming | ||
*Click Edit Hours and set the hours (we will not be following these hours, but they need to be set regardless) | *Click Edit Hours and set the hours (we will not be following these hours, but they need to be set regardless) | ||
− | *Go to Call Routing=>Incoming, the page will say | + | *Go to Call Routing=>Incoming, the page will say Displaying Day Mode. Point your trunks to Schedule: Business Hours |
*Click the button Edit Night | *Click the button Edit Night | ||
*Set your trunks on this page (Displaying Night Mode) to go to Menu: In a Meeting | *Set your trunks on this page (Displaying Night Mode) to go to Menu: In a Meeting | ||
Line 15: | Line 15: | ||
#The user will keep the system forced in Day Mode, either by dialing *1 or follow the instructions from pressing a programmed Day/Night mode key to force Day Mode at the Is Operator extension. This will cause all calls to route to Schedule: Business Hours, and route accordingly. | #The user will keep the system forced in Day Mode, either by dialing *1 or follow the instructions from pressing a programmed Day/Night mode key to force Day Mode at the Is Operator extension. This will cause all calls to route to Schedule: Business Hours, and route accordingly. | ||
− | #When the user goes to a meeting, they will either dial *2 or follow the instructions from pressing a programmed Day/Night mode key to force Night mode at the Is Operator extension. This will cause all calls inbound to | + | #When the user goes to a meeting, they will either dial *2 or follow the instructions from pressing a programmed Day/Night mode key to force Night mode at the Is Operator extension. This will cause all calls inbound to route to Menu: In a Meeting. |
#When they return from their meeting and wish to resume normal functionality for inbound calls, they will need to follow the instructions listed above in step 1. | #When they return from their meeting and wish to resume normal functionality for inbound calls, they will need to follow the instructions listed above in step 1. |
Latest revision as of 14:30, 18 March 2015
This Application Design will outline a scenario when the user wants normal calling to follow a schedule, but needs to be able to trigger to a menu on demand to inform callers of something, such as no one being available because they are in a meeting.
- Create a Schedule: Business Hours; to match the users normal business hours, say 9am-5pm, Monday - Friday
- Set the In Hours, Out of Hours, and Lunch destinations as needed. eg.:
- In Hours; Ring Group
- Out of Hours; Menu: We are Closed
- Create your Information Menu, in our scenario it will be Menu: In a Meeting
- Enable Day & Night Mode, found under Call Routing=>Incoming
- Click Edit Hours and set the hours (we will not be following these hours, but they need to be set regardless)
- Go to Call Routing=>Incoming, the page will say Displaying Day Mode. Point your trunks to Schedule: Business Hours
- Click the button Edit Night
- Set your trunks on this page (Displaying Night Mode) to go to Menu: In a Meeting
Here is how this will function.
- The user will keep the system forced in Day Mode, either by dialing *1 or follow the instructions from pressing a programmed Day/Night mode key to force Day Mode at the Is Operator extension. This will cause all calls to route to Schedule: Business Hours, and route accordingly.
- When the user goes to a meeting, they will either dial *2 or follow the instructions from pressing a programmed Day/Night mode key to force Night mode at the Is Operator extension. This will cause all calls inbound to route to Menu: In a Meeting.
- When they return from their meeting and wish to resume normal functionality for inbound calls, they will need to follow the instructions listed above in step 1.