# CX Survey (Pro)

##

{% embed url="<https://youtu.be/Q0Utw0MqrwI>" %}

## Survey Management

#### Audios[](https://i-survey-addon.readthedocs.io/es/latest/survey_create.html#audios) <a href="#audios" id="audios"></a>

Each completed survey involves 3 audio classes to be played:

* Initial greeting
* Closing speech
* Questions

Before creating our surveys, we must make sure to previously upload the audios involved in it using the OMniLeads audio module: Telephony - Audios - Custom audios.

Once the audios with which we are going to create our survey are available, then we move forward!

#### New Survey <a href="#nueva-encuesta" id="nueva-encuesta"></a>

The i-Survey Addon should be displayed within the Main Menu: <br>

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FzzP6OhwrPXpRgmkun4iz%2Fimage.png?alt=media&#x26;token=ff596761-0e21-437c-8602-2a0d1ac90f54" alt=""><figcaption></figcaption></figure>

\
From there we can generate a new survey:&#x20;

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FgWFyNUKA6w9DvsXVomZI%2Fimage.png?alt=media&#x26;token=41c974a7-167b-4965-a9ae-d9851356deab" alt=""><figcaption></figcaption></figure>

\
\
The first view of creating surveys involves the following fields:

* Name: The name that the new survey will have.
* Timeout: The tolerance time in which a DTMF response is expected as an interaction.
* Time retry: The time to wait to replay each question.
* Retry: The number of times you will tolerate a response not listed as an option.
* Start audio: The audio that plays as a welcome on each call transferred to the survey.
* End audio: The audio that is played when the survey ends.

Once the form is completed, the survey becomes available for further preparation, assignment and subsequent publication.

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2F3GHwtoaYKDxsocIgFUu9%2Fimage.png?alt=media&#x26;token=d68542ec-7d08-4aef-bc2a-40249cd69710" alt=""><figcaption></figcaption></figure>

## Question preparation

In the correct order, we must first generate all the questions that will be used in our survey, and then begin to associate the possible answers to each question and the actions to be triggered.\
&#x20;Now we are going to focus on the questions, so we click on the icon with a “?” inside the survey in question. \
\
To illustrate, we are considering a post-service satisfaction survey with two questions: As can be seen in the preparation of the question, you only have to indicate the audio to be played, a name for the question, a description, and then indicate if it is the first question in the survey on the one hand and if the question is weighted, that is, the response must be averaged in the reports.

* How would you rate the level of care received from 1 to 5?

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FLGzGnWDbVkNCKJK8Gl35%2Fimage.png?alt=media&#x26;token=ee08f2be-b032-43a7-84bd-3213f44fb520" alt=""><figcaption></figcaption></figure>

* The reason for your call was resolved

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FgrUFdHzkslrFtb3cRlnv%2Fimage.png?alt=media&#x26;token=3661f3f2-a082-49e5-8059-347238a1fb85" alt=""><figcaption></figcaption></figure>

#### Preparation of the answers to each question

Once all the questions have been generated, the expected responses for each question must be created along with the action that each one of them must trigger.\
Following the example presented, there are two questions:&#x20;

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FuqsE84M6HAg47nV8nkjt%2Fimage.png?alt=media&#x26;token=4892cd08-82d4-4a13-90fe-caba65fff2f8" alt=""><figcaption></figcaption></figure>

\
Next, we work on preparing responses for the initial question:&#x20;

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2Fa6Wdk1GsRVqSon46fM5t%2Fimage.png?alt=media&#x26;token=793db879-c66d-4486-bc9c-6b1a6b751240" alt=""><figcaption></figcaption></figure>

\
As can be seen, it is a matter of associating each DTMF expected as a response with an action:

* End
* Repeat
* Next Question

That is, the fact of receiving the expected DTMF as an interaction on the one hand qualifies the interaction and on the other triggers one of the aforementioned actions. As we can see, each of the answers leads to reproducing the next question, that is, question number two of the survey.

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FWvZKAZmkcxeauKAD5KA3%2Fimage.png?alt=media&#x26;token=6815329e-4ebb-4037-81b2-baa6a10403e9" alt=""><figcaption></figcaption></figure>

Note

This does not necessarily have to be the case; in a more complex example, many questions could be nested at different levels, forming a tree of the desired complexity. \
\
The second and last question in our example:

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FeHQdluxArZEfD5q2EGVy%2Fimage.png?alt=media&#x26;token=be128e7f-9191-413e-94a6-87bb94033c60" alt=""><figcaption></figcaption></figure>

&#x20;Each of the answers to this question has the action of ending the survey. Assignment to campaign and publication of the survey to production:&#x20;

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2FJJsRIEUbpkFdCtAyYMtt%2Fimage.png?alt=media&#x26;token=4c6b7375-bd2b-415f-86f8-854782a80c24" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2Fw3KZsYG7dY8IxbK9VCiS%2Fimage.png?alt=media&#x26;token=49ac8b5d-4ae1-4e52-ae5b-59ad12633099" alt=""><figcaption></figcaption></figure>

\
\
The survey must be associated with a campaign. Note Only one survey can be associated with a campaign. It is not feasible to associate a survey with more than one campaign. \
\
Finally, to leave the survey in production, it must be published. Transfer of the call to the survey \
\
For a post-service survey, the agent must transfer the call to the survey relevant to the campaign. To do this, he must press the transfer button, from which a modal window will be displayed with the option to transfer to the survey.

<figure><img src="https://1083123978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7qGfc9c0eCArZb6QcwvW%2Fuploads%2Ful0u8PqpQ6StjiBcya7o%2Fimage.png?alt=media&#x26;token=7df3345a-d9d2-4360-a2c4-6bb89b8b65f1" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.omnileads.net/english/cx-survey-pro.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
