Most child helplines still take phone calls while children have moved to text
Most child helplines still primarily take voice calls, while the children they serve increasingly communicate by text, and some helplines run social media counseling from a single office phone. Dee Luo, a product manager at the nonprofit Tech Matters, helps build Aselo, a shared contact center for helplines worldwide. How do you build one platform for dozens of organizations with different laws, budgets and ways of working, without rebuilding it for each one?
See how beta testing, JSON-based configuration and field visits let one platform serve many NGOs
Dee Luo, Product Manager at Tech Matters, explains how her team is co-developing Aselo, an open source cloud contact center shared by child helplines around the world. She shows how a beta program with ten helplines, infrastructure as code with JSON configuration, partnerships with Twilio and Okta, and in-person relationship building help one platform serve organizations with very different needs, budgets and privacy laws.
“And as we all know, kids are continuing to move to more text-based communication in their day-to-day lives. So there's a widening gap in how the help lines can even be reached.”
“As a software provider, we are very clear that the helplines own their own data and they are the decision makers in how their data is being used.”
What you will learn
Identify the gaps that make fragmented, custom-built or spreadsheet-based tools costly for nonprofits that share a mission.
Design a beta program with a diverse group of user organizations, regular releases and feedback surveys to shape a shared product.
Apply an infrastructure-as-code approach where per-customer configuration lives in simple JSON files that non-engineers can edit.
Plan for privacy, security and data ownership when a platform holds sensitive data about children across different legal regimes.
Build trust with remote software users by placing team members close to them and observing how they actually use the tool.
Key takeaways from the speaker
1. Attendees will learn how the child helplines and Tech Matters built a collaborative process that enabled the nonprofit users to prioritize the challenges to be addressed and co-create an innovative tech solution for an entire field.
2. Attendees will hear how the development team planned for critical privacy and security issues, while supporting data collection to further global advocacy for children.
3. Attendees will learn the nuts and bolts of creating digital public good to be shared by fields that are not used to sharing tech infrastructure.
Details
Level
Intermediate
Format
Talk
Technical depth
Introductory technical
For
Early career, Mid-career
Length
16:41
Published
June 2021
Questions this talk answers
Why did child helplines need a shared contact center platform?
Their tools were fragmented, often custom built, expensive and hard to maintain, some recorded data by hand in spreadsheets, and most supported only voice calls while children moved to text. The pandemic also forced counselors to work from home, which in-office phone systems could not support.
How can one platform serve helplines with very different requirements?
Aselo uses infrastructure as code: a generic framework shared by every instance, with each helpline's data fields, options and language defined in its own JSON file. This lets the product team, and eventually helpline administrators, customize instances without extra engineering work.
How did Tech Matters involve users in building the product?
It selected ten diverse helplines for a beta program, released new features roughly every six weeks with documentation and training, and sent surveys after each release. The feedback revealed helpline operations and new feature ideas the team had not prioritized.
How did the team handle launching software during the pandemic?
When travel bans blocked visits, Tech Matters hired a full-time team member in South Africa to focus on the first deployments. She later visited Childline Zambia, ran usability studies with counselors and built trust between the teams.
How does Tech Matters handle helpline data?
Privacy, security and strict, regulated data access are core values, and the helplines own their data and decide how it is used. Tech Matters aims to make data systems robust and reporting easy without dictating data use.
About this talk
This session will explore the challenges related to co-creating platforms designed to be used by hundreds or thousands of NGOs to maximize and support collective action. We will focus on Aselo, a shared cloud contact center (based on Twilio’s Flex communications platform as a service technology) being co-developed with child helplines, many of which struggled with capacity even before the pandemic. Children and youth have moved to social media channels, creating additional challenges for what have historically been voice-based helplines. This session will share the approaches to user-informed collaboration and the types of technology enhancements that can help the crisis response movement improve their capacity and effectiveness.
Letting non-engineers configure the platform (74 s)
Hiring in South Africa when travel stopped (84 s)
Thank you all for being here today. My name is Dee Luo and I am a product manager at Tech Matters. Tech Matters is a Silicon Valley based nonprofit dedicated to building shared technology platforms for the social sector. I'm super excited to speak to you all today and to support fellow women pursuing careers in the technology space. Go ladies. So today I'm going to be talking to you about Asalo, which is our project focused on building contact center technology for our child helplines around the world. We'll discuss the challenges developing a software as a service platform in the nonprofit space and the different approaches that we are taking to develop our solution. Keeping in mind the importance of user collaboration, privacy and security and scale.
Speaker 2: So what is Asalo and how did our project get started? Drew Billamoria, who is the founder of Child Helpline International, which is a global collective of about 170 plus different child helplines. She approached our CEO. time interviewing different child help lines, it was very clear that technology solutions across the network were very fragmented. While there were some existing tools, many help lines had rolled their own solutions. So the technology was custom built, expensive, and generally hard to maintain.
Contact center technology solutions do exist, but typically are built for more commercial enterprise use cases. For example, think customer support. For other help lines, data was being recorded entirely by hand and maintained across Excel spreadsheets and very which you can imagine is not only very cumbersome for day-to-day operations, but also makes aggregate reporting to donors and any data reporting incredibly tedious.
Another point to mention is that the majority of child help lines primarily or only really support voice calls. And as we all know, kids are continuing to move to more text-based communication in their day-to-day lives. So there's a widening gap in how the help lines can even be reached. On top of that, for help lines that maybe have adopted social media counseling, counseling conversations are typically handled across siloed systems. For example, some help lines will handle their social media counseling all through a mobile phone in the office.
And the last point I want to mention is the Covid-19 pandemic. So not only are helplines a direct resource for kids who are dealing with anxiety and mental health concerns as a result of the added stress of the pandemic, but stay-at-home orders mean that counselors in some countries need to work in home. And with data technology solutions and in-office phone systems, counselors aren't always able to service kids remotely.
Sorry. So there's a clear need here for modern technology that can unify the work of child helplines across the world, giving counselors the tools to efficiently and effectively engage with children in need. Additionally, a shared platform across help lines makes data aggregation across the network much, much simpler, which means the power of data to advocate and influence policy change around child protection. And that's where a sale comes in. So before we dive into the actual product and what we are building and to quickly go over some of our core values that are foundational in our software development. First, partnership. So partnership, not only with the child helplines that we are serving, but also with the rest of the NGO community. From the beginning, we have been dedicated to
building open source software with the intention of sharing knowledge and tools, not just to support children in need, but for the entire crisis response movement. Second, privacy, security, and reliability. We are supporting organizations that deal with emergency response on a daily basis and handle extremely sensitive and private information about kids. We recognize the importance and need for strict and regulated data access alongside local regulations. And lastly, data ownership. As a software provider, we are very clear that the helplines own their own data and they are the decision makers in how their data is being used. Our goal is to strengthen and service the child helplines by making their data systems more robust and easy to transform for a report, but we have no intention of actually
dictating how they are using their data. So with those key values in mind, what did we actually build? So we built a modern cloud-based solution that can be accessed just with an internet connection, which enables counselors to be able to work from home. Asalo is an omnichannel platform. We support voice calls, Facebook Messenger, WhatsApp messages, web chat, and soon Twitter direct messages, services all in one unified interface with the goal to expand to many more channels as the communication landscape continues to change. We're building efficiency tools within the interface so counselors can save time while collecting data, which gives them more time to focus on the actual counseling and servicing of children. Our solution has built-in reporting capabilities, not only giving helpline management insights into their operations such as wait times, but also synthesizing programmatic data so
helplines can identify the main issues affecting kids in their communities. And lastly, our solution is customizable, meaning each helpline has their own unique instance of a salo that captures their specific data requirements in their preferred language. Over the last two years that we have been developing this product, we've had to think about many challenges that really any software as a service product team has to consider with the additional considerations of being in the non-profit space with limited funding and very sensitive data. To start, these helplines, they all have a common goal of helping children in need, but how they achieve that goal can vary immensely. So for example, there's the variety of functionality needs. Helplines in the US and Europe with straighter data privacy regulations tend to be anonymous helplines
where calls are considered one and done, say, whereas helplines in Africa and Asia tend to do more hands-on case management and follow up on more serious calls to the helpline. As mentioned before, each helpline has a suite of different existing systems that sometimes not only service their contact center operations, but also are integrated with other operational aspects of the helpline, such as scheduling or payroll or integrations with government systems. Each of these systems can be dictated by different operating budgets, which is especially important to consider in the non-profit world with donor-based project budgets. Technical fluency can vary, not just for helpline administrators, but for individual counselors who are actually using the platform every day. Each region can have different channel priorities. WhatsApp is huge in some countries and very minimal in others. And perhaps most daunting of all,
each country has different legal and regulatory requirements around the data privacy of children. So I could go on and on about the different operating requirements of helplines, but now let's say we've managed to figure out all these nuances for one or two helplines, but then the question becomes how do we scale to handle 5 or 10 or 50 helplines? How do we build the technology in a way such that each specialized instance doesn't require duplicated or one-off development or implementation efforts?
And lastly, an obvious challenge, but worth mentioning, the COVID-19 pandemic and remote work generally. Launching a new software product that is being used as part of an organization's core function is a very involved process that requires switchover planning, training, data audits, etc., now add-on, six to nine hour time difference, unreliable internet that makes Zoom calls difficult, cultural communication differences, and the inability to actually meet with software users in person.
It's not ideal. So how did we tackle some of these challenges? I want to cover some of our top practices that guide not only our early product development, but also our continued growth as we scale up. So first, our beta program. At the beginning of our development, we put out an open call to the child helpline network and selected 10 child helplines that we hoped would represent the diversity of the network. The helplines were from all different regions with different levels of existing tech solutions and different requirements. Approximately every six weeks, we would release a new set of features to the beta helplines with detailed documentation and training guides to walk them through new product functionality.
With each release, we sent surveys to assess and prompt user feedback around ease of use for the features, usefulness to the helplines, and to further explore generally each helpline's specific use cases. While we did have a product roadmap of features that we knew we wanted to build, those feedback surveys really gave us tons of insight into each helpline's operations and also gave us new ideas for features we hadn't necessarily prioritized or considered. This approach to developing a minimum viable product for a soft launch ensured that we had a consistent and informative feedback cycle with actual helpline users. Next, in terms of actual software development, we took early on an approach called infrastructure as code, which is an emerging trend in the software as a service space.
The simplified idea behind infrastructure as code is that the core code configuration of the interface is just a framework. Each unique instance of the platform can use the same generalized framework, while the actual customization of the platform and what the helpline users and counselors actually see can be defined in simple JSON files that get plugged into the generic framework.
What does that mean in practice? Well, the approach allows for much more scalable deployments. So, the more we build features and functionality into the base customization framework, the fewer number of hours are spent doing one-off adjustments or shared or development on top of shared components of the platform for every single instance that needs to get spun up. This means that configuration and customization can be done by and defined by non-software engineers. So, our non-technical team members, myself included, who are more focused on success, gather and define those customization requirements, but actually configure the changes directly in the code. As a basic example, each helpline has different requirements around what data they need to collect about the caller to the helpline.
These data collection requirements can be easily defined and adjusted in a helpline-specific JSON file. If we need to make a new field required, add a drop-down option, or change the wording of a drop-down option, those changes can all be done by our product team, say, or hopefully, eventually, helpline administrators without the need to spend any additional engineering resources on those helpline-specific adjustments. In the spirit of partnership, but also efficiency, we also want to take advantage of and understand existing tools that we can use. Our platform is built on top of Twilio Flex technology, and we have close partnerships with the team at Twilio to understand how we can use their very sophisticated contact center tools and tailor them to the helpline movement. We use Okta, an industry
leader for access security software, for single sign-on and authentication. Using existing industry tools, especially in places where we may not be experts, not only helps us stay in line with best practices, but also pushes us to continue to find partnership opportunities, not just with other NGOs, but also with major tech players who have built the best solutions in their respective industries.
And lastly, one of the most important aspects of user-centric development is the dedication to relationship building with our users. So we had a set plan to launch a salo with two national child helplines, the national child helpline of Zambia and national child helpline in South Africa. We had that planned shortly before the pandemic hit, then the pandemic hit, and with the international travel bans in the U.S., we quickly had to pivot, and we decided to hire a full-time team member in South Africa, whose primary role would be focusing on the success of our first deployments. So not only did hiring in South Africa solve some of our time zone meeting issues, but it also gave us the room to focus more on the relationship building aspect of being a true software partner. So our South African team
member, her name is Humera, she was able to travel to the Childline Zambia offices last month. Some photos of the visit I'm showing on this screen right here. Humera is the one in the in the black t-shirt in the the top left corner. But so she was actually able to spend time with each of the counselors and and get to understand the helpline environment a little bit better. She answered questions about the platform, she was able to get feedback on some new features we were considering, do usability studies to validate some of our assumptions on how the software is being used.
Um, and probably most importantly of all, her visit really laid a foundation of trust and improved communication across both of our teams. Um, and we are very excited and very hopeful about continuing to build both in-person and remote relationships with our helpline partners moving forward. Um, I will end by sharing what's coming up for our team at Asalo and where we're hoping to grow.
So we currently have two helplines launched and have done demos with many, many prospective helplines from all over the world, um, and are hoping to launch 10 to 15 helplines hopefully in the next year, if not more. Um, with these deployments will obviously come the continued importance of scalability and reliability practices as we build more advanced features into the platform.
Um, we will continue to make our software open source with the hope that Asalo will grow, not only as a robust platform for the child helpline movement, but as a solution for any crisis response organization that runs a contact center. Um, and lastly, as a nonprofit, we know our partners are working on limited budgets and we are thinking through sustainable pricing models to ensure that the technology is affordable for helplines with smaller budgets with the same set of core features.
We have made a decade long commitment, if not longer, uh, to being a technology partner for the helpline movement. And we are excited to say that this is just the beginning. So thank you so much for listening. Um, and we'll take any questions for the next five minutes. Um, if we have any questions, and yes, Kelsey agreed feedback from people who are actually using the tool is, is super, super helpful. It really, um, our, our, when our team member visited the team in Zambia, um, being able to just even watch them figure out like where they're clicking buttons and how to find things and kind of their thought process around how they complete actions in the platform is really, it was really, really so informative. Cool.
All right. Um, well, if, uh, you have any questions, um, contact info is here. Um, and just wanted to say thank you so much, uh, for this time and hope you enjoyed learning about the sale out and the work we're doing at tech matters. And, um, thank you to all the women who are here, um, supporting each other and, uh, building a community of women in tech really love it and think it's so, so inspirational.
So, thank you guys so much. Um, feel free to email me if you have any questions.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
How can one software platform serve child helplines around the world?
Dee Luo of Tech Matters explains how Aselo was co-created with helplines that differ in laws, budgets, channels and ways of working.
In short
Dee Luo, Product Manager at Tech Matters, argues that nonprofits working toward the same goal can share technology infrastructure if the platform is built with them, not for them. Using Aselo, an open source cloud contact center for child helplines, she shows how a diverse beta program, infrastructure as code, partnerships with established tech providers and on-the-ground relationship building let one product adapt to very different organizations.
Key takeaways
Attendees will learn how the child helplines and Tech Matters built a collaborative process that enabled the nonprofit users to prioritize the challenges to be addressed and co-create an innovative tech solution for an entire field.
Attendees will hear how the development team planned for critical privacy and security issues, while supporting data collection to further global advocacy for children.
Attendees will learn the nuts and bolts of creating a digital public good to be shared by fields that are not used to sharing tech infrastructure.
Why child helplines needed something new
The project began when the founder of Child Helpline International, a global collective of about 170 helplines as Luo cited, approached Tech Matters. Interviews across the network showed technology that was fragmented: many helplines had built their own custom systems, which were expensive and hard to maintain, while others recorded data by hand in spreadsheets. That made daily operations cumbersome and reporting to donors tedious.
The bigger problem was reach. Luo explains that most helplines primarily or only support voice calls, while the young people they serve communicate differently: "And as we all know, kids are continuing to move to more text-based communication in their day-to-day lives. So there's a widening gap in how the help lines can even be reached." (2:10) Some helplines handled social media counseling through a single mobile phone in the office. The COVID-19 pandemic added pressure: children needed support more, and counselors in some countries had to work from home without systems that allowed it.
Values first: partnership, privacy and data ownership
Before describing the product, Luo sets out the values that guide its development. Partnership means working with the helplines and the wider NGO community, which is why the software is open source and intended for the whole crisis response movement. Privacy, security and reliability matter because helplines handle extremely sensitive information about children. Data ownership is explicit: "As a software provider, we are very clear that the helplines own their own data and they are the decision makers in how their data is being used." (3:59)
With those values in place, the team built a cloud-based, omnichannel platform. Counselors can handle voice calls, Facebook Messenger, WhatsApp and web chat in one interface, with efficiency tools that save time on data collection and built-in reporting on both operations, such as wait times, and the issues affecting children. Each helpline gets its own customized instance in its preferred language.
The hard part: one product, many realities
Luo is candid about the challenges. Helplines in the US and Europe, with stricter privacy rules, tend to run anonymous services where calls are one and done, while helplines in Africa and Asia often do hands-on case management and follow-up. Existing systems are tied to scheduling, payroll or government integrations. Budgets depend on donors, technical fluency varies down to individual counselors, channel priorities differ (WhatsApp is huge in some countries and minimal in others), and every country has its own legal requirements for children's data.
Then comes scale. The question becomes how to support 5, 10 or 50 helplines without duplicated, one-off development for each. Remote work compounded it all, with six to nine hour time differences, unreliable internet and no chance to meet users in person.
Beta testing and infrastructure as code
Tech Matters answered with practices that still guide its growth. An open call to the network produced a beta group of ten helplines chosen to represent its diversity in region, existing technology and requirements. Roughly every six weeks the team shipped new features with documentation and training guides, followed by surveys on ease of use and usefulness. Those surveys revealed how each helpline operates and surfaced feature ideas the team had not considered.
On the engineering side, the team adopted infrastructure as code. The core platform is a generic framework, and each helpline's customization lives in simple JSON files. Adding a required field or changing a drop-down option no longer needs an engineer. As Luo puts it: "This means that configuration and customization can be done by and defined by non-software engineers." (10:19) The hope is that helpline administrators will eventually make these changes themselves.
The team also leans on established tools. Aselo is built on Twilio Flex, in close partnership with Twilio, and uses Okta for single sign-on and authentication. Luo notes that using industry tools where the team is not expert keeps it aligned with best practice and opens partnerships with major tech players.
Relationships as a product practice
The first launches, with national child helplines in Zambia and South Africa, were planned just before the pandemic. When travel bans hit, Tech Matters hired a full-time team member in South Africa, Humera, to focus on those deployments. She later visited Childline Zambia, answered questions, gathered feedback on new features and ran usability studies. Luo sees this as the foundation of the partnership: "Um, and probably most importantly of all, her visit really laid a foundation of trust and improved communication across both of our teams." (13:50)
Looking ahead, Luo describes two helplines live, many demos, and a goal of launching 10 to 15 more in the following year. The team will keep the software open source so any crisis response organization running a contact center can use it, and is working on pricing that keeps core features affordable for small budgets. "We have made a decade long commitment, if not longer, uh, to being a technology partner for the helpline movement." (15:04)
Watch the talk
Creating Shared Platforms for the Social Sector, Dee Luo, 17 minutes: https://www.womentech.net/video/creating-shared-platforms-social-sector
About the speaker
Dee Luo is a Product Manager at Tech Matters, a Silicon Valley based nonprofit that uses technology to support social sector innovators and advance large-scale positive social change. She previously built SaaS business software at Yext and worked on pro bono projects for international social enterprises as a fellow of the MovingWorlds Institute.
Questions this talk answers
Why did child helplines need a shared contact center platform?
How can one platform serve helplines with very different requirements?
How did Tech Matters involve users in building the product?
How did the team handle launching software during the pandemic?
How does Tech Matters handle helpline data?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Infrastructure as code
Minimum viable product
Beta program
Resources mentioned
Aselo
Twilio Flex
Okta
Cite this talk
Dee Luo. "Creating Shared Platforms for the Social Sector." WomenTech Network, 2021. https://www.womentech.net/video/creating-shared-platforms-social-sector