Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.
  • 1.  Outbound Columns as Participant Data

    Posted 04-21-2023 00:18
    No replies, thread closed.

    Is there an easy way to get outbound columns and values as participant data for outbound Campaigns.

    The way I know is a Data Action calling patch attributes API to write all the columns as participant data and have that triggered on either the agent script or as a call rule. 
    Which is a pain as each Campaign needs its own Data Action, and if you have a lot of columns it just takes awhile to setup. Feel like there should be a simple toggle for it.


    #Outbound

    ------------------------------
    Anton Vroon
    ------------------------------


  • 2.  RE: Outbound Columns as Participant Data

    Posted 04-21-2023 15:21
    No replies, thread closed.

    Anton,
    I'm sure you've thought of this, but I'd just write the Contact ID to the PD (which would be the same DA for all campaigns) and then use it as a reference back to the original data from the contact list. (Or, if your data has an account number, use that and reference back to the CRM.)
    This was a simple checkbox in PureConnect, but as we all know, not everything that was easy on the old system is similarly easy on the new! 😑



    ------------------------------
    Paul Simpson
    Eventus Solutions Group
    ------------------------------



  • 3.  RE: Outbound Columns as Participant Data

    Posted 04-23-2023 20:27
    No replies, thread closed.

    Thanks for the suggestion @Paul Simpson
    We currently, for better or worse, clear the contact list each day, starting with a fresh list each morning. So can't refer back to the contact data the next day, hence why adding PD would solve that.

    Guess I'll log another idea request
    https://genesyscloud.ideas.aha.io/ideas/CEOCD-I-676




    ------------------------------
    Anton Vroon
    ------------------------------



  • 4.  RE: Outbound Columns as Participant Data

    Posted 04-24-2023 09:56
    No replies, thread closed.

    Anton,
    I see your problem. For the time being, you will need to go with option 2 - write a record ID from the original source system (your CRM?) such as an account number. Then you can cross-reference the data from that.
    Otherwise, I'm afraid it's gonna be doing it the long way...



    ------------------------------
    Paul Simpson
    Eventus Solutions Group
    ------------------------------



  • 5.  RE: Outbound Columns as Participant Data

    Posted 04-29-2023 01:32
    No replies, thread closed.

    Hi Anton,

    Just want to make sure I understand your question. 

    1. You have Outbound flow used by Outbound campaign
    2. In your outbound flow you want to read the columns from the contact list associated with your Outbound flow?



    ------------------------------
    Maxim Tsvetov
    Principal PS Consultant
    Genesys
    ------------------------------



  • 6.  RE: Outbound Columns as Participant Data

    Posted 04-30-2023 16:12
    No replies, thread closed.

    Hi Maxim,

    No, that would be easy to do.

    When viewing the interaction, conversation detail API or in the UI where the recording is, I want to see the column and values in participant data regardless of what has or hasn't happened with the call, ie, even if a preview call and hasn't gone to an agent yet.

    As mentioned we clear the contact list each day, as contact lists do a have a maximum limit and requirement wise we have no need to carry over to the next day. 
    However this means if an agent reports an issue with a contact the next day, we can't see anything that happened since the contact list itself is gone. 

    I was hoping for a toggle that would automatically just do this. Using DataAction to patch the attributes in pre call rules don't work for preview campaigns and pushes us closer to rate limits, as well as requiring a DataAction for each contact list which just becomes difficult to manage.



    ------------------------------
    Anton Vroon
    ------------------------------



  • 7.  RE: Outbound Columns as Participant Data

    Posted 05-01-2023 18:27
    No replies, thread closed.

    Maybe you need to use whatever tool you use to re-load the list, to download the list prior to reload, so at least you have something to refer to.  I write everything in a post call rule to our CRM using a data action.  How many concurrent calls do you allow?  Maybe that would limit your data actions.



    ------------------------------
    Ryan Cheesman
    Senior Manager, IT Integration Services
    Tandem Diabetes Care Inc. | positively different
    ------------------------------



  • 8.  RE: Outbound Columns as Participant Data

    Posted 05-01-2023 18:58
    No replies, thread closed.

    I'm not certain, but I believe the contact-ID is written to the interaction details automatically. When you import your contact list, make sure you define a column to be the unique identifier, and you should see that is used as the contact ID. (Use a column that contains some kind of unique identifier in the source system, such as customer ID.)

    If / when you need to analyze, you can see the contact ID and use that to look up the information in the source system to see who the victim (I mean customer!) was.

    HTH



    ------------------------------
    Paul Simpson
    Eventus Solutions Group
    ------------------------------



  • 9.  RE: Outbound Columns as Participant Data

    Posted 05-15-2023 09:10
    No replies, thread closed.
    Hello Anton,
     
    If I have understood your problem correctly, then the solution may lie in the script itself.
    The outbound columns can easily be queried in the script, as long that "outbound" is activated under the script properties. In the script, you can read out these outbound variables via page load actions and assign them to custom variables. If you define this variable as an output variable, the value is automatically written to the participant data.
     
    I hope this helps.
    Best regards
    Christoph


    ------------------------------
    Christoph Domaschke
    CRONBANK AG
    ------------------------------