Top primary zones — use this to decide where to place battery-swap stations.
Preferred subscription on registration.
Which apps riders work on.
New waiting-list sign-ups per day.
Helps size battery range and swap frequency per rider.
| Rider | WhatsApp actions | Platform | Primary zone | Plan | Daily km | Insurance | Status | Joined | Actions |
|---|
Top referrers and the discount tier they've reached.
Applied automatically as referrals are verified.
| Referrer | Referrer phone | New driver | New driver phone | Date |
|---|
| From | Type | Message | Status | Received |
|---|
The public homepage counter now loads from the live Supabase leads table.
Tip: this is now only a fallback. The live count comes from Supabase.
This console now uses Supabase Auth. Admin users must be created inside Supabase under Authentication → Users.
Recommended first admin: admin@flatgo.co.za. Enable MFA in Supabase before giving access to other users.
Export everything (riders, referrals, messages, counter) to a JSON file, or restore from a previous backup.
Populate the dashboard with sample riders, referrals and messages so you can preview it or show stakeholders.
The public website and this console are prepared for Supabase. Once you replace the placeholder Supabase values, signups, referrals and messages will load centrally from the database.
For payments, connect PayFast, Yoco, Ozow or Peach Payments after signup capture is working reliably.