Field teams and beneficiaries: messaging where the connection is bad

Three constraints change everything about messaging in field work: bandwidth, shared handsets, and data about people who are vulnerable. Each one makes an ordinary practice inappropriate.

Bandwidth

Assume every message may arrive hours late, out of order, or not at all until the handset finds signal. The practical consequences:

• Anything time-critical needs an acknowledgement. A delivered receipt is not confirmation that a person acted - see what statuses mean.
• Keep media small. A field worker on a shared bundle will not download a twenty megabyte video, and the instruction inside it does not reach them.
• Text beats everything. It arrives when nothing else will.
• Expect duplicates. People resend when they see one tick, and your systems should not treat that as two reports.

Shared handsets

Data about vulnerable people

An inbox in this context can accumulate health information, immigration status, details about children, and accounts of violence. It arrives unasked, in a channel that was set up for coordination.

1. Decide who can read the inbox, deliberately and narrowly - and be able to show it.
2. Set a short retention period and enforce it in a job. See retention.
3. Do not copy sensitive detail into tags or fields. One copy is unavoidable; five is a decision.
4. Never let an automated send reach an open case conversation.
5. Keep it on organisation numbers, not on staff phones that leave with staff.

What works well

Coordination between field teams, distribution announcements, appointment and clinic reminders, and structured reporting from the field - photographs of a site, a count, a form. All of it benefits from a record the organisation keeps rather than one that lives on individual handsets.