Genesys Cloud - Main

 View Only
Discussion Thread View
  • 1.  Callback data clean up (GDPR)

    Posted 24 days ago
    Edited by Gregyor Visser 24 days ago

    Via an API triggered by an external application we're creating a callback request. In this callback we're sending basic, but confidential, information from the source application to Genesys Cloud. So that this information is shown in the created script. In the same script there'll be a questionnaire with the filled data that we need to keep and sent back to the source application.

    We've created a trigger which will react after a callback, this trigger will start a workflow which will clean up the participant data that the source application provided. This kinds of works, because under the Partipicant data there're 3 participants. 1 is the main Callback data participant, the second is Unknown (this one only appears when we provide the data from the source) and the third is the agent data.

    Callback info:
    {
      "scriptId": "ef98fb40-a9b0-4158-9617-2493b8160c10",
      "routingData": {
        "queueId": "421a146d-9bdd-4b49-a7cf-44122a33ccce",
        "skillIds": [
          "bacb28b7-626f-43df-a4a7-25cad3320c5d"
        ]
      },
      "callbackUserName": "ShrekTheFirst",
      "callerId": "+31334509379",
      "callbackNumbers": [
        "+31620870513"
      ],
      "data": {
        "person1name": "Shrek",
        "person1phone": "+31620870513",
        "person2name": "Fiona",
        "person2phone": "+31620870513"
      }
    }

    This appears in the script as follows:

    At first the Performance dashboard will show the full data:

    But after 120 seconds the trigger will clean up the "ShrekTheFirst" data, but not the Unknown part.

    Trigger conditions:

    Workflow conditions:
    nr15:
    Nr18 extra condition:

    Where and on what way can I define the 'Unknown' participant to clean the data?


    #ArchitectureandDesign
    #Outbound
    #Telephony

    ------------------------------
    Gregyor Visser
    Stater Nederland B.V.
    ------------------------------



  • 2.  RE: Callback data clean up (GDPR)

    Posted 10 days ago

    Remember that each attribute is written as participant data on the conversation in the segment that pertains to the participant.  Most of the time, this is the external call segment of the conversation, You can usually query the conversation and get the first participant and then find the attributes.  Let me know if this is not what you are asking for.  



    ------------------------------
    Robert Wakefield-Carl
    ttec Digital
    Sr. Director - Innovation Architects
    Robert.WC@ttecdigital.com
    https://www.ttecDigital.com
    https://RobertWC.Blogspot.com
    ------------------------------



  • 3.  RE: Callback data clean up (GDPR)

    Posted 8 days ago

    Hi, that we allready found out.

    But we expect that there will be only 2 participants, being the Agent and the Callback user. But we're finding out that a third participant is being created, the difficulty with this participant is that it's called Unknown. We can't figure out why and how this Unknown participant is created (or excists anyway). Because we can't find that out we can't clean it up in this proces.



    ------------------------------
    Gregyor Visser
    Stater Nederland B.V.
    ------------------------------



  • 4.  RE: Callback data clean up (GDPR)

    Posted 7 days ago

    You'll likely find the 3rd participant is a queue. Check the conversation timeline as you should see a participant on each row. You can use the GET /api/v2/conversations{conversationId} API to get the detail of one of your conversations and check the participants. Also bear in mind a transfer will create additional participants so you may want that in your logic.



    ------------------------------
    Richard Chandler
    Connect
    ------------------------------



  • 5.  RE: Callback data clean up (GDPR)

    Posted 2 days ago

    Do you have "Output" enabled on the variables in the script?

    In that case it would save the values as Participant Data, which might be causing this.

    Otherwise your trigged could check all participants that have data that need to be deleted and loop the Set Participant Data action for each.



    ------------------------------
    Jan Heinonen
    Contact Center Specialist
    GlobalConnect AB
    ------------------------------



Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources