Customer channels
WhatsApp, student app, teacher app and email each receive messages through their own integration.
ONE PLACE TO SEE THE SYSTEM
Control Center
Service health, capacity and recovery for your team.
Checking your admin session…
Live capacity
Waiting for a measurement
Services
Health checks every 15 secondsInbox experience
Waiting for browser reportsBest-effort reports from updated desktop browsers over the last 24 hours. P95 values are bucket upper bounds; the final bucket includes all durations above 60 seconds. Input-delay reports cover browser events lasting at least 16 ms. No messages, customer identifiers or agent names are collected. Missing reports do not confirm good performance.
Message processing
Waiting work, including scheduled retriesUnconfirmed native text sends need review; they are not automatically sent again. An accepted send does not confirm delivery to the recipient.
Retrying is part of Waiting, not an extra queue. These totals include older files and do not measure Inbox speed. An empty media queue does not mean every file was recovered. Unavailable files and unverified outcomes remain visible after retries finish.
Recorded measurements
Collecting historyLast 24 hours of available samples. Gaps and traffic between samples are not measured. Health-probe timing does not measure message delivery.
From a customer to your team
Current system mapChannel engines
S2 handles its WhatsApp session. Leads7, Students7 and Teachers7 own their channels and expose their messages through APIs.
S2 workspace
Your team sees the conversation, customer context and unread activity in one inbox.
A reply goes to its owner
S2 routes a reply to the engine responsible for that channel. The provider then supplies its own delivery status.
Markaz & academic systems
Markaz owns customer identity. Teachers7 and Students7 own academic data. A shared family phone can refer to several people.
Files & recordings
Media storage and processing support the message. Their health must be checked independently of the inbox page.
Saved before the inbox updates
A native WhatsApp message enters a durable incoming journal first. The inbox then updates; media downloads run separately.
A saved send receipt
The send request keeps one identity through retries. An unconfirmed result needs review. Acceptance and delivery remain separate states.
A separate read process
Cold group and student calculations run in a bounded process that reads the mirrors. It has no WhatsApp session and cannot send messages.
Scheduled backups
Completion is different from restorationLocal S2 data
The first automatic full backup was downloaded from independent storage and restored away from the running application: all 77,472 files and 7 databases passed verification, including both message journals. A separate five-minute journal backup was also restored.
Full backups run daily; message journals run every five minutes. Copies have seven-day object retention. Files and databases are captured separately, not as one atomic recovery point.
Markaz database & Teachers7 files
The full Markaz database was restored in isolation: 153 tables and 2,130,676 rows matched. All 87,435 Markaz/Leads7 files and 1,471 Teachers7 files were encrypted off-host, decrypted and checked.
Recovery snapshots, not live replication. Managed Supabase services were not started in the restore drill.
Full platform recovery
- Remaining external services and finer recovery targets
- Recovery keys held by the organization
- Recurring restore drills and recovery-key custody
- Tested replacement of a failed server