Genesys Cloud - Main

Hello Jan, 

I think what you are trying to achieve cannot be done with Genesys Cloud in its current state. Reconciliation needs to happen at the campaigns end and I cannot think of a way to do this while the campaign is running without getting an error. 

Cheers, 

Hello Cameron,

when i got it right, is the reconciliation "just" an update one existing Salesforce Records. What would be helpful is to know what technical process of the package (closed source) is needed to start the update. We would like to use another starting trigger than the end of the campaign.

Alternatively I'm thinking of using the a mechanism on the Genesys side to update the campaign member when the call  or attempt is finished. I think we need the campaign member record ID (delivered via existing integration to Genesys Cloud Contact List) and use this to update this right after the call.

What do you think?

Kind regards

Jan

Hello Jan, 

I think what you are trying to achieve cannot be done with Genesys Cloud in its current state. Reconciliation needs to happen at the campaigns end and I cannot think of a way to do this while the campaign is running without getting an error. 

Cheers, 

Hello Jan, 

The problem I see is that the campaign on the salesforce side needs an end date. The reconciliation, as far as I am aware, needs to have the campaign end in order to trigger. 

As far as your second point,

"Alternatively I'm thinking of using the a mechanism on the Genesys side to update the campaign member when the call  or attempt is finished. I think we need the campaign member record ID (delivered via existing integration to Genesys Cloud Contact List) and use this to update this right after the call."

This might work, though I haven't seen it done to date, but would require development and testing from your end. 

Cheers, 

Hello Cameron,

when i got it right, is the reconciliation "just" an update one existing Salesforce Records. What would be helpful is to know what technical process of the package (closed source) is needed to start the update. We would like to use another starting trigger than the end of the campaign.

Alternatively I'm thinking of using the a mechanism on the Genesys side to update the campaign member when the call  or attempt is finished. I think we need the campaign member record ID (delivered via existing integration to Genesys Cloud Contact List) and use this to update this right after the call.

What do you think?

Kind regards

Jan

Hello Jan, 

I think what you are trying to achieve cannot be done with Genesys Cloud in its current state. Reconciliation needs to happen at the campaigns end and I cannot think of a way to do this while the campaign is running without getting an error. 

Cheers, 

Dear Cameron,

the needed end date is some organizational issue, campaign in SF can have a date in the far beyond future (many years), so this could cover a "permanent" campaign.Is there any chance to get some insights of the package which API are headed in which way at the Genesys side to get the needed information?

Maybe somebody else in the Community has some experience about option 2 or another approach.

Kind regards
Jan

Hello Jan, 

The problem I see is that the campaign on the salesforce side needs an end date. The reconciliation, as far as I am aware, needs to have the campaign end in order to trigger. 

As far as your second point,

"Alternatively I'm thinking of using the a mechanism on the Genesys side to update the campaign member when the call  or attempt is finished. I think we need the campaign member record ID (delivered via existing integration to Genesys Cloud Contact List) and use this to update this right after the call."

This might work, though I haven't seen it done to date, but would require development and testing from your end. 

Cheers, 

Hello Cameron,

when i got it right, is the reconciliation "just" an update one existing Salesforce Records. What would be helpful is to know what technical process of the package (closed source) is needed to start the update. We would like to use another starting trigger than the end of the campaign.

Alternatively I'm thinking of using the a mechanism on the Genesys side to update the campaign member when the call  or attempt is finished. I think we need the campaign member record ID (delivered via existing integration to Genesys Cloud Contact List) and use this to update this right after the call.

What do you think?

Kind regards

Jan

Hello Jan, 

I think what you are trying to achieve cannot be done with Genesys Cloud in its current state. Reconciliation needs to happen at the campaigns end and I cannot think of a way to do this while the campaign is running without getting an error. 

Cheers,