Skip to content

Get Last Survey For Client

Element Name:Get Last Survey For Client

Category: Customer Satisfaction

Description: This is an advanced functionality that retrieves all surveys from a specified date until the present for the client associated with the interaction. The information is returned in JSON format.

Functionality: Returns survey-related information in JSON format.

Action Configuration Fields

[Survey period]: Select the period for which survey information is required from the dropdown list. The options available are:

  • Day

  • Week

  • Month

  • Year

Example: Month

[Maximum count of surveys in the period]: In relation to the survey period configuration, indicate the maximum count of the established period. In the example below, selecting 1 corresponds to retrieving information for a maximum of 1 month. Only integer values are accepted.

Example: 1

[Entity to store a boolean value indicating whether there are results or not]: Define an entity (previously created as a boolean) that will contain a value of true if there is no data or false if there is data.

[Entity to contain the JSON response indicating whether there is data or not]: Define an entity (previously created as a string) that will contain, if there is information, the obtained result in JSON format for the previously configured period

Output example:

    [
        {
            subLevel": "CustomerSatisfactionSurvey",
            "subData": 
            {
                "evaluationTitle": "Please help us improve your experience. How would you rate the attention received?",
                "conversation": "82620af4-9755-4c2f-9fd2-62e72110d1de",
                "evaluationEntity": "SURVEY",
                "evaluationValue": "regular",
                "intent": ""
            }
        }
    ]

[Error handler]: Drop-down menu where the intention that will be activated in case of an error in Get Last Survey For Client is identified. When an error overflow occurs, the "Get_Last_Survey_For_Client_Error" entity will be loaded with the error details if available.

Implementation example

[Survey period]: Day

[Maximum survey count in period]: 1

[Results exist]: prueba_booleano --> false

[JSON output]: prueba_json -->

   [
        {
            subLevel": "CustomerSatisfactionSurvey",
            "subData": 
            {
                "evaluationTitle": "Please help us improve your experience. How would you rate the attention received?",
                "conversation": "82620af4-9755-4c2f-9fd2-62e72110d1de",
                "evaluationEntity": "SURVEY",
                "evaluationValue": "regular",
                "intent": ""
            }
        }
    ]

IMPORTANT:❗ It should be noted that for there to be survey information, a survey must already be active within the flow.