RISE is growing. This is the way forward.
This page explains what is changing inside RISE, what is staying the same, and how our systems will support the people doing the work.
What is not changing
Survivor support remains human led. Intake remains careful and handled with responsibility. This shift is about reducing volunteer admin and creating better structure around the work.
Founder note
From a founder perspective, this is necessary. The current manual load cannot be sustained by two or three people and a small group anymore. We need to move time away from admin and back into workshops, domestic violence training, growth, and impact.
Why this change is happening
RISE has grown. We are serving more people, managing more cases, and carrying more admin than a small volunteer team can sustain manually. This change is about capacity, structure, and support.
Current pressure
Too much of the work depends on manual forwarding, assigning, checking, and following up. That takes time and energy away from meaningful support.
What we are fixing
We are building systems for task tracking, ticketing, onboarding, workflow visibility, and secure internal communication.
What stays human
Survivors are not being handed over to machines. People still do the work. The systems support the people doing it.
What is changing and what is not
This shift applies to volunteers, systems, and internal processes. It does not change the heart of the work.
What is changing
- How forms are received and processed
- How volunteers are onboarded
- How tasks are assigned and tracked
- How management sees progress and workload
- How we work within one secure RISE email environment
What is not changing
- Survivor intake remains human led
- Support remains trauma informed and careful
- POPIA obligations remain in place
- Judgment, care, and decision making remain with people
- Confidentiality still matters at every stage
The two systems supporting this shift
One tool helps systems speak to each other. The other tracks work clearly from start to finish.
Zapier
Zapier is a connector. It links systems and tells them what to do automatically.
Simple idea: if something happens, then something else happens.
- If a form is submitted, the right team can be notified
- If a volunteer applies, onboarding emails and training links can be sent
- If a task is overdue, a reminder can be triggered
Zendesk
Zendesk is a ticket system. It turns incoming matters into trackable tickets with a reference number.
Simple idea: a person reaches out, a ticket opens, the matter is assigned, tracked, and followed through.
- Each matter can be seen in one place
- The right person can be assigned quickly
- Management can see status, ownership, and progress
Important clarification on privacy
These systems support notifications, task tracking, workflow, and visibility. They do not replace survivor care. They do not remove our legal and ethical responsibilities. Sensitive information must remain where it belongs inside the secure RISE environment.
Interactive workflow examples
Open each example to see how this can work in practice for counselling, legal, volunteer onboarding, and management.
Counselling workflow example Click to open
A survivor completes an intake form.
- A confirmation email can be sent automatically
- An internal task or ticket can be created
- Lisa and the counselling team can be notified
- The intake can be assigned to an available counsellor or intake volunteer
- The system can track whether contact has been made
- If no action is taken within a set time, a reminder can be triggered
What stays human: survivor care, decision making, and the actual support process.
Legal workflow example Click to open
A legal request form is submitted.
- A legal ticket can be created and given a reference number
- Jay or the legal team can be notified immediately
- Supporting documents can be linked in one place
- Status updates can be tracked from intake to opinion to closure
- Deadlines can trigger reminders
- Management can see where the matter sits without searching through inboxes
What stays human: case judgment, survivor communication, legal thinking, and final review.
Volunteer onboarding and training example Click to open
A new volunteer completes an application form.
- A welcome email can be sent automatically
- Training links and onboarding documents can be shared immediately
- Management can be alerted that a new volunteer has joined
- A simple checklist can track progress
- The system can show who still needs to complete each step
This reduces repetition and makes onboarding more consistent for everyone.
Management visibility example Click to open
From a management perspective, this creates a live overview of what is happening inside RISE.
- How many intakes have come in
- Who is assigned to each matter
- What is still pending
- What has been completed
- Where delays are happening
This removes dependency on personal inboxes and helps protect continuity.
Step by step system logic
These flows show how the new structure can reduce manual work while keeping the support itself human.
If a counselling intake is submitted
The intake enters the system through the correct channel.
The matter is recorded and visible from the start.
Lisa and the relevant team members can see a new intake is ready.
The intake can be given to the right person without manual forwarding.
Management can see whether contact was made and what still needs to happen.
If a volunteer applies
The volunteer enters the process through the correct form.
Training links and onboarding information can be sent automatically.
The team can see who has joined and what stage they are at.
The system can show what has been completed and what still needs attention.
The process becomes shared, visible, and easier to manage.
Quick understanding cards
Click any card to turn it.
Why security matters
We are building infrastructure that carries real responsibility. The people with access to these systems need secured accounts.
Why RISE emails matter
Everyone operating inside the system needs to work through the RISE workspace and domain. That creates better control, accountability, and continuity.
Why two step verification matters
If someone gets a password, they should still not be able to access the account. Two step verification adds a second layer of protection and helps protect RISE, the account holder, and the people we serve.
The direction of travel
This is not about making the work cold or distant. It is about protecting the people doing the work, reducing unnecessary pressure, and creating a stable system that can support RISE as it grows.
Two step verification for RISE management
As part of this shift, management accounts must now be secured properly. This is not about making things difficult. It is about protecting RISE, your account, and the people we serve.
Why this matters
We are now working inside a secure RISE workspace with email accounts, admin access, and internal systems that carry real responsibility.
If someone gets access to your password, they can get into your account. Two step verification adds a second layer of security, so a password alone is not enough.
This protects RISE, protects you, and protects the integrity of the work.
Important note
This is only required for the RISE management accounts that need access to protected systems and settings. It is part of building a secure structure as RISE grows.
Please do not panic. The setup is simple, it takes only a few minutes, and once done, it becomes part of your normal login process.
What two step verification means
When you log into your RISE email, you will still use your password as normal. After that, Google will ask for a second code from your phone. That code changes often and helps make sure nobody can access your account without your device.
What changes when I log in Open
You type in your password as usual.
Then Google asks for a code.
You open the Google Authenticator app on your phone and type in the 6 digit code shown there.
That is all.
Why this is safer Open
If someone gets your password, they still cannot get into your account without the code on your phone.
That extra step is what protects the account.
Does this affect survivors Open
No. This is a security step for management access inside the RISE workspace. It is about protecting internal systems and sensitive operational access.
How to set it up
Please follow these steps carefully. It should take less than five minutes.
Step 1
Download Google Authenticator on your phone.
iPhone: Open the App Store, search Google Authenticator, and download it.
Android: Open the Play Store, search Google Authenticator, and download it.
Step 2
Go to your Google account settings.
Open myaccount.google.com
Log in with your RISE email address and password.
After logging in, click on Security.
Scroll down to How you sign in to Google.
Click 2 Step Verification, then click Get started.
When Google asks how you want to verify, choose Authenticator app.
Open Google Authenticator, tap the plus sign, then choose to scan a QR code.
Point your phone camera at the QR code on your screen.
The app will show a 6 digit number. Type that into the computer when asked.
Click Turn on. Your account is now protected.
Quick questions
These are the concerns most people usually have.
What if I get a fright when Google asks for a code Open
That is normal. It just means the extra security is working. Open the app on your phone, get the code, type it in, and continue.
Will I have to do this every single time Open
You may be asked more often on a new device or if Google thinks a login needs to be verified. On trusted devices, it may not ask every single time.
What if I do not understand the steps Open
Ask. We will walk through it with you. You are not expected to figure it out alone.
Why are we doing this now Open
Because RISE is moving into a more secure and structured system. The people with access to management tools and settings must have protected accounts.