Author Topic: Courtesy Callback via GMS  (Read 889 times)

Offline genesys_techie

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Courtesy Callback via GMS
« on: March 09, 2020, 09:47:16 PM »
I am trying to see if anyone can give me directions on courtesy callback. What I need to do:
Based on EWT and some other factors, make a decision, to offer courtesy callback (this is easy and doable). The next part is to insert the callback as a virtual call in place of the actual caller in the same position in the queue and offer callback when the position comes to the front of the queue (this is the part I am struggling with).

Does anyone know how this can be done?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7131
  • Karma: 56330
Re: Courtesy Callback via GMS
« Reply #1 on: March 09, 2020, 11:51:12 PM »
You can use Genesys Call back solution with GSM, what you intend to do without creating a voice interaction is not doable.

Offline genesys_techie

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Courtesy Callback via GMS
« Reply #2 on: March 10, 2020, 01:18:59 AM »
You can use Genesys Call back solution with GSM, what you intend to do without creating a voice interaction is not doable.

I would be creating the callback, but I need to make sure that the created callback is at the same position in the queue. So for example, when the customer calls in they are at Queue Position 15 in VQ. We offer them to hold the position in the queue and they accept, which is when I would create a new callback.

Now, what kind of callback this should be? Immediate or scheduled? In either case, how to I ensure that the position of the customer in the VQ is 15 when the callback is created and then once the customer moves to the beginning of the queue generate the outbound call and connect with the available/reserved agent.

Offline terry

  • Sr. Member
  • ****
  • Posts: 292
  • Karma: 33
Re: Courtesy Callback via GMS
« Reply #3 on: March 10, 2020, 02:51:54 AM »
Up to my knowledge if it is immediate callback the position will be preserved automatically.
If it is scheduled then "preserving position" is sort of not applicable.

Offline genesys_techie

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Courtesy Callback via GMS
« Reply #4 on: March 10, 2020, 03:19:16 AM »
Up to my knowledge if it is immediate callback the position will be preserved automatically.
If it is scheduled then "preserving position" is sort of not applicable.

Okay, if the position is maintained, then all I have to do is generate a web call to create an immediate callback.. correct?

Offline gen_rtfm

  • Newbie
  • *
  • Posts: 21
  • Karma: 1
Re: Courtesy Callback via GMS
« Reply #5 on: March 10, 2020, 04:10:50 AM »
I agree, immediate should be the way to go. Make sure to inherit the inbound calls current priority, priority increment and skill expression and the callback interaction should have the "same place" in urs queue.

Skickat från min F8331 via Tapatalk


Offline genesys_techie

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Courtesy Callback via GMS
« Reply #6 on: March 13, 2020, 08:20:36 AM »
So I finally tried to create Callback via API POST request, my request looks like this:

https://host:port/genesys/1/service/callback_service_name?_customer_number=11235555555&_wait_for_agent=false&_call_direction='USERTERMINATED'&_wait_for_user_confirm=false&_urs_virtual_queue=VQ_Alias_Name&_target=Skill_Name&_offer_callback=false&_media_type=voice&_cb_dim_channel=IVR

But ORS breaks and no callback is generated:

Code: [Select]
14:01:30.727 [T:5920] {ScxmlMetric:3} METRIC <transition sid='GFSKJQLNOL6AHATQG273H0A9VO000004' name='Activity.ActivityMethodsTemplate.RequestURSDelayStrategy.ReportInitialUserEvent' event='report_initial_userevent' target='Activity.ActivityMethodsTemplate.RequestURSDelayStrategy.AttachRepUserData1' line='5675' />
14:01:30.727 Alr 23019 [T:5920] Orchestration session: GFSKJQLNOL6AHATQG273H0A9VO000004 has encountered an execution error: uncaught exception: Invalid format for UTC timestamp :  - in <script> at line: 5676.
14:01:30.727 [T:5920] {ScxmlMetric:3} METRIC <exec_error sid='GFSKJQLNOL6AHATQG273H0A9VO000004' result='uncaught exception: Invalid format for UTC timestamp :  - in <script> at line: 5676' />

I tried passing the _desired_time in UTC as well, but that doesn't generate the callback either, and it breaks here:
Code: [Select]
15:23:11.040 [T:6672] {ScxmlMetric:1} METRIC <extension sid='GFSKJQLNOL6AHATQG273H0A9VO000008' name='reschedule-callback' namespace='http://www.genesyslab.com/modules/dfm/gsgCallback/v1' />
15:23:11.040 [T:6672] {ScxmlMetricEvalExpr:3} METRIC <eval_expr sid='GFSKJQLNOL6AHATQG273H0A9VO000008' expression='_genesys.session.tenantid' type='number' result='101' />
15:23:11.040 [T:6672] {ORSInternal:3} +OrsEvent[0x0000000008183980]:name=error.gsgCallback.reschedule-callback
15:23:11.040 [T:6672] {ORSInternal:3} +IORSSessionTask[0x0000000003fcb750]
15:23:11.040 [T:6672] {DFM:1} DFMActionData::Execute() - Error: Failed to create fetch request descriptor; SessionID=[GFSKJQLNOL6AHATQG273H0A9VO000008], Error=[callbackexecutionname: Incorrect attribute type]
15:23:11.040 [T:6672] {ORSInternal:3} +OrsEvent[0x0000000008180180]:name=error.gsgCallback.reschedule-callback


Any ideas?

Offline gen_rtfm

  • Newbie
  • *
  • Posts: 21
  • Karma: 1
Re: Courtesy Callback via GMS
« Reply #7 on: March 13, 2020, 02:37:12 PM »
Have you refreshed the dfm files for ors after configuring gms?

The dfms are downloaded from gms admin UI, you need to enable dfm download in gms options, I think the section is named 'features'.

After download you need to configure ors so it knows the location of said dfm files and restart ors.

Br

Skickat från min F8331 via Tapatalk


Offline gen_rtfm

  • Newbie
  • *
  • Posts: 21
  • Karma: 1
Re: Courtesy Callback via GMS
« Reply #8 on: March 13, 2020, 03:43:04 PM »
Another thing, I checked your url and I wonder if that's correct. Ors seems to complain about callback_execution_name.

In your url you have [...]/service/callback_service_name [...]

When I check the url in a working environment I see [...]/service/callback/nameofcallbackservice/[...]

How have you named your gms callback service, is it called 'callback_service_name' or is that a placeholder?

Regardless you seem to be missing /callback/ between 'service' and the name of the service that should handle the request.

Br

Skickat från min F8331 via Tapatalk


Offline genesys_techie

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Courtesy Callback via GMS
« Reply #9 on: March 19, 2020, 03:58:03 AM »
Thanks, putting the /callback/ helped.

Another thing, I checked your url and I wonder if that's correct. Ors seems to complain about callback_execution_name.

In your url you have [...]/service/callback_service_name [...]

When I check the url in a working environment I see [...]/service/callback/nameofcallbackservice/[...]

How have you named your gms callback service, is it called 'callback_service_name' or is that a placeholder?

Regardless you seem to be missing /callback/ between 'service' and the name of the service that should handle the request.

Br

Skickat från min F8331 via Tapatalk

Offline gen_rtfm

  • Newbie
  • *
  • Posts: 21
  • Karma: 1
Re: Courtesy Callback via GMS
« Reply #10 on: March 19, 2020, 04:37:54 PM »
Glad to hear it :)

Skickat från min F8331 via Tapatalk