What the Durban team needed
The project came from a shelter service in Durban that was dealing with a steady flow of enquiries from social workers, donors, community members and partner organisations. Messages were arriving in personal inboxes, calendars were kept in separate places, and files were being shared through our contact form attachments that were easy to lose. The brief was simple in principle but important in practice: create one shared communication setup that could be managed by a small team, stay affordable for a non-profit budget, and keep working during load-shedding and after staff changes.
They also needed something that could support shift work. When one person was off site or on leave, the next person had to see the same intake messages, the same calendar bookings and the same documents without hunting through old threads. That made reliability and clear access control the top priorities.
Constraints we had to work around
The shelter team did not want a complicated rollout. They needed a low-disruption changeover because front-line work could not stop for a long training period. A second constraint was data discipline. Intake notes, referral documents and contact details had to be handled carefully, with clear folder structures and limited admin access. As with many service organisations, there were a mix of phones, older laptops and a few staff members who worked mostly on mobile devices.
Durban conditions also matter. Coastal humidity can affect ageing equipment and mobile devices, and a power interruption can interrupt syncing if the setup is not planned properly. So we built the migration plan around stable mailbox moves, staged calendar setup and short training sessions that could be repeated for each group of users. No fancy process, just something the team could keep using day after day.
- Mixed devices: Android phones, iPhones and Windows laptops
- Need for simple permission control across office and field staff
- Short rollout window so client service could continue
What we supplied and configured
We supplied hosted mailboxes for the core team, set up shared calendars for intake and follow-up scheduling, and created document spaces for referrals, case notes and internal forms. The mailbox structure was planned around roles rather than individual preferences, so the admin inbox, intake inbox and general enquiries inbox could be monitored by more than one person. That reduced the risk of missed messages when a staff member was away or busy with a visit.
We also handled domain linking, mailbox setup, calendar setup, document space setup, contact imports and mobile device setup. Where needed, we gave the team guidance on how to use shared folders without creating duplicate files. A careful admin handover was included so the shelter could manage common tasks on its own, like adding a new user, resetting access or assigning calendar permissions.
- Shared mailboxes for intake, admin and general enquiries
- Central calendars for roster planning and appointments
- Document spaces for referral letters, forms and working files
Migration and training in a four week roll-out
The work was completed over four weeks. Week one covered discovery, account planning and mailbox structure. Week two was used for migration preparation, contact imports and testing calendar sharing with a small pilot group. Week three handled the main mail migration and mobile setup for the full team. Week four was training, go live support and a final security review to make sure the right people had access to the right information.
Training was kept practical. We showed the team how to file messages, use shared calendars, find older documents and flag items that needed follow up. We also covered basic hygiene such as password control, device lock settings and what to do if a phone was lost. A few staff members had never used shared collaboration tools before, so we kept the pace steady and repeated the key steps twice where needed. That extra bit of time made a big differnce.
What changed after go live
After go live, the shelter team had one place to manage enquiries instead of several private inboxes. That meant fewer missed messages and less time spent asking who had seen a particular message. Shared calendars also made shift planning cleaner because the team could see intake slots, internal meetings and follow-up times in one view. Document collaboration improved too, especially when several staff members needed to work on the same referral or donor response.
The biggest gain was consistency. New volunteers or staff could be added without starting from scratch, and departing users no longer took important information with them. For a shelter service, that matters because every delayed reply can affect a placement, a transport arrangement or a support referral. The setup gave them a steadier daily rhythm, even on days when the office was stretched.
- Less time lost to searching old message threads
- Better visibility on intake and follow-up appointments
- Easier handover between shifts and staff changes
What we would do again for a similar shelter
If we were starting the same kind of project again, we would keep the same approach: map the daily workflow first, then build the mailbox and calendar structure around that workflow. For a shelter team, the admin load must stay light. It helps to keep the number of shared mailboxes sensible, use clear naming, and avoid overcomplicating permissions. We would also keep training close to go live so the team can ask questions while the setup is still fresh.
For organisations operating in Durban, Cape Town or Johannesburg, we would again recommend testing on the devices people actually use, not just on office computers. It saves time later. We would also keep a short security review in the plan, because non-profits often handle personal information and need a clean paper trail. In short, we’d build for real working conditions, not ideal ones.
That practical method is what lets a small team get more value from their message and collaboration tools without stretching the budget.
Key facts
| Client type | Durban shelter and support team |
|---|---|
| Project timeline | 4 weeks |
| Core services | Domain Linking, Mailbox Setup, Calendar Setup, Document Space Setup |
| Data work | Mail Migration, Contact Imports, Admin Handover |
| Support included | Team Training, Go Live Support, Ongoing Admin Help |
| Service areas | Durban, Cape Town, Johannesburg, Pretoria and Bloemfontein |
