Installations Analytics
Router Configuration Sessions Started / Week
Budget Used / Week (Agent + Scan)
RTI Conversion Funnel
Installs started / week
Human-login handover conversion · all-time since instrumentation
Weekly Failure Analysis · AI classification, per selected week
Downloads
New downloads / month · first download per IP — updates excluded
Install downloads
| When | OS | Version | Location | Timezone | Language | IP | Browser | Referer | |
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
Incidents · Airbag alerts
Airbag alerts ([Airbag] {reason} @…) across every incident type — pick one from the Incident dropdown to narrow it down. SL1-visible = an alert that is born directly in new/open (e.g. no app client to engage) or escalates out of pending into new/open — the signal we want to drive down. Bucketed by the day or week the event happened (UTC; weeks are Monday-anchored).
RTI installations
| Client ID | Started | Created | Store | Status | Online | Last seen | Notes | Budget |
|---|
Router Knowledge Base
| Router Model | Brand | UI Variant | Usage | Updates | Success Rate | Last Updated | Actions |
|---|
Incidents
| Client ID | Server name | Type | Incident type | Status | Created▼ | Last update | Resolved | ||
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
DVR Knowledge Base
| Model | Brand | UI Variant | Usage | Updates | Success Rate | Last Updated | Actions |
|---|
RTF incidents
| Server | Organization | Code | Status | Created | Alert ticket |
|---|---|---|---|---|---|
| Loading… | |||||
Find a store
Enter store ID, CRM company ID, server, name, phone number or address…
Resellers
Choose the WhatsApp pool you want to use.
Pick a sales tool below
Administration
Manage who can sign in and their access level.
Provision a reseller user
Settings
WhatsApp Web sessions
Twenty persistent sessions across five WhatsApp pools. Each number remains available if either Fly machine is unavailable.
History
All audited Store operations performed through Cockpit, across every user and environment. New actions appear while they are still running.
Incidents
— · Environment: —New ticket subject — set on the customer ticket at creation
"Your setup is back!" email — public reply when the alert is solved
cascade-solve-incidents action.
The ticket is set to solved at the same time, which also stops the reminders cadence.
No placeholders — keep it short and reassuring.
"It's down again" email — public reply when a solved incident re-flaps
cascade-reopen-incidents action.
The ticket is set back to open at the same time, and the next "Your setup is back!" email is re-armed for this new cycle.
Debounced: at most one public "down again" per incident per SD_REFLAP_COOLDOWN_HOURS window (re-flaps inside the window reopen the ticket silently).
No placeholders — keep it short and factual.
Auto follow-up flow — customer reminder cadence
Public comments — Fast Pace — daily reminders while the customer hasn't signaled their issue or attempted recovery
Public comments — Slow Pace — every 3 days, when the customer reported the issue is on their side
Global exclusion tags — if a ticket has any of these tags, all reminders skip
Router sticker scans
| When | Case | Outcome | Brand / IP | Fields | Confidence | Cost | Duration | Token · IP hash | Image |
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
Admin login & password values from sticker photos are never stored — we only keep brand, IP, presence flags, confidence and cost so you can monitor quality and abuse.