Built once, adapted for crisis: ParentText in Palestine, Ukraine, Georgia and Afghanistan

In crises, parents carry a double load: keeping their children safe and helping them cope, often while living through the same fear and disruption themselves. This month, ParentText Crisis went live for World Vision families in Ukraine and Georgia (2 December) and in Afghanistan (8 December), with Romania to follow in January. Behind these launches is a year of work that began in Palestine and tested every part of how we build.

Where the crisis version comes from

ParentText Crisis began in 2024 through Parenting for Lifelong Health’s (PLH) Africa 5 Nations project. Parents from Ukraine, the Democratic Republic of Congo and Rwanda, all of whom had lived through crises with their children, helped design it. It delivers ten short, practical parenting tips approved by UNICEF, UNHCR and WHO, in a format meant to be quick and cheap for any country to adapt.

Palestine: designing for real constraints

The first full adaptation was for Palestine, and almost nothing about it was routine.

Language. Arabic was the first right-to-left language in ParentText, and it caused no major technical problems.

Connectivity. Internet access can disappear without warning. At the end of each day’s session, parents can open the next day’s content straight away instead of waiting for a message that may never arrive.

Delivery. Early in the year, changes to the WhatsApp fee waiver meant UNICEF could no longer distribute the chatbot. Local partner organisations took over dissemination, and we built a system to give each organisation its own quota within an overall cap of 5,000 users, with a waiting list for anyone beyond it.

Trust. After launch in June, the country prefix of the WhatsApp number put some users off, so we added a second line.

The deployment also included a research component, with surveys embedded in the experience, an opt-out, and none offered to under-16s. We built it on the survey system we developed for the South Africa trial, so the research tools moved with us.

From one deployment to three

When World Vision asked for ParentText Crisis in three new contexts, we did not copy the Palestine version three times. We separated what should stay common from what is specific to a country, and turned the common part into Crisis Sample 2.0: a shared base made of the global crisis content, the Palestine features and the research component, with an improved survey structure based on what Palestine taught us.

Each country team received the same standardised data lists, with the parts that needed local adaptation highlighted. Local partners rewrote, translated (through Crowdin) and tested the content in their own languages, while the core stayed common. Where contexts differed, the system allowed for it: Ukraine and Georgia share a deployment but ask different onboarding questions, and Romania collects location data that the others do not.

Each version carries its own local name. Батьківська опора (Batkivska Opora, “Parental Support”) is for displaced and host families inside Ukraine and for Ukrainian refugee parents in Georgia. نور والدین (“Parents’ Light”) reaches Afghan families recovering from the 2023 earthquake, and Busola Părintelui (“Parent’s Compass”) will reach rural families in Romania. World Vision aims to reach 7,000 caregivers across the four countries through this pilot, using the messaging apps families already have, such as WhatsApp, Viber and Telegram.

This is the global-local balance we have been working towards since ParentText began. Local teams own what makes their version theirs. Improvements to the core, such as a better survey, a fixed bug or a new feature, are made once and reach everyone.

Owning the infrastructure

Romania is the first ParentText deployment inside the European Union, and GDPR applies in full. The commercial RapidPro hosting we had relied on until now has servers only in the United States. Rather than limit what the programme could do, we built our own hosting capability.

We now run RapidPro on cloud servers we manage, packaged in Docker containers so that a new instance can be set up reproducibly. The World Vision deployments run on servers in Germany. A second instance, for the SWIFT study in South Africa, is hosted in South Africa, and setting it up took half a day. For the EU work we started a data protection impact assessment, built reusable tools for retrieving and deleting user data, and now handle privacy requests directly. World Vision’s Trusted Partner assessment rated our residual risk as low.

This changes our role. We are no longer only the team that builds the chatbot. We can now also host it, process its data responsibly, and keep that data in the jurisdiction where the users live. For humanitarian partners, where the data sits and who controls it are not technical details.

What comes next

Crisis Sample 2.0 now exists, so the next crisis deployment will not start from scratch, or even from Palestine. It will start from a tested base, built from real launches, that a local team can adapt far faster. In emergency response, that speed matters.

Authors

Tags

Public Health · Socio-Technical Innovation · IDEMS Inclusive Innovation · Contextualised Variants