Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Also are you getting NULL result or a -1 results.
A1: I've not been able to establish this clearly, but NULL seems to be the likely answer based on the results.  If I play the variable in an audio prompt, it returns silence.  I tried setting it in participant data, and when I did so, it resulted in no entry within participant data at all.  I subsequently added a test value with a static string of "Test" in the same set participant data action, and it worked as expected..



Q2: What type of flow is this being conducted in?
A2:  I am doing this in an in queue call flow.  The design does implement a common module, but I have tested the Estimated Wait Time both before and after the common module, and it behaves the same.

Q3: What happens if I set Task.EWT to Call.EstimatedWaitTime?
A3: This didn't change anything however...


One of my test calls mysteriously worked while I was experimenting with this and produced the following:


I retraced my steps on the test call and I figured out what was different with this one vs the others:  I was on queue at the beginning of the call.

In most of my test calls, I don't want it to answer right away, so I leave myself off queue until I am ready for the call to deliver to me.  Apparently being on queue at the outset allows the variable to be set.

I've tested it with both Call.EstimatedWaitTime and Task.EWT and it worked both ways as long as I was on queue.

So, in an actual production situation, this should be a non-issue.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt

Also are you getting NULL result or a -1 results.
A1: I've not been able to establish this clearly, but NULL seems to be the likely answer based on the results.  If I play the variable in an audio prompt, it returns silence.  I tried setting it in participant data, and when I did so, it resulted in no entry within participant data at all.  I subsequently added a test value with a static string of "Test" in the same set participant data action, and it worked as expected..



Q2: What type of flow is this being conducted in?
A2:  I am doing this in an in queue call flow.  The design does implement a common module, but I have tested the Estimated Wait Time both before and after the common module, and it behaves the same.

Q3: What happens if I set Task.EWT to Call.EstimatedWaitTime?
A3: This didn't change anything however...


One of my test calls mysteriously worked while I was experimenting with this and produced the following:


I retraced my steps on the test call and I figured out what was different with this one vs the others:  I was on queue at the beginning of the call.

In most of my test calls, I don't want it to answer right away, so I leave myself off queue until I am ready for the call to deliver to me.  Apparently being on queue at the outset allows the variable to be set.

I've tested it with both Call.EstimatedWaitTime and Task.EWT and it worked both ways as long as I was on queue.

So, in an actual production situation, this should be a non-issue.

Thanks,

Matt

Hello,

I've encountered something a bit strange in one of my test flows today.  Specifically, I experimenting with an in queue call flow and noticed that my Play Estimated Wait Time action is not actually doing anything.

I've done some testing with this and found that the variable it uses for the prompt: Call.EstimatedWaitTime has no value in it, or at least when I attempt to play the value of the variable in a prompt, it interprets it as silence.  I can't actually use debug mode with it as it is within an in queue flow.

I am doing this with a test queue that does not normally receive production calls in my testing, and at first I thought it might be that there isn't data on recent calls because it doesn't normally receive production calls.  I conducted a few test calls to myself and answered them, and it doesn't seem to have an impact unless there's some threshold value I didn't conduct enough calls to reach.

I was curious if anyone can suggest potential factors which could drive this behavior.

Thanks,

Matt