Flexible Time/Date Based Dial Plans

[PWillemen]

Hi everyone,

I'm quite new to the forums and a brief search didn't result in a solution I can use, so maybe someone over here as a good idea or can help me post a Feature Request.

We plan to migrate our current hosted PBX to hosted 3CX but there's one thing we can't quite find a good solution for.
Our current system offers the following:

We can setup different Dial Plans/Number Plans which basically tell DID A through X to go to a different Extension each.
For example:
- Dial Plan A for when we are closed, all DIDs get our closed+office hours Prompt.
- Dial Plan B for when the office (8:30-17:00) is still closed but Support is already reachable from (7:30-8:30)
- Dial Plan C for all reachable from 8:30-17:00) etc.
- Dial Plan D holidays, this leads all or some DID to a prompt while having our emergency line active for example.

We then can set an automated weekly schedule that says from Monday 0:00 to Sunday 24:00 we are closed (Dial Plan A), from Mo through Friday 7:30 to 8:30 Plan B runs, from 8:30-17 Plan C runs and on pre-planned holidays Plan D can overrule this.

We also have an option to have let's say a Plan E that's says (instead of holiday) 'We are currently and unexpectedly unavailable' which we can manually set to override until it's removed again (upon which the automated program continues).

This is an example from the scheduling option from our current PBX:


This is basically what I need to achieve in 3CX, either by scripting or by some other means (or hopefully such a feature ever makes it to a newer version).

Does anyone have an idea how to accomplish this?

Thanks in advance, any thoughts are much appreciated.

 

[Evolute IT]

Hi everyone,

I'm quite new to the forums and a brief search didn't result in a solution I can use, so maybe someone over here as a good idea or can help me post a Feature Request.

We plan to migrate our current hosted PBX to hosted 3CX but there's one thing we can't quite find a good solution for.
Our current system offers the following:

We can setup different Dial Plans/Number Plans which basically tell DID A through X to go to a different Extension each.
For example:
- Dial Plan A for when we are closed, all DIDs get our closed+office hours Prompt.
- Dial Plan B for when the office (8:30-17:00) is still closed but Support is already reachable from (7:30-8:30)
- Dial Plan C for all reachable from 8:30-17:00) etc.
- Dial Plan D holidays, this leads all or some DID to a prompt while having our emergency line active for example.

We then can set an automated weekly schedule that says from Monday 0:00 to Sunday 24:00 we are closed (Dial Plan A), from Mo through Friday 7:30 to 8:30 Plan B runs, from 8:30-17 Plan C runs and on pre-planned holidays Plan D can overrule this.

We also have an option to have let's say a Plan E that's says (instead of holiday) 'We are currently and unexpectedly unavailable' which we can manually set to override until it's removed again (upon which the automated program continues).

This is an example from the scheduling option from our current PBX:
View attachment 17913

This is basically what I need to achieve in 3CX, either by scripting or by some other means (or hopefully such a feature ever makes it to a newer version).

Does anyone have an idea how to accomplish this?

Thanks in advance, any thoughts are much appreciated.

You could use the CFD to program that and give them ability to force it if needed. A few parts could probably be done with Time-aware inbound rules.

 

[PWillemen]

You could use the CFD to program that and give them ability to force it if needed. A few parts could probably be done with Time-aware inbound rules.

Thank you for the reply.
I have indeed starting looking at the CFD. Haven't seen all options in this but will research that further. The thing with scripting is that it makes it less serviceable for others when minor changed need to be made to it.

 

[AWS2P]

- Dial Plan A for when we are closed, all DIDs get our closed+office hours Prompt.
- Dial Plan B for when the office (8:30-17:00) is still closed but Support is already reachable from (7:30-8:30)
- Dial Plan C for all reachable from 8:30-17:00) etc.
- Dial Plan D holidays, this leads all or some DID to a prompt while having our emergency line active for

set office hours 8:30 to 17 in global pbx hours from monday to friday.
Create an inbound rule for support DID with specific hours.
Create inbound rules where you want to forward others calls during OH set an IVR for OOH
In holidays IVR set DNA to another IVR for emergency use

Of course some of those steps are not usable completely automated , you will need to put hands in console and make few changes in settings.

 

[PWillemen]

set office hours 8:30 to 17 in global pbx hours from monday to friday.
Create an inbound rule for support DID with specific hours.
Create inbound rules where you want to forward others calls during OH set an IVR for OOH
In holidays IVR set DNA to another IVR for emergency use

Of course some of those steps are not usable completely automated , you will need to put hands in console and make few changes in settings.

Thanks for the reply.
I'm considering this or looking for some automation through CFD.

I kind of need it to be serviceable with minimal alterations from me or the other 3CX guys, so when our support line at certain times must redirect to the engineer on call this must be changeable by our planner etc.

 

[AWS2P]

CFD is of course the way if you want automated things, but for sure you need to change CFD content if something change.
Of course CFD is not so easy as everyone in company can play with

 

[SupV]

All of these are possibly without CFD to possibly make it a bit easier.

A: Basic Out of Office mode
B+C: DDI to a user. Under forwarding rules use the Exception option to add specific routes to specific times (7.30 - 8.30)(8.30 - 17.00)
D: Configure Holiday (either with or without the check on the different DDI's for Play holiday prompt when it's a global holiday)

 

[PWillemen]

Thank you for the reply, I will experiment with the Exceptions function before turning to CFD as that is less serviceable.