Home
# DialRush panel in the Command Center: scope
Status: scope only, nothing built. Sample counts, no real people, no keys.
## Answer
A DialRush panel is possible today as a read-only view (phase 1). Changes to DialRush (move a lead file, change a
playlist priority, toggle a playlist) are not possible yet: DialRush has no public admin API, and the bot has no code for
these three. They are phase 2 and need new bot work first.
## What DialRush exposes today
- **DialRush Claude connector (read only):** get_stats, get_report (including lead_status_penetration), search_call_logs,
get_call_transcript. Phone numbers are masked. It shows playlists only through report numbers, not as a list of
playlists with priority and on/off.
- **Nexus pull (website server, every 5 minutes):** lists "Complete Sale" calls, fetches transcripts, scrubs them, sends
them to the Call Review door; once a New York day it writes yesterday's Dialer Stats. Counts and code words only are
kept. The Call Review hub holds the graded sold calls.
- **The bot (jg-dialer-bot):** `dialrush map` and `dialrush inspect` are read-only (JG Admin only; every request that is
not a plain read is refused). Actions exist in the bot code behind `DIALER_BACKEND=dialrush`, which is off, and have
never been run on real DialRush: create, deactivate and reactivate users, move an agent's upline, assign a playlist,
rename, free seats.
- **No public DialRush admin API.** Anything beyond the connector goes through the bot driving the DialRush screens.
- **Command Center:** a preview build exists in the Ice look (dark, blue glow, Geist and JetBrains Mono, one blue main
button): `/mnt/project-files/command-center/build/preview/command-center.html`, with the plan in
`/mnt/project-files/command-center/PLAN.md`. It keeps projects and tasks in the browser with practice data only. It is
not in the `web/` code on this branch yet. The mock here uses its Ice tokens (dark only; the Ice build has no light
theme).
## Phase 1: read-only panel
Five tabs. All counts, no names. Each tab shows an "as of" time.
| Tab | Shows | Data source | Status today |
| --- | --- | --- | --- |
| Overview | one tile per tab below, plus last refresh | the other four | needs a snapshot (below) |
| Playlists | what the last inspect run showed: 7 active, 3 at priority 1, 4 at priority 5, all on; one of the priority 5 playlists is named VA (about 19,000 leads). Other per-playlist lead counts: TBD | bot `dialrush inspect` snapshot (My Playlists) | snapshot not built |
| Lead files | count of lead files and leads per file: TBD | connector `get_report` (lead_status_penetration), bot snapshot for file names | partly available |
| VA routing | the playlist named VA (priority 5, about 19,000 leads). VAs on it, calls and booked: TBD | bot snapshot (agent route) | snapshot not built |
| Call grading | graded calls today and counts per Call Review result: Approved, Needs human review, Denied, No sale | Call Review hub (already in Nexus) | available |
**Snapshot:** a bot job, started by a timer or a "Refresh" button, runs the read-only inspect route and posts counts to
the CRM, which stores the last result. Starting it needs a stored table in the database: not built, and out of this
scope (a database change goes to Opus and a Fable review, with SQL on a canvas).
**Who sees the admin view (phase 1), proposal:** 1st level (Julian) and Contracting team, counts only. MGA heading a
branch, GA, SA, Agent and VA do not see the admin view. The Agent view (below) is separate and is each person's own.
Matteo confirms this; question 1 below has the same answer.
**What could break:** the inspect route reads DialRush's screens, so a DialRush layout change breaks the snapshot; the
panel then shows "Not refreshed" with the last good time, never a guess. Playlist priority is only readable as
displayed text.
## Phase 2: actions, each needs Julian's typed yes in the CRM
Common rules: the CRM never calls DialRush itself. A request is made in the CRM, Julian types "yes" in a confirm sheet
(his own account, not a role stand-in), the CRM signs it and logs it, the bot runs it in a dry run first, reports what it
would change, applies only after the dry run matches, then reads the value back from DialRush to confirm it took. Each
result is logged (who asked, who approved, before and after counts, time). Nothing runs on real DialRush until Matteo
says.
**Decision for Julian, not decided:** today the rule is Julian's typed yes in the thread. Typing a yes inside the CRM
would be a new way to approve DialRush changes. Until Julian says so, the CRM sheet is only a request that waits for his
thread yes.
| Action | Data source | What starts it | Who may do it | What could break | Not built |
| --- | --- | --- | --- | --- | --- |
| Move a lead file (to another playlist or campaign) | bot, DialRush Content Library > Leads | a button on a Lead files row, then Julian's typed yes | Request: 1st level only. Approve: Julian. Nobody else | leads dialed by the wrong group; a move may be hard to reverse in DialRush | bot code, dry run, undo, the screen route (only read from `inspect`) |
| Change a playlist's priority (1 to 5) | bot, DialRush playlist screen | a button on a Playlists row, then typed yes | Request: 1st level. Approve: Julian | changes which leads dial first for every agent on it at once | bot code, dry run, reading the value back to confirm |
| Toggle a playlist on or off | bot, DialRush playlist screen | a button on a Playlists row, then typed yes | Request: 1st level. Approve: Julian | switching off stops all dialing on it mid-shift; a toggle clicked twice flips it back | bot code, dry run, "already in that state" check |
MGA heading a branch, GA, SA / Agent, Contracting team and VA never request or approve a phase 2 action. A button they
cannot use is not shown, and the CRM refuses the request on the server too.
## How the CRM would reach the bot (proposal, not built)
The bot already pulls "dialer jobs" from the website with a bearer secret (`/api/dialer/jobs`, claim then report back).
Reuse that pattern, adding a signature:
1. Julian types his yes; the CRM server writes one request row: action, target (a playlist or file code, no names),
requested by, approved by, time, a one-time id, an expiry of 10 minutes.
2. The CRM signs the request (HMAC with a shared key kept only in server variables, never in the browser or in git; the
one-time id is inside the signed text) and the bot fetches it on its next poll. A request is claimed once; a replay
(same id) or an expired one is refused.
3. The bot checks the signature, runs a dry run, reports "would change N", applies, reads the value back from DialRush,
and reports "done" or "failed" with before and after counts.
4. The CRM log keeps every step. The bot also logs to its Discord channel.
Why a poll and not a direct call: the bot is not a public web server, so a direct call would need a new open door.
Needs: a jobs table (a database change, with undo), the signing key set by Julian in the server variables, and a stop
switch (`DIALRUSH_ACTIONS=off` default) the bot checks first.
## Agent view (added Nov 19)
Julian wants an agent to run their own DialRush, with Dopamine Dialer's patterns: a mode switch, a lead queue with a
next-up card, and task cards. Dopamine Dialer (practice data only, copy kept in the NAP AI builds backup, folder
`Dopamine-Dialer`) has three floor modes (Normal, Training, Dialed), a queue of the next 8 leads with the first one
marked, a call card showing the mode, and callback and appointment dispositions. The mock reuses those ideas, restyled
to Ice, with no data copied. In the mock a top switch picks Admin view or Agent view; a small "Viewing as" switch
shows the VA version.
**Mode** (shown on every Agent tab): Inbound only, Outbound only, or Blended (inbound first, then outbound). A VA has no
choice: VA routing is inbound first, so a VA sees "Inbound first" and no selector.
| Tab | Shows (counts and practice rows, first-name-only labels like "Practice Lead 1") | Data source |
| --- | --- | --- |
| My playlists | the agent's own playlists: used by (inbound or outbound), priority, leads, on or off. Priority is read only | connector read-only data; bot inspect snapshot for on and off |
| Inbound | waiting count, longest wait timer, answered and missed today, a next-up card, the inbound queue | connector `get_stats` and `search_call_logs` (read only); live queue not available from the connector: TBD |
| Outbound | dial list size, dialed and contacts today, top priority, next-up card with its playlist and attempts, the dial list | connector stats; the dial list itself: TBD |
| Tasks | follow-ups, callbacks, appointments, done today; a task table | Nexus (the CRM), not DialRush |
| Leads | the agent's lead files (leads, worked, status) and leads by status | connector `get_report` (lead_status_penetration), Nexus |
**What changes, and what starts it** (all inert in the mock, each shown off with "Coming soon"; clicking opens a sheet
that says "Needs a typed yes and the bot runs it; not running tonight"):
| Change | Starts with | Goes through |
| --- | --- | --- |
| Change mode (Inbound only, Outbound only, Blended) | the mode selector | the bot, with a typed yes |
| Take call | the next-up card on Inbound or Outbound | the bot, with a typed yes |
| Turn one of the agent's own playlists on or off | a row on My playlists | the bot, with a typed yes |
| Mark a task done | a row on Tasks | Nexus only, not DialRush. A proposal for Julian: not decided |
Nothing in Agent view changes a playlist's priority or moves a lead file; those stay admin phase 2.
**Who may do it:** the agent, for their own mode, calls and playlists only. An MGA heading a branch, for agents in their
branch. Julian, for everyone. GA, SA, Contracting team and VA do not change another person's DialRush. A VA's mode is not
chosen by the VA (inbound first). The CRM must refuse the request on the server too, not only hide the button. This
role list is a proposal for Matteo and Julian.
**What could break:** a mode or playlist change moves which calls reach the agent, mid-shift, and a toggle clicked
twice flips it back; "Take call" must never race with DialRush's own call routing, so two calls could reach one agent
if the bot and DialRush disagree; a DialRush layout change breaks the bot's screen route, and the panel then shows the
last good time, never a guess. Counts from the connector can lag the DialRush screen.
**What is not built:** everything above. No live inbound queue source exists today (the connector shows stats and call
logs, not a live queue), no bot code for mode change, take call or per-agent playlist toggle, no per-agent identity link
from a CRM login to a DialRush user, and no task data wiring. DialRush is the only dialer in scope; the Whop payment
structure is not touched. Nothing runs tonight.
## Not done, not tested
- No code, no database change, no bot change. Spec and mock only.
- The three actions have no bot implementation; the existing bot actions (users, upline, playlist assign) have never
been run on real DialRush.
- Playlist priority and on/off are read only through screen inspection, never confirmed against a live run in this
scope.
- Role list for phase 1 is a proposal.
- The mock uses the Command Center's Ice look (dark, blue glow). `docs/crm/UI_RULES.md` describes the portal's honey-gold
canvas, so this panel is in the Command Center's look, not the portal's. Every action that does not exist is shown off
with "Coming soon"; clicking one only opens a sheet.
## Questions for Matteo
1. Which roles see the admin view in phase 1: 1st level, MGA heading a branch, GA, SA, Agent, Contracting team, VA?
Recommended: 1st level and Contracting team only (counts only); MGA heading a branch, GA, SA, Agent and VA do not
see it.
2. Build the snapshot table now with phase 1, or start with Call grading only (no new table)? Recommended: Call grading
only first.
3. Reuse the existing jobs pattern with a signature (above), or a new door? Recommended: reuse.
4. (Agent view) Let an agent change their own mode and own playlists, with the MGA heading a branch for their branch and
Julian for all? Recommended: yes, own only for an agent; the typed-yes route stays a decision for Julian.
## Decision (Julian, Nov 19, 2:46 AM ET)
A typed yes inside the CRM may approve DialRush changes, for Julian only. The CRM signs and logs it, and the bot reads the value back. Nothing runs tonight.
## Source of the Agent view (Julian, Nov 19, 2:41 AM ET)
His words: "add dopamine dialer where agents can control their dial rush and manage tasks/leads via the inbound and outbound panels and selected mode".
Open question for Julian: who may change a mode or a playlist (the agent for their own, MGA heading a branch for their branch, Julian for all, or Julian only). The decision recorded above covers Julian's own typed yes only, not an agent's. Building it needs the Opus build plus independent review rule.
The mock's explaining sentences on the sheets are removed in the real screen.