Skip to main content

Genesys call outcomes on customers

How Kolleno writes the outcome of the last Genesys call onto each customer.

Each day, the Genesys sync reads the outcome of the last call to each contact. It writes the outcome onto the customer in Kolleno, so that your team, your filters and your workflows can use it.

Where the outcome goes

Kolleno writes into two customer custom fields. The Kolleno team selects them when it sets up your connection:

  • Action code: a text field that holds the outcome of the last call.

  • Last call attempt: a date field, or a date and time field, that holds when the last call was made.

To see the two fields, open the customer and click the Insights tab. The fields are under Custom fields.

How Kolleno finds the action code

  1. Kolleno reads the wrap-up code that the agent chose in Genesys, for example "Promise to pay".

  2. If no agent chose a wrap-up code, for example because nobody answered, Kolleno reads the call result from Genesys, for example "No Answer".

  3. Kolleno changes the name into your action code with your mapping, for example "Promise to pay" becomes "PTP". The Kolleno team sets up the mapping with you.

If a name is not in your mapping, Kolleno writes the Genesys name as it is.

Use the outcome

  • Filters: filter your customers on the action code or the last call attempt.

  • Workflows: use the two fields in the filters of a workflow trigger. A workflow sees a new outcome on its next run.

Common questions

Genesys called a customer more than once. Which outcome do I see? The outcome of the latest call, also when the customer is in more than one contact list.

I see a Genesys name, not my action code. The name is not in your mapping, for example because a new wrap-up code was added in Genesys. Contact Kolleno support to add it. To find these customers, filter on the action code field.

Why did the outcome of a customer not change? Kolleno writes the outcomes once a day, so a call made today shows after the next sync. If the customer is still not updated, check the unmatched rows in the Genesys sync history.

Did this answer your question?