01-30-2019 08:30 PM - edited 03-14-2019 06:45 PM
I am having an issue with a script that has a callback option, it has been requested that when the agent is ready the agent should be able to see the customers number and what CSQ they selected. Issue is, the first script calls the trigger to the CCB script and then it returns to the first script to complete the process. i cannot capture the information requested. what am i doing wrong? I have tried the usual steps (Call Info and Set Enterprise Info) any help would be great!!
Info flow: script 1---->CCB script-->script 1
Solved! Go to Solution.
01-31-2019 11:10 AM - edited 01-31-2019 11:14 AM
The easiest way to pass information from the calling script (the one with the Place Call step), to the answering script (the one queuing the callback call), is to use Set/Get Enterprise Call Info steps.
In fact, the way in which the Set/Get Enterprise Call Info steps work, is by attaching data to a Contact. The Contact in the calling script, the one you use in the Place Call step, is actually the same Contact in the answering step, the default --Triggering Contact--. So, actions performed on one, are actually performed on both.
Example
Calling Script
Place Call (callback_contact) Success Set Enterprise Call Info (callback_contact) my_variable = "my value"
Answering Script
Accept (--Triggering Contact--) Delay 3 sec my_variable = Get Enterprise Call Info (--Triggering Contact--) If (my_variable == "my value") True /* This should be true */
Note the delay in the answering step. This is not accidental. You are essentially firing two scripts to run in parallel here, and so we have a timing issue between when the calling script has set the variables, and when the answering script is trying to read them.
Tip for the pros: You can actually use this feature to understand when the Agent answers the call from the answering script, and then in the calling script poll the Enterprise data for a flag to be set to true. E.g., is_answered. This avoids the repeating message thing of "This is a callback call. Press any key to blah blah blah"
It's confusing, no doubt, so just post back if this still doesn't make sense, and I'll keep helping.
01-31-2019 11:10 AM - edited 01-31-2019 11:14 AM
The easiest way to pass information from the calling script (the one with the Place Call step), to the answering script (the one queuing the callback call), is to use Set/Get Enterprise Call Info steps.
In fact, the way in which the Set/Get Enterprise Call Info steps work, is by attaching data to a Contact. The Contact in the calling script, the one you use in the Place Call step, is actually the same Contact in the answering step, the default --Triggering Contact--. So, actions performed on one, are actually performed on both.
Example
Calling Script
Place Call (callback_contact) Success Set Enterprise Call Info (callback_contact) my_variable = "my value"
Answering Script
Accept (--Triggering Contact--) Delay 3 sec my_variable = Get Enterprise Call Info (--Triggering Contact--) If (my_variable == "my value") True /* This should be true */
Note the delay in the answering step. This is not accidental. You are essentially firing two scripts to run in parallel here, and so we have a timing issue between when the calling script has set the variables, and when the answering script is trying to read them.
Tip for the pros: You can actually use this feature to understand when the Agent answers the call from the answering script, and then in the calling script poll the Enterprise data for a flag to be set to true. E.g., is_answered. This avoids the repeating message thing of "This is a callback call. Press any key to blah blah blah"
It's confusing, no doubt, so just post back if this still doesn't make sense, and I'll keep helping.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide