Custom reporting field as a scenario variable

Product Q&A
1

Hello everyone,

I’m facing the following task. I’d like to run an outbound list—where the “AZ” field serves as the unique parameter—in a skill-based scenario.

The “AZ” field is written to a custom reporting field during import. I would like to read this field in the scenario and write it to a variable so I can use it to retrieve additional information via an API. However, this variable is not populated in all cases. The question is, how can I write the “AZ” field from the outbound campaign directly into a variable in the scenario?

Thank you very much for your advice and best regards from Germany.

2

Mark, do you mean you import the AZ as a custom list field and it is not available as the outbound scenario variable $(workitem.fullInfo.AZ) at all times?

thanks,

Sergey

3

Hi Sergey,

Thanks so much for the tip. That was the key clue.

Best regards,

Mark

4

Hi Sergey, I have another question about this. I’ve now set up a final scenario based on an outbound campaign. In this scenario, I’ve configured a skill-based overflow. However, it seems that as soon as a call goes into the overflow, the dialer always receives the “No Agent” status, even though a call has been established. Can you help me?

Best regards,

Mark