 Well, hello everybody. Good morning. Good afternoon or good evening, depending on where you're joining us from today. Welcome to Engineering for Change, where you foresee for short. Today, we're very pleased to bring you a special segment in E4C's 2016 webinar series, focusing on mobile data collection. My name is Yonah Randa, and I'm the Director of Engineering for Change Programs and I'll be the moderator for today's webinar. I'd like to take a moment now to tell you a bit about the Mobile Data Collection series. The widespread availability of mobile communication offers international development researchers, practitioners, and students new tools and techniques for collecting field data and determining the success of projects. So we've partnered with the Development Impact Lab at UC Berkeley for a series of six webinars to introduce a sample of the survey software tools and demonstrate how to implement each tool in practice. For a recorded introduction to the series, we invite you to visit the E4C home page. Today's webinar is this third in the series, featuring survey TPO, introduced by Faisan Zewan of Dugiliti Inc. Our next webinar will be with VotoMobile on March 16th at 3 p.m. each year's better time. If you would like to make a recommendation for a specific platform, future topics and speakers, we invite you to contact the series team via the email addresses visible on the slide. Now before we move on to our presenters, I'd like to tell you a bit more about E4C, who we are. E4C is a knowledge exchange platform and global community of over one million engineers, designers, development practitioners and social scientists leveraging technology to solve quality of life challenges faced by underserved communities, including access to clean water, sanitation, sustainable energy, improved agriculture, and more. We invite you to join the E4C by becoming a member. E4C membership provides costly access to relevant and current needs, professional development resources including jobs and fellowships, and a growing database of hundreds of properly leading products in our solutions library. E4C members enjoy a unique user experience based on their site behavior and engagement. Essentially, the more you interact with our site, the better we'll be able to serve you resources that meet your needs and interests. We invite you to join our passionate global community and continue to make people's lives better across the world. Please check out our website, EngineeringGoodChains.org, to learn more inside out. We're excited to collaborate with Dill on this and future webinars. Dill is an international consortium of universities, research institutes, NGOs, and industry partners addressing global poverty through advances in science and engineering. Dill has had part of the University of California Berkeley and was launched in 2012 with the support of the U.S. Agency for International Development through the U.S. Global Development Lab. This leverages the innovative capacity of world-class universities to design development solutions, which couple new technologies with novel economic and behavioral interventions. Dill calls this approach development engineering. The webinar you're participating in today is part of E4C's professional development offerings. The E4C webinar series is a free, publicly available series of online seminars showcasing the best practices and thinking of development practitioners. Information on upcoming installments in the series, as well as archive videos of past presentations, can be found on the E4C webinars page. If you're following us on Twitter today, I'd also like to invite you to join the conversation with our dedicated hashtag, hashtag E4C webinars. Now, a few housekeeping items before we get started. Let's see where everyone is from today. In the chat window, which is located at the bottom right of your screen, please type your location. If the chat is not open on your screen, you can access it by clicking the chat icon in the top right corner of the screen. Thank you, everyone, for entering your location and we welcome you all from all around the world and all around the states. Any technical questions or administrative problems should go in the chat window. During the webinar, please use the Q&A window, which is located right below the chat to type in your questions to the presenter. Again, if you don't see this, you can access it by clicking the Q&A icon in the top right corner. If you're listening to the audio broadcast and you encounter any troubles, please try hitting Stop and then Start. You may also want to try opening up WebEx in a different browser. Following the webinar to request a certificate of completion, showing one professional development hour for the session, please follow the instructions at the top of the E4C professional development page. All right. And it's now my pleasure to introduce to you our speaker for the day. We have with us five on day one of Disability Inc. I'm not going to read the bio this morning, but I will just hand it over to Faison to take that to you and introduce us to Survey CTO. Thank you so much for joining us. Thank you, guys, for hosting the webinar. And thank you, everybody, for taking the time out of your day to listen to me talk a little bit about Survey CTO. So I have to briefly introduce myself. I'm Faison. I work at Survey CTO, which is a mobile data collection tool designed for resource constrained settings. So if you're collecting, doing surveys, monitoring and evaluation, et cetera, and field settings where you don't have an internet connection but you want to collect data using smartphones or tablets, you could do that using Survey CTO. Before joining Survey CTO, I actually spent many years myself in the research world. I was working for Innovations of Poverty Action, which is a partner of the Poverty Action Lab at MIT as a research manager in Kenya, where I ran a few different impact evaluation studies. In particular, for example, I did a lot of research on unconditional cash transfers in partnership with an organization called Give Perfectly, and also did a few different studies such as on the impact of vocational skills training for women who own small and medium enterprises and impact of extension training for farmers to improve farm yields. I also worked and managed the Boussara Behavioral Economics Lab, which is in Nairobi. And yeah, in the process while I was doing all this work, at the time when I was working at IPA, we were doing transitioning from paper surveys to using digital data collection because of all its advantages. And so I sort of was at an exciting pace in the organization where we got to actually help projects transfer from paper to digital data collection. And in the process, I myself used a lot of different tools for my own research, learned a lot of lessons in the process, and at the end I decided to join Service CTO because I was so impressed with what the company was doing and thought that in the digital data collection space they were doing a lot of interesting things and wanted to sort of bring my own experience to help inform that. So before I actually dive into talking more about Service CTO, I actually wanted to first get to know the attendees a little better. So if you can in the chat window so that everybody can see, type out sort of your responses to a few of these prompts. For example, how many people here have conducted any surveys before even using paper? And how many of you have worked with other mobile data collection tools or even Service CTO before? And what are sort of the challenges that you faced collecting data in the field? Yeah, and I can tell you a little bit about my own work. Like I said, I've done sort of surveys both on paper and using a variety of data collection tools including a Windows tool called Blaze, Open Data Kit, which is what Service CTO is based on, and Service CTO itself. And I mean the challenges are many, ranging from sort of trying to figure out, making sure that the data that I'm collecting that my surveyors were out in the field, who are in remote places, can get me the data easily, who can collect the data easily, and for example, I can monitor their work, audit their work, things like that. All right, so I see Enrique says he's mainly used paper. Oh, Chris and Chris says he's used paper. Oh, okay, Kristen, thank you, Kristen, for the shout out, I appreciate it. Yeah, other challenges that people have faced? So there's a few different thoughts that people had, and I'll keep an eye on these as they keep coming in, but to quickly summarize what we have so far, and then I'll sort of dive into Service CTO and how it could potentially address some of the challenges you guys have. So I think a lot of people mentioned the issues around quality, so making sure that the data you're collecting is high quality, being able to catch errors, things like that. And for a lot of people mentioned that they need to be able to use something that will work offline, so in a setting without any internet connectivity, and also being able to transfer data easily once it's collected to where you can analyze it. And yeah, so I'll address some of these topics as we go through the presentation. I'll come back to some of these specific challenges people have faced in the Q&A. Yeah, so thank you so much, and yeah, you can keep sort of chatting in the window if you have more ideas or points you want me to touch on. So first, sort of to give you a little bit of background about Service CTO and why Service CTO was started. So Service CTO is actually founded by Christopher Robert, who's a research fellow at the Harvard Kennedy School of Government and also does a lot of his own economics research in partnership with J-PAL in South India. And he first started Service CTO when, you know, in his own research in 2011, he needed a tool for collecting digital data from an offline that was both affordable and could be used easily by his team. So, you know, he was facing a lot of the same challenges that people here are facing, which is around issues of data quality, around issues of being able to work offline. And, you know, he didn't want to reinvent the wheels, start building something from scratch. There were a few different tools available at the time. And he thought the most promising one was an open-source tool called OpenDataKit. And actually, the ODK team will also be presenting as part of this webinar series in a few weeks. OpenDataKit was a great starting point. You know, we have a great relationship with the team. They're doing a lot of amazing work. But it is as an open-source tool. It can be a little bit rough around the edges. It's not supported. And so it does require a little technical capacity on the users and to be able to use it, install it, maintain it. And what Chris wanted was something that had all the strengths of ODK, but at the same time could be used that had, you know, professional support team behind it so that if you needed help, you could get it in a timely way. That was a more polished product for more professional use. So, you know, for example, there were some reliability issues that he wanted to fix and something that was sort of off the shelf. So it was as easy to use as Gmail. You sign up and you're good to go. And sort of that's how ServiceCTO was born. He took OpenDataKit and added a lot of these improvements focused on reliability, flexibility, and support. And sort of, you know, in the space of all this, all the, so yeah, so that's how she started ServiceCTO. And, you know, for those of you who are familiar with the digital data collection, you'll know that there's a whole bunch of these tools out there. We're not the only one. I think Cobra presented last week or two weeks ago, ODK is presenting. There's a few other serving tools out there. And so I wanted to sort of explain where we fit sort of in this space of digital data collection tools. So given our background, we sort of view ourselves as sort of the perfect fit between, you know, the open-source tools and sort of slightly more expensive paid tools. The idea being that we get the strength of both, you know, open-source flexibility and power and the professional reliability and stability and support of paid tools. And when we're building our ServiceCTO, we focus sort of on a few key areas that we, you know, what the software and the company should represent. One is we wanted a tool that's powerful. So, you know, whether you're the World Bank and IPA or you're a smaller NGO doing, you know, you know, data M&E, you should have a tool that can sort of address all your needs that can handle short surveys and long surveys that can handle, you know, all sorts of complex survey design requirements. But at the same time, it should be usable and manageable. So it should be, you know, easy to use. It shouldn't require you to be a technical expert or, you know, require a lot of coding or you could really use it or a lot of training. We also wanted to make sure that it was a tool that was well supported. So we have a team, a great team of staff who themselves have lots of experience in the field and research. And so, you know, they understand the user's contacts are always very responsive. So yes, we wanted to build something that had a great team behind it so that we can help all our users get the most out of the platform. And at the same time, we wanted a tool that was still extremely reliable, secure, and affordable. You know, it's one thing to have lots of fancy features. It's another to make sure that they actually work in the field in an offline setting when you really need them to. So yes, we focus a lot on making a tool that's very stable. We pay a lot of attention to details and do a lot of rigorous testing before we roll it out to our users. And actually sort of dive a little bit more into that. You know, like I've already mentioned, we have an app that is powerful. So, you know, we wanted something that was very flexible. You can do pretty much anything you need to do for your survey. Another area we focused on is quality. So for example, we've added lots of features to allow you to monitor your surveyors and check the quality of the data that's coming in. So for example, people mentioned that they, you know, they're always worried about the quality of their data. And while moving from paper to digital, addresses some of those issues, we felt that we also wanted to take the potential of a digital tool and take it to the next level. So for example, we've added features like audio and text audits which lets you, you know, invisibly listen in to different parts of the survey so, you know, without the survey or knowing. So basically your microphone, the microphone on the device will turn on invisibly record a clip. And then when you get your data later on, you can listen in on this clip later. I mean, the survey has no idea. We also added what they were up to. We also added what we call frequency checks on the server which allow you to basically, you know, set up checks on your incoming data to check for patterns like interviewer effects. You can see obviously metadata and look at differences in the metadata between one server and the team. So for example, you could see if one survey or survey is much shorter on average than the team as a whole. So to tell you that something suspicious is going on. So we've added all these features that allow you to monitor your data for quality and catch errors very quickly and detect fraud. And another area obviously that matters to us is performance. So we have users who are using us for small scale scale surveys all the way to users who are using us a very large scale surveys. For example, you know, they use Service C2 for the 2015 Mexico national elections where they had one day to do polling around the entire country and they had tens of thousands of submissions coming in. And so we wanted to make sure that the platform we build is able to, is stable and able to handle all sorts of loads and needs of users. And I think this is also where we differentiate ourselves from a lot of the other tools. You know, I think it's easy to have a cloud server. It's not easy to have a cloud server that is very stable, that has 100% uptime and that can handle a lot of loads. So if you're an organization that's doing very large scale surveys, I think you'll see there's a noticeable difference in performance between Service CTO and some of the other tools. So yeah, it's an app that's powerful but still usable. So those of you who've used ODK before, you'll know that, you know, the standard way to program in ODK and ODK-based tools, a creative survey is using an Excel spreadsheet. And you can still do that in Service CTO. We have power users who find the flexibility of the Excel format very appealing. But we wanted something that was more accessible for users as well. So we actually built a drag-and-drop form builder, which I'll show you in a little bit as part of our demo, which makes it much easier for a beginner user to start creating and doing surveys in Service CTO. Similarly, you know, I talked about the high-frequency checks earlier. So people from organizations such as IPA or the World Bank will already be familiar with how to do high-frequency checks. And you know, you could always have created them and coded them in something like Stata, but that required a lot of statistical knowledge. It required advanced knowledge of coding and tools like that. And so it wasn't really very accessible to users. And so again, similarly, we actually built a drag-and-drop version on our server, which very quickly and easily lets anybody set up a quality check of the same kind without having to have all that technical know-how or hiring somebody who does have that technical know-how. Similarly, also on the analysis side, you know, we've integrated with a service called Statwing which automatically visualizes your data for you. So again, something that previously would take a lot of time and effort and technical knowledge to code up in Stata or SPSS or SAS, you cannot easily do in a single click or two with Service CTO. And again, I'll demonstrate this for you in our demo. And you know, so an app that's powerful, but still usable and built on solid foundation. So I already touched on this a little bit and I wanted to reiterate, you know, it's one thing to have a tool to focus on features and features obviously important, but something that also matters in software is making sure that the software actually works. So you know, there's very little point in having, you know, XYZ features if they don't actually work when you need them to. And so at Service CTO, we've focused a lot on making sure that the core foundations of the platform are solid, that it's a very reliable platform that works. We fixed, you know, hundreds and hundreds and hundreds of bugs that we found in other tools. We'd rigorously test everything before we roll it up to users. We let users choose when to update to a new version so that if they're comfortable with the current version they're using, they're not forced to change partway through data collection. Similarly, we also then make sure to back that up with an excellent support team, which isn't just, you know, again, like I said, isn't just sort of customer support stuff, but actually researchers from the field who understand the user's context, who spend a lot of time in care, sort of listening to our users, understanding what their issues are and what their needs are, and responding in a thoughtful way. So we sort of view ourselves almost as partners and colleagues of everybody who uses us and work very closely with our users to make sure that their project runs very smoothly. And finally, another very important foundation that we think isn't talked about enough is also security. I think most of our users are collecting very sensitive, identifying information. And so we also wanted to make a platform that, again, went beyond the sort of the most basic level of security to something that truly met the needs of the IRBs that made sure that their respondent's data was actually protected. So, you know, for example, we made sure that not only is all our data encrypted in transit when you're sending it from the device to server, but that, you know, you can actually encrypt your data at rest even using what we call public private key pairs. So only you as a user have will have the decryption key, which will decrypt the data when you download it onto your computer. So even we as a service CTO could never view that data on our servers. Similarly, we spend a lot of resources on making sure that our servers have, you know, the state-of-the-art firewalls that they're monitored 24-7, you know, for any attempts at breaches, we lease all our servers from Amazon Web Services, which has security guards and CCTV footage monitoring of all their data centers. And we've also added a whole bunch of features that easily let users separate automatically, you know, personal identifying information from other data, so that if you do have to share data, you're sharing it in a secure way without compromising anybody's privacy. And, you know, I think these issues aren't talked about enough, but do matter a lot when you're trying to decide what your organization should be using to do all of their research. All right, so, you know, there's having said all that, there's obviously a lot more that I could talk about with service CTO, but, you know, given the time constraints of this webinar, I'm going to actually, you know, now dive into a live demo which sort of shows you the workflow and how you would work in service CTO from start to finish. But if you wanted, you know, we have a few of these extra, you know, a lot of other features that people might find interesting, and I'm happy to address them during the Q&A. So, you know, for streaming data from one form to another, we have, you know, case management which lets you push assignments to individual surveyors. You can, you know, we have support for streaming data automatically to external systems like Google Sheets or Fusion Tables or any sort of information management system you have using our APIs. So, yeah, so I'm not going to get into all of these right now, but if you have any interest in the Q&A. Now, having said all of that, how does service CTO actually work? The workflow or the process is sort of very simple, five-step process, right? You design your form and service CTO, you deploy it, and you can then collect your data offline in our Android app on smartphones or tablets, or you can collect it even online using our web forms. And then you will, as data is collected, the servers are collecting data offline. The service gets saved in the app until they are able to connect online. And then data as soon as it comes in is aggregated and can be analyzed or exported instantly. So I'm now going to switch to sharing my screen so that you guys can actually see the demo. All right, so let me turn on screen share. All right, so I think everybody can see my desktop now. So you'll see this is the service CTO server console. I'm already logged in. So the way it works is when you create a service CTO account, everybody gets their own URL. So you'll see I'm using a URL called use.servicecto.com, which is a server I use for demos. But you'll have your own URL and your own server console, which you would log into by going to that URL. When you log in, this is what your server console looks like. You can see the workflow or the layout of the product, which is design, collect, monitor, and export. So the first step when you use service CTO is to design a form. And you can do that by clicking the start new form button under the design section. You can give it a title. So let's say I was creating a form called sample form 2. And you can even actually use a library of forms you already have to get started. So for example, you could say, let's start with that. You click next. And then you'll click the edit online button, which will launch our form builder in a new tab. I already did that a little earlier so that we don't waste too much time on the call. So yeah, so you can see when you open that form, this is what it looks like. And then you can easily sort of edit the form by adding questions. So you can add all sorts of question types, visible fields. You can add calculations which are hidden fields, for example. So you can sort of modify the form very easily using our drag and drop form builder. Whenever you're done and ready to start collecting data, you can just hit save and deploy. And as soon as you do that, the form appears under your your form section. So you can see for example, we have a sample form here which I created earlier for the demo. And then once the form is here, you can start collecting data in two ways. You could deploy the web form by switching to the collect tab and either clicking fill out or sharing the web form link. And if you did that, it would open a web form, for example, in a browser tab like this. This is what our web forms look like. So you can see I'm going to swipe forward. I'm going to say, yeah, I'm going to continue. All right, let's fill in the survey. All right, all right. Let's fill in the survey. All right, and I'm going to quickly submit. So that was just a quick short survey. And now the form has been submitted and it actually shows up on the server. An alternative way to collect this data, especially if you're collecting it offline, is to use our Android app. So I have a simulation of an Android phone up on my screen. All right, so this is what our Android app looks like. You can see it's a very simple screen, again, designed to be super easy to use, especially for surveyors. So you open the Android app. You click get blank form and you'll see that the form that we've created on our server is available for download. I click get selected. And once I do that, the form is now available on the device even offline. And then I can fill in as many surveys as I need, completely offline by clicking fill blank form and then selecting the form that I want to fill in. All right, so I'm going to also fill this form in just so that you guys can see how the Android app works. And again, you can save form and exit. And then once saved, it shows up under send finalized form from where we can upload it whenever we do get an Internet connection. All right, and so then once we do that, the data is now actually we can switch over to our monitor tab. We should be able to see our submissions come in. All right, let's look at form submissions. Let's refresh this. There we go. We can see there's two submissions that I just submitted, one from the web form and one via the Android app. And then you can export your data or analyze it by going to the export tab. So here we have our sample form. I could download the data as a CSV file by clicking download or I can click the analyze button and open the data in our visualization window. This form doesn't have too much data, so I actually created some sample data to show you guys what it looks like when I click the analyze button and then it would open an analysis in a new tab, which I already had open for you earlier. So you can see this is what the visualization space looks like. All the variables in our data set are on the left and we can select a variable and choose to describe it, which sort of creates a chart or table automatically in the right-hand side. And you can also look at relations variables for analysis purposes. So let's say I wanted to see and by surveyor if my answer to certain questions varied. So let's look at vegetable consumed in kilos on average and see if there's an interviewer effect. So I can click those two and I click relate and you can see that it will tell me it will run a statistical check and tell me, okay, there's a strong statistically significant relationship between surveyor ID and vegetables consumed in kilos. And what this actually very quickly tells me is that there's based on who's doing the survey, the answers for this variable vary significantly, which means the survey is actually having an effect on the answers being collected. And you can see there's huge difference for surveyor 16, the average is five and a half kilos, whereas for surveyor 18 it's only three kilos. And that's sort of the whole process for survey CTO from start to finish, from launching your survey to collecting data and analyzing it. So I'm going to start off the screen share. Yeah. And so I think that sort of brings me to the end of my demo and my very quick run-through of survey CTO. And I wanted to leave a lot of time for Q&A. So yeah, based on what people saw, if you have questions, comments, if you want to learn a bit more about some of the other features that I couldn't touch on given the time constraints, yeah, please sort of type them out actually in the chat window so that everybody can see. So actually, thank you for that first and foremost. I really appreciate that was probably one of the fastest demos we've ever experienced. But I also wanted to hear some questions in the Q&A window. So one question that team is regarding the analysis. Do the analysis features work on encrypted data? So very good question. So yes and no. So the way we set up encryption is you can choose to encrypt your form and still mark individual fields as publishable. So what that will allow you to do is you can encrypt your form so that your identifying information is encrypted but any non-identifying data or fields are still visible to the server and then you'd still be able to specifically analyze those fields in the visualization window without having the identifying information unencrypted. Okay. And we have another couple of questions here in this series. So we had featured Kobo Toolbox. I'm not sure if you're familiar. So the question here, a little challenge here is despite the fact that Kobo has intended really for humanitarian organizations, what is your difference or value out in comparison to Kobo? Sure. Very good question. So I think, I mean it's always like I say, I always like to say talk is cheap and the best way to make their own decision and obviously I'm biased. But I think the big difference is in the three key areas, which I mentioned, which is one is reliability and the other support and then security. So yes, we do have a Dragon Draw Form Builder. Kobo does too. In fact Kobo, I think they did it first. I fully admit and they were an inspiration for it. But if you've used the Kobo Dragon Draw Form Builder there's a lot of things that aren't supported in the Dragon Draw Form Builder that you could do in Excel, for example. And what we wanted was a more complete form builder so that even if you wanted to do, you know, create all sorts of question types that you were used to, that you would otherwise need to program directly, you could still do that in the form builder. That's one, you know, big area. The other big difference is just support. So we have, like I said, you know, very professional support team that you know, is always ready to respond to all our users so I think it depends, you know, on the user, whether they're comfortable and depending on the time and capacity they have, they might feel like, you know what, we'll support ourselves if we have an issue, you know, we have X hours in our day to sort of spend figuring it out. But if you're sort of more, if you have a more streamlined operation, you have more of a time crunch and you just, or you just need sort of, you just want somebody who's always there for you to sort of got your back, then I think it's worth using Service CTO because of that support that we provide. And then the other, the final issue is security. So, you know, I think, like I mentioned, it's not always visible on the front end, but a lot of the work and important, a lot of the differences between software happen on the back end. So, you know, what is your server infrastructure like? How many resources are being spent to make sure that different user servers are siloed and protected from other users? What resources are being spent to make sure that, you know, the firewalls and there's excellent firewalls that are available in 24-7 that, you know, the servers have uptime, that the servers have a lot of memory and capacity to handle lots of surveys. And that's, I think, a big area where we expand a lot of resources compared to global and other tools. Yeah. So, I think those are the three things. And on the note of support, do you offer support in Spanish? So, we're not exactly. So, we do have lots of users who use that, you know, primary Spanish speakers, and we've done our best to support them. We basically tend to use Google Translate for a lot of our support in that case. But, yeah, we don't have sort of a fluent Spanish speaker on staff yet. It's definitely something we want to expand into. But, yeah, I mean, I'm happy to also put, and we can touch with some of our users in Latin America and, you know, he can talk to them as well to learn about their experience. Yeah. So, I'm going to come back to a couple of things. I part question, but I just want to make sure that we spread the love here a little bit. So, I think there's some questions relative to the actual mechanics of Survey CTO. So, is it possible to show a little bit more about the relevance and constraints in the form, Bill Sir? Oh, sure. Yeah, of course. I'm going to clap all these and also review how skip pattern works. Of course. Sorry. So, let me just do that. So, I'm going to switch over to my screen share again. Actually, I think you need to make me a presenter for me to do that. I think that, if I can do that, I think actually, our administrators have to give you, there we go. You're all set to go. Cool. Yeah, I think I'm. All right. So, I'm going to switch over to our form designers. Yeah. So, let's sort of walk through that. So, let's clear the question. I'm going to clear the question inside my consent group. So, it's only asked of people who are doing consent. So, let's say I'm creating an integer question, you know, what is your weekly income, right? So, you type the question text, you select the question type, and you hit configure, and that opens the pop-up window where you can configure your skip patterns and constraints. So, the first section is very simple, and then you can add, you click more options, and it sort of opens up the relevance and constraint builder. So, if I wanted to click add relevance, I can specify it by hand or I can specify it by hand or I can use a drag and drop, click through wizard. So, let's just use the wizard and you can see. All right. So, let's say I wanted to only ask this question if the user has given consent. All right. So, let's say feel is relevant if all of the following conditions are true. All right. Field consent is equal to the numeric value 1, where 1 in this form is equal to yes. All right. So, I hit save and I could add more conditions if I wanted, and I can also then edit by hand. You can see it actually appears some expression, so that if you're a more advanced user and you want to directly co-code the relevance, you can do that too. For the constraint, it works in a similar way. Let's say I want to add a constraint. I click add constraint. I can click add with a wizard and I want to create a numeric constraint. It's an income field and I want to allow answers in the range of 0 to 10,000 say, because I think more than 10,000 would be, say, a very crazy answer. So, I click numeric. I hit next and I can say minimum value is 0. Maximum value is 10,000. I could even allow exception. So, let's say for this question I said enter minus 99 for don't know or minus 98 for refuse. So, I can create those exceptions. If I want to display custom error message, I can type that in. Please enter a realistic weekly income. All right, and I hit save. And that's it. I can then hit save now. I have to give a unique name to this field. All right, let's call it income. All right, and we can see we have our field created and if you expand it, you can see it even tells you the relevance visible if this expression is true. And the question for the group is true. Constraint responses only allowed if this expression is true. So, you can actually see, quickly get an overview of what, when different questions will be asked, et cetera. So, that's sort of a demo of how to build constraints and relevances. And I think part two of that question was they wanted to explain skip patterns a bit more. So, skip patterns in service CTO and are interchangeable with the video relevance. So, it sort of just flipped on its head a little bit where in a paper survey, the way patterns work is when you add a question, you have an arrow saying, okay, if they've answered yes to this question, jump to question five. Whereas with service CTO and other similar tools that use digital data collection, instead of specifying a skip pattern, you specify relevance. So, you say for question five, you say ask this question when XYZ is true. All right. And then if you build, I'll go ahead. No, no, sorry. I'm going to kind of skip around a couple of these other questions that are related to the actual interface. So, the other question was if you build a survey in the drag and drop, does this translate over the XSL sheet like ODK uses? Can you go back and forth with this? You can absolutely go back and forth. So, actually, let me see if I can do that again. Yeah. So, we designed it with the idea that people will be able to use both interchangeably. You could start a form in the drag and drop form builder and then switch over to XSL. Maybe you're now offline. You need to be working offline more easily or you want to do your more comfortable in XSL. And then you can actually also have forms in XSL that you can upload into the drag and drop form builder. So, the way to do that is say I've created this form and I could just hit export which will say export to download and export to Google Sheet, especially if you're collaborating with team members and you want everybody to be able to edit and comment on the form, then Google Sheets is a good alternative. So, I'm just going to, for now, since the question was about XSL, I'll export to XSL. Right. Then it'll ask me to save sample form. Let me just save it to my... I'll just save it to wherever. XSL, this is what it looks like in the XSL. You can also do the reverse where you have a form in XSL that you upload into the drag and drop form builder. And the way you would do that is you would just go to your design tab and upload form here. So, you would upload the XSL file here and once it's uploaded, you can always open it in the form builder by clicking edit. Great. And someone, another question was related to the API. Could you describe how a user would use this with an M&E app like DHIS2? Hello? We have a REST API. Can you hear me now? Yes, we can hear you now. Anyone tell me for a minute. Okay. So, we have three different APIs which would let any external system. So, if it's DHIS, if you have some other kind of custom IMS system, which can query our server using APIs and whatever format, you know, the format you desire. So, the three APIs you support at the moment are you can arrest API which lets your external system including, say, those DHIS query data using an API call in CSV format. We have a JSON API which lets your external system query your data from the server using in JSON format. And we also support the standard ODK API which is XML, the XML ODK briefcase API which would let your external system query your server using pull data and XML format. How the data is then mapped in your external system would be up to you because you would sort of know that best and then you can sort of pick whichever API you want to use and have your system map the data that's pulled in to fit your system. Great. And in terms of multiple languages, how do you use multiple languages in the form filter? Great. Questions. So, yeah, I mean just we support you can put as many as you want. Let me show you again. So, let's say, switch to screen share. All right. And so I'll open our form builder. So, let's say if you go to, you have form settings, you can see there's, you can see there's languages right now only English. If I wanted to add a language, I would click edit form settings, right? And you can see there's languages I can hit edit and you can add a language here. So, let's call it, you know, let's say I wanted to add Spanish, all right. I can add and let's say I wanted to add French, all right. And I hit OK. All right. And now I have these three languages added. I hit save and now when I create a question, all right, let's just create a text question and I hit configure. If I go to click more options, right, you'll see where the label section opens up. I have the label in English with the question text in English and then now I have extra appeals for entering the question text in each of the languages that I added to that form. And you can add hints and similarly if you have multiple choice questions, you will get prompts to enter the answer labels for the answer options in each language that I added. So, there's this question. I hope I'm tracking this one correctly. It's regarding updating a survey that has the information with an error in the tablet for upload later. I'm not sure. Does that question... Sorry, let me stop my screen if I read the question. It will be possible to update a survey that has information with an error in the tablet for upload later. Not entirely making sense to you. It seems like it's a very specific question. Felix, I think this is your question. Maybe you can e-mail me and I'm happy to answer it because I think that depends a lot on the specific error that you're getting and what the issue might be. So, if you can e-mail me, I can answer a question. So, you can e-mail me at fezon at surveycto.com and I'm happy to answer it. You can send me the error message you're getting. Sorry. We are coming up on time. I'm going to close it out with one last question and that is, again, another competitive advantage question if you will. Could you compare SCTO, surveycto with ComCare? Why would you choose one over the other? Good question. I think, again, this really depends on your exact references. So, for example, they want different features. I think we have different sets of features. So, there's a lot of features in surveycto that aren't in ComCare. I think in terms of affordability, including support, I think we're much more scalable and affordable platforms. So, like I said, even with our most basic tier, we include an excellent support team and it's always supported. You can ask all the questions you want. You can email or anything like that. And, you know, we have our, yeah, we also have our, and again, like I said, there's also issues around security and reliability. So, again, I can't always speak to, I don't know, ComCare's infrastructure, but I do think that if you look at our reviews and talk to other users of ours, I think everybody sort of stands by the fact that they found both surveycto very stable and stable as a platform. And again, I think that's one of our strengths compared to a lot of the other tools out there. But again, I encourage whoever wants to try out all the tools they want. We have a free trial as well. We give a lot of people trying to test surveycto to make their own decision. I feel like the proof is always in the pudding. It won't be until you try it that you really know for sure which you're interested in. I think that's one of the things that we encourage you to do today and be very honest and clear in your addressing of the questions from our participants today. And I'd like to thank everybody for attending. For those of you who are interested in receiving a professional development hour for this session, the code is listed on the slide right now. If you can't reach FIZON, you're not going to be able to get a professional development hour. We have a program called the FIZON mobile data collection series. We do have our next webinar with photo mobile on March 16th at 3 p.m. Easter standard. Thank you for attending. Have a fantastic morning, afternoon or evening depending where you are. We look forward to catching you on the next