Evo Survey is Live — Ditch the Third-Party Tools

Thank you, Ana. I'm going to pick up the screen here and I'm going to dive into Survey. If you remember, we've presented Survey a while ago, I don't know, a couple of weeks back.

And I just wanted to reiterate and announce everybody in case you haven't heard that we've launched a Survey tool. which is a productivity tool throughout Access. So you now can access it from here, from productivity tools. As you see, it's together with Kanban and workflow automation.

And it has two main roles, and I'm going to dive into them immediately. But first, I'm going to say what this EVO survey is a native survey and feedback tool built into EVO platform. It provides A structured end-to-end workflow for creating surveys, applying conditional logic, distributing them to respondents, collecting the respondents. responses and reviewing results, everything runs within the single access zone environment.

The problem it solves is the fact that, well, surveys are being used as a mechanism for collecting feedback from colleagues and currently this activity still relies on tools outside of access platform, separate licenses, disconnected data, manual re-importing and processing, and third-party interfaces. Evo survey removes that dependency, response data stays within Access from the moment the survey is submitted. Creators manage the full life cycle, the design, the logic, the distribution, and the analysis without leaving evil.

And now we even have created the survey as a connector, and then I will show you that after I'm going through the basic flow. Yeah. So we have two roles, the survey creator and the respondent.

The main thing comes from the survey creator. And I'm having here a couple of surveys just to not go through the whole cycle of creating. And we can, for example, I can, no, I'm going to show you this one because this one I can show the questions as well.

This is like a new survey created. I can add various types of questions here and within those questions I can add logic.

Kristy Gilham 35:15

Deane.

Andreea Aparaschivei 35:23

Logic granting, meaning that on some of the options from the question asked, the response can go to a different question or skip or, you know, you decide where the flow should go based on the option selected by the user. Right, after I've created the survey, applied the logic flow, if that's what the user wants, we can, we have a wizard that goes next to a logic flow where you have an overview of the questions and how they are linked together. Right, like this, we can play with them. they will be in the future be able to be editable from here as well, meaning all the logic flows.

Currently they aren't, but we're working on that. And then we can go to settings where we are defining the deadlines, the creators, And basically we're validating if the Google survey is ready to go live. Right, I cannot go live without setting up a date.

I'm selecting here a date and I'm going to put here my username is going to be available here. If not, I can put. on behalf of an entity, on behalf of whom I'm submitting. I can allow editing response after submitting by the respondents.

Right now I'm going to deselect this and I can publish survey. And then the next step, I'm selecting the organisation and members to whom I want this survey to be sent. I'm going to send it to myself right now because I can show you that it came to me as a respondent.

And I also have the option to send a notification message. If not, it's going to be something Quite simple and default from the feed, and I'm sending it through feed. Okay, and now I'm finishing, and I can switch role going to respondent.

I should have a feed notification, which... Just came. This is the one that I received.

Okay, one second. And it's going to open the survey. In another in a second tab, see, I have here EVO survey where I am as a creator logged in and I have the other tab which is for my EVO survey, but from the respondent perspective.

Why I have this? Because we did not want to lose the work midway. And here I can, whatever, just go through it, do something I can save and pause as a respondent.

The idea is that we can have two separate. views and we can manage them separately without interfering with one another. I'm not going to finish the survey because I want to remain on the creator side and show you that once this, once the survey is. The. being responded to, I'm capturing, as a creator, I'm capturing the responses.

I have a summary of that. Mm. Sometimes it's loading a bit.

So. I'm going to switch again the role. K.

I'm going to see here for the surveys that have become active. I'm going to see them how many responses I've got when there is the deadline where I published it and how many questions there are. And I can see here, I can preview it.

I can only soft edit it. For example, I can change the deadline. I can change the things that I've said here.

And when I'm changing the settings from an already active survey, the only additional thing I can do apart from this is to add new users to whom I'm sending. So the users to whom I've already sent that survey will not be affected by the changes that I've done. Only new users can be added.

I'm going to go back to my surveys. And like you see here, I have a number of results collected. I can see them here in results.

I'm going to go to this one. I can see a summary of those results per question. and the trend of responses of where I've got them per, when I've received them per days, and I can export this in a CSV. Second.

And it's going to look, you know, like a basic, like a basic file. So this would be the end-to-end flow of the survey, and I'm going to pass on to Diana to show you how the connector, survey connector, works. You know, again, it's an incipient version of the connector.

We're still... going through it and we're going to expand the number of use cases we're going to go with using it.