Start with the work, not the people
The easiest way to organise message is to follow the work your organisation already does. Programme inboxes should mirror service lines, funder reporting streams and campaign cycles, rather than each staff member's personal workload. That way, when someone is on leave, in a field visit, or stuck in traffic on the N1, the work still keeps moving.
For a non-profit in South Africa, that usually means one inbox for enquiries, one for programme delivery, one for fundraising or donor liaison, and one for finance or admin. Smaller teams may start with fewer inboxes, but the rule stays the same: if a message needs a repeatable action, it deserves a dedicated address and a defined owner.
- Use function-based inboxes, not personal names, for shared work.
- Keep each inbox tied to one clear purpose.
- Write down who checks it, when it is checked and what gets escalated.
Build inboxes around campaigns and service lines
Campaigns often generate bursts of message from volunteers, beneficiaries, schools, clinics, suppliers and donors. If those messages all go into one general mailbox, it becomes hard to tell which query belongs to which campaign. A better structure is to create campaign-specific inboxes for time-bound work, then close them once the campaign ends or roll them into a programme inbox if the work continues.
Service delivery inboxes are different. They need to stay active through the year because they support recurring tasks such as bookings, referrals, case follow-up and appointment changes. In practice, that means one inbox for the service itself and a separate inbox for temporary campaigns, so staff do not spend half the week sorting mail instead of helping people.
- Use campaign inboxes for event-driven activity.
- Use programme inboxes for ongoing delivery and follow-up.
- Archive old campaigns instead of letting them clutter current work.
Separate external queries from internal coordination
One of the most useful habits is to keep external communication apart from internal chatter. Staff often want to reply from whatever inbox is open, but that creates confusion. A beneficiary should not receive a message that was meant for a colleague, and a funder should not be copied into a thread about rotas or transport.
For this reason, shared inboxes work best when they are paired with clear rules. Use one mailbox for incoming public queries and another for internal handover notes, approvals or team follow-up. Calendar sharing can also reduce back-and-forth, especially when the team is spread between Cape Town, Johannesburg and Durban and people are working across time-sensitive visits.
- Keep public communication in shared programme inboxes.
- Use internal notes and calendar events for coordination.
- Set a short daily check-in time so mail does not pile up overnight.
Assign ownership and backup cover
Every inbox needs a name on paper, even if several people can access it. Without ownership, messages sit unanswered because each person assumes someone else is dealing with them. Ownership does not have to mean one person answers every message. It means one person is responsible for monitoring, triaging and making sure nothing falls through the cracks.
Set clear handling rules for each inbox. A service-delivery mailbox might need frequent checking, while a donor relations mailbox may follow a different routine. Then name a backup person for leave periods, power cuts or load-shedding windows when a remote team member cannot work through messages. In Observatory, Cape Town, that kind of planning matters because even good systems can be interrupted by internet issues or municipal delays.
- Nominate one owner per inbox.
- Define a backup for leave, illness and outages.
- Write simple service times for each mailbox.
Make the structure easy for staff and beneficiaries to use
A good inbox structure is only useful if people can understand it. Long or clever mailbox names usually confuse everyone. Keep addresses plain and practical, and make sure the labels are easy to remember across branches and sites. If a mailbox is meant for training requests, say so. If it is for programme referrals, say so. Clear names save time and reduce errors.
This also helps when you onboard new staff or volunteers. A short training session can cover which inbox receives what, how to move messages between teams, and when to escalate a case. In non-profit work, staff changes are common, so the more visible the structure is, the easier it is to keep continuity. A clean setup also supports compliance, especially where service records or donor correspondence need to be retained for audits.
- Use simple mailbox names that describe the function.
- Keep naming consistent across all programmes.
- Train staff on the process, not just the technology.
Use local examples to test the setup before rollout
Before you roll out new programme inboxes across the organisation, test them on one team or one campaign. For example, a Cape Town non-profit running community training could set up one inbox for registrations, one for venue coordination and one for participant support. That lets the team see whether messages are landing in the right place and whether someone can cover the inbox during travel or at peak times.
A Johannesburg or Pretoria office may need stronger handover rules if staff are often in meetings or on the road. A Durban branch may need extra planning around mobile access, because some team members rely on phones more than laptops. The point is not to copy one model everywhere. It is to build a structure that matches how the organisation actually works, then refine it as the team settles into it.
Once the inbox structure is stable, it becomes easier to add shared calendars, document spaces and mobile access without creating more admin. The result is not just tidier mail, but better follow-through on the work that matters.
