Platform console
every view of this page is written to the audit logSign out
| Customer | Paid services | Manual | Declaration | Training | FRAT | Status | Next date | MRR | One-time |
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
Loading…
| Operator | Daily today? | To-do | Bounced | Not signed in | Invites open | Recipients |
|---|
| Operator | Plan | Billing | Users | Reports | Readiness | Last login | What we owe them |
|---|
Readiness is a coarse signal — one quarter for each Part 5 component showing any activity. It is useful for spotting an operator who has stalled, not for telling them they are compliant. Figures on this page are read live from the database.
Loading…
| Date | First email | Follow-up 1 | Follow-up 2 | Errors | Visits /go | Visits /checklist |
|---|
| # | Operator | State | Tier | First email | Follow-up 1 | Follow-up 2 | Result | Next |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||
| When | Operator | Touch | Result |
|---|
The campaign runs on James's laptop (sms-targets/send_outreach.py). After every batch, build_tracker.py checks the james@skylinevegas.com mailbox for bounces and for mail from a contacted operator's domain, then copies the results here and to the Desktop tracker. Reply = a person wrote back; Opt-out = asked not to be contacted; Auto-reply = out-of-office or ticket acknowledgment. Visits are anonymous page views, not tied to an operator.
Grouped by problem, not by event. You are emailed once when something new appears, and again if a resolved problem comes back — never per occurrence. Platform administrators only.