Communicating with displaced communities at scale means solving a problem that most communication platforms were not designed for: reaching people across dozens of countries, in multiple languages, through channels that vary by context, some recipients on smartphones in urban settings, others on feature phones in camps with no reliable data access, and maintaining that reach as the population moves. The Norwegian Refugee Council's communication infrastructure is one of the most operationally complex humanitarian deployments in the field today.
When the Norwegian Refugee Council needed to maintain contact with displaced communities during COVID-19 lockdowns, the challenge was not simply that in-person services had to move online. It was that the populations they serve do not live in a single country, communicate through a single channel, or need the same kind of information at the same time. NRC's response to that challenge, the Digital Community Hubs initiative, has since become one of the more instructive examples of what humanitarian communication infrastructure can look like when it is built for operational complexity rather than a single use case.
In Uganda, field teams were coordinating WASH program delivery. In Venezuela, families needed information about available aid. In Kenya, beneficiaries were receiving cash voucher distributions. In Palestine, communities were lodging complaints and feedback on services received. Each situation demanded a different kind of communication. Some required a conversation. Some required a broadcast. Some required a structured intake process. Some required a way to follow up after aid was delivered.
A messaging platform that does one of those things well does not automatically do all of them well. What NRC built is a communication infrastructure that handles all of them, across more than 20 countries, from a single platform.
Organizations that communicate with displaced communities face a structural problem that most enterprise software is not designed to solve.
The populations they serve are mobile. The geographies they operate in are diverse. The connectivity infrastructure varies by country, by region, and sometimes by crisis phase. A field team coordinating in urban Kenya is operating in a fundamentally different environment from a team working in a conflict-affected area where local SIM-based connectivity is the only reliable option. A beneficiary receiving a cash voucher distribution needs a different kind of interaction than a community member filing a complaint about services received.
Most communication tools are built for a single use case. A broadcast platform handles outbound notifications. A survey tool collects structured responses. A helpline manages incoming calls. Running all of these simultaneously, across dozens of countries, through a patchwork of separate tools, creates exactly the kind of operational complexity that slows humanitarian response when speed matters most.
The alternative is building communication infrastructure where each of these use cases runs through the same system, configured differently for each context, managed by a small team without requiring technical expertise in every country office.
That is what NRC set out to build.
NRC's Digital Community Hubs deployment spans several distinct communication workflows. Each one serves a different operational purpose.
Information sharing is the most foundational. NRC country teams send updates to beneficiaries about available services, program changes, and access to resources. At scale, this requires the ability to reach large populations quickly, in multiple languages, through whatever channel is most reliable in that geography.
Complaints and feedback mechanisms are structurally different. A beneficiary who wants to report a service issue or ask a question needs a two-way channel, not a broadcast. The system needs to receive the message, route it appropriately, and in many cases trigger a follow-up response. This is not a notification workflow. It is a case management workflow with a messaging layer.
WASH program communication involves coordination across field teams and beneficiary communities simultaneously. Water, sanitation, and hygiene programs depend on communities understanding what services are available and how to access them, and on field workers being able to confirm delivery and report issues. That requires both outbound and inbound messaging to function reliably.
Cash voucher distribution is a high-stakes workflow where communication failures have direct consequences. Beneficiaries need to know when and where to collect aid. Field staff need to confirm receipt. Any breakdown in the communication chain delays assistance to people who may have no alternative.
Security updates to field staff in active crisis environments require immediate, confirmed delivery. A security alert that is not received is as useless as one that was never sent. This is where channel fallback logic matters most: if a WhatsApp message does not go through, the system routes to SMS. If SMS delivery is uncertain, voice confirmation becomes the failsafe.
Post-distribution monitoring closes the loop after aid has been delivered. NRC uses structured SMS and chat-based surveys to gather feedback from beneficiaries about the quality and adequacy of services received. The responses feed into program evaluation and inform future operations. For NGOs building this kind of feedback infrastructure, the design of the survey workflow matters as much as the channel it runs on.
In 2023, NRC reached over 465,000 people in less than a month using this infrastructure, with a team that would previously have required hundreds of additional staff to achieve similar reach. That figure is not a broadcast metric. It is the aggregate of multiple distinct workflows running simultaneously across countries, use cases, and channels.
The channel selection logic inside NRC's deployment reflects something that organizations new to multi-country communication often underestimate: connectivity is not uniform, and the channel that works in Nairobi does not reliably work in South Sudan or Venezuela.
In countries with strong mobile data penetration and a large smartphone-using beneficiary population, WhatsApp is an effective primary channel for two-way engagement. It supports rich media, location sharing, and structured conversation flows. For an organization gathering feedback through a post-distribution survey, it reduces friction for the beneficiary responding.
In countries where smartphone penetration is lower, or where mobile data connectivity is unreliable, SMS is the right default. It works on any handset, without data, and delivers reliably through local networks. Where international SMS aggregators do not cover a country adequately, local network integration through Android Gateway devices fills the gap, routing messages through local SIM connections.
Voice and interactive voice response add a layer for beneficiaries with limited literacy, or for situations where a text confirmation is insufficient and a spoken acknowledgment is required.
The practical consequence is that a humanitarian organization cannot design its communication system around a single channel and expect it to work everywhere. NRC's infrastructure handles the channel routing automatically, based on the contact's location and the workflow's requirements, without the program team having to manage it manually for each country.
As Anand Nair, Global Lead for NRC's Digital Community Hubs initiative, described it: "Telerivet powers the delivery of mobile messages and USSD requests for NRC, enabling seamless communication across multiple regions. Leveraging Telerivet's advanced integration techniques, NRC can connect with local mobile service providers and major connectivity platforms to send and receive bulk messages effortlessly."
The development sector is under significant budget pressure. For many international NGOs, the question of how to maintain program delivery with smaller teams and tighter resources is not abstract. It is the operational reality of 2025, 2026 and beyond.
The NRC model demonstrates something important: communication infrastructure is not a cost center that scales linearly with program size. A well-configured system can reach dramatically more people without proportionally more staff, because the workflows that previously required manual coordination are handled automatically.
The caveat is that this does not happen by default. It requires building the right infrastructure before it is urgently needed, and configuring it for each use case specifically rather than assuming a single tool does everything adequately.
Organizations evaluating their communication infrastructure for multi-country programs should be asking whether their current system handles all of their active use cases, or only some of them. The gap between "we have a messaging platform" and "we have a communication infrastructure" is where operational breakdowns tend to happen.
What communication channels do humanitarian organizations use to reach displaced populations? The channel mix depends on where the population is. In urban displacement settings with reasonable connectivity, WhatsApp and SMS are the primary channels. In camp settings or areas with limited data access, SMS and IVR (voice) are more reliable. USSD works where carriers support it and internet is unavailable. Most large humanitarian programs need all of these channels available simultaneously, with routing decisions made per recipient rather than per campaign.
What are the main communication challenges for NGOs working across multiple countries? The primary challenges are: maintaining consistent message delivery across different carrier environments and regulatory contexts in each country, handling multiple languages and dialects within a single program, managing opt-in and consent requirements that vary by country, and coordinating communication across field teams, beneficiaries, and partner organizations from a single platform. Organizations that run separate tools per country lose the ability to coordinate cross-border programs and create significant administrative overhead.
How do humanitarian organizations handle communication when beneficiaries move between countries? This is one of the hardest operational problems in refugee and displacement communication. The contact record needs to follow the beneficiary across country contexts, with the associated channel preference, language, and consent status intact. SMS is the most portable channel because it travels with the SIM card regardless of geography. WhatsApp-based communication breaks when a beneficiary changes their number or loses access to their account. Programs that depend on WhatsApp for primary contact often need SMS as the reliable fallback.
What is the role of two-way messaging in humanitarian programs? Two-way messaging is how humanitarian organizations create a feedback loop with the communities they serve: allowing beneficiaries to confirm receipt of aid, report service failures, ask questions, or request callbacks. It is also how field coordinators and community health workers communicate status back to the central team. Programs that operate one-way, broadcasting information without creating a response channel, miss the signal that their communication is or is not working until it is too late to act on it.
Telerivet works with humanitarian organizations, development sector programs, and NGOs across 150+ countries to build communication infrastructure that handles multiple workflows, channels, and geographies from a single platform. Explore our humanitarian and NGO solutions or Schedule a Conversation to discuss your program's requirements.