Holiday Prompts in V20

John_OMalley

Silver Partner
Advanced Certified
Joined
Aug 5, 2020
Messages
14
Reaction score
12
Hi All

Am I missing something when it comes to Holiday Prompts in V20?

In V18 I would select Date/Time and prompt and it would play that prompt during that date/time:

v18.jpg

However in V20 I do the same but the call goes to my out of hours IVR without playing this prompt...am I missing something?

v20.jpg
 
  • Like
Reactions: Plains_JosephW
However in V20 I do the same but the call goes to my out of hours IVR without playing this prompt...am I missing something?

You have to activate holiday.cs script from the store (in integrations area) for your trunk(s). Then your sound files are played for incoming calls on this trunk(s).
 
You have to activate holiday.cs script from the store (in integrations area) for your trunk(s). Then your sound files are played for incoming calls on this trunk(s).
is this script pre-written, e.g. I don't have to edit anything?
 
  • Like
Reactions: John_OMalley
Kudos to you, this actually worked, I tried it the other day but selected DID's not Trunk and it totally ruined the system, calls just ended, when removing the script the inbound rules stayed present so calls still ended. As that was a live system I restored it back there and then as I didn't have time to troubleshoot so was sceptical if this would work.

Thanking you :)
 
  • Like
Reactions: jed and PBX128

If you want to play the holiday prompt you need to go to the destination and flick the setting "Play announcement" under the holiday section.
@Alphabetic This is only if you want a single prompt, for different prompts on different days, you have to use :

You have to activate holiday.cs script from the store (in integrations area) for your trunk(s). Then your sound files are played for incoming calls on this trunk(s).
 
  • Like
Reactions: Evolute IT
Kudos to you, this actually worked, I tried it the other day but selected DID's not Trunk and it totally ruined the system, calls just ended, when removing the script the inbound rules stayed present so calls still ended. As that was a live system I restored it back there and then as I didn't have time to troubleshoot so was sceptical if this would work.

Thanking you :)

Yeah, since v20 Update 4 the holiday.cs script works very well.
 
  • Like
Reactions: John_OMalley
Yeah, since v20 Update 4 the holiday.cs script works very well.
Hmm, I hadn't realized it changed. I guess we need to re-add, or copy/paste from one with the update?
 
Why not just have 3CX play the prompt that's defined under the department holiday when it detects a call to the department during the defined holiday period??

Why must I manually go set "play announcement" on a destination during a holiday and then choose a prompt, when that prompt is already defined on the holiday definition.

If I have various holiday specific prompts, I have to manually change the prompts under the destination EACH TIME, when 3CX could just play the darn prompt that defined for the holiday so I don't have to manually swap prompts on each destination...
 
  • Like
Reactions: FYS
Why not just have 3CX play the prompt that's defined under the department holiday when it detects a call to the department during the defined holiday period??
That’s what the script does.
 
That’s what the script does.
Point is, why have to mess around with a script? Why not just have the PBX do natively do just that?
 
  • Like
Reactions: FYS
I feel like the script should be installed by default - shouldn't have to remember to add it to all systems, especially when it visually looks like it'll play a prompt. There is a place to upload it, there is a gap to show whether it's uploaded, and many people have come from V18. If it needs a script, fine, but don't make it manual

Also, there should be a way to stop it from playing the After Hours programming after the prompt has played - if you stay on the line, people hear both. Not sure how that makes sense in any context, ever
 
  • Like
Reactions: FYS
Yeah, I feel like the switch to v20 was rushed overall. The release phases made no sense. Putting out a product with missing features from the version before, then mandating migration due to licensing changes etc. For example, hot desking wasn't available until some time after the initial v20 release, I think 2 or 3 updates after.

I've been using 3CX since v11 in 2012. Never really had issues, but there are times when I find myself asking "why is it this way?".

Don't like that I was forced to move from a perpetual license either to annual. I've always paid maintenance so even if I decided to stick with a version, I could have on perpetual. Now I believe if it's not renewed, the product is deactivated? I am and have always been on prem.

I bought perpetual and at that time I bought a product I could have owned, now I'm forced out of product ownership.

Anyway, that's off topic. Hope the holiday prompt thing can be reviewed and some more though put into it.
 
  • Like
Reactions: FYS
Yeah, I feel like the switch to v20 was rushed overall. The release phases made no sense. Putting out a product with missing features from the version before, then mandating migration due to licensing changes etc. For example, hot desking wasn't available until some time after the initial v20 release, I think 2 or 3 updates after.

I've been using 3CX since v11 in 2012. Never really had issues, but there are times when I find myself asking "why is it this way?".

Don't like that I was forced to move from a perpetual license either to annual. I've always paid maintenance so even if I decided to stick with a version, I could have on perpetual. Now I believe if it's not renewed, the product is deactivated? I am and have always been on prem.

I bought perpetual and at that time I bought a product I could have owned, now I'm forced out of product ownership.

Anyway, that's off topic. Hope the holiday prompt thing can be reviewed and some more though put into it.
The holiday script essentially replaces the HOL IVR.

The HOL IVR was very static.

What the holiday script now does is that it allows you a bit more flexibility to have a DIFFERENT holiday prompt per queue, ring group, or digital receptionist, or you can have one prompt per trunk and then go and route your call to the original destination.

This was very basic when we only had the global office hours. Now we have the department office hours, each with their own schedules and holidays.

So a lot of the routing responsibility was moved over to the system extensions with the destinations menu.

The flow currently is: Trunk --> Script --> Original destination of the DID dialled.

During a holiday a lot of companies may still be providing services, so they can have some queues open, and during the holidays they use the "Accept anyway" option to keep receiving calls. But some close, so they use the play announcement option to play a prompt without the need for the script.

The script is there as an option if you dont want to configure the various forwarding and it will just end the call or get a voicemail from your queue.
 
I encourage you to take a look at our free tool 3CX Holiday Importer. It makes assigning holidays and the associated prompts simple.

1748442750526.png
And if you would like additional features, reach out to us. We are constantly adding features to our tools based on customer feedback. For example, we can now push holidays to each department.
 

Latest Posts

Forum statistics

Threads
111,962
Messages
589,993
Members
164,867
Latest member
swegner