The Roundtable · private map · Nov 19, 2026

CRM and Command Center, connected to DialRush

What exists, what is partly built and what is missing, read from the CRM repo, the bot repo, the review notes and the project threads. Anything not confirmed is marked TBD. Read only: nothing was changed in DialRush, Railway or live CRM data.

The short answer

CRM reads DialRush today

One read-only connector with three tools in use: call list, call transcript, daily stats. It feeds Call Review and Dialer Stats. Whether the 5 minute pull is switched on in Vercel is TBD.

Nothing can change DialRush

DialRush has no public admin API. Every change (create or turn off a login, move an upline, assign a playlist) has to be a browser robot in the bot. It is built, switched off, and has never run on real DialRush.

The CRM cannot ask the bot yet

The CRM to bot job queue exists but only knows the old ReadyMode dialers. The signed request, typed yes and stop switch Julian chose at 2:46 AM ET are not built.

Command Center is a preview

It lives as an artifact with browser-only practice data. It is not in the CRM code yet. The shared database for it is being written, not run.

Connection map

CRM screens Call Review, Dialer Stats Members (DialRush logins) Dialer Bot, VA, Hit List Hierarchy, Whop billing DialRush panel spec and mock only Command Center artifact preview, not in web/ board data stays in the browser practice data only CRM server (Vercel) cron pull every 5 min DialRush link, sealed logins /api/dialer/jobs door Call Review door, stats ingest Supabase tokens and logins (sealed) pull ledger, dialer_jobs call reviews, hierarchy Signed requests typed yes, one-time id stop switch. Missing Bot (Railway) Discord, map, inspect 7 actions in PR 30, off create, turn off: not merged DialRush read-only connector: 3 tools used no public admin API screens: users, playlists, lead files Julian's own yes for every change sync SQL not run READ: connector, every 5 min (switch TBD) polls jobs claimed once WRITE robot, off Agents and leaders sign in to DialRush themselves with the login the CRM holds for them. No arrow carries data from the Command Center to DialRush. Its DialRush panel is a mock.
Built and wired Built, off or unproven Missing

Every module and what it does with DialRush

ModuleDialRush linkStatusWhat is true today

Ranked gaps to run DialRush end to end

Order is the order things depend on each other. Each one names who must say yes. Nothing here runs without Julian's typed yes.

    The flow Julian chose

    • A leader or Julian asks in the CRM.
    • Julian types a yes in the CRM (Julian only, chosen 2:46 AM ET). The CRM signs and logs it.
    • The bot polls, checks the signature, runs a dry run and reports what it would change.
    • The bot applies it only after the dry run matches, then reads the value back from DialRush.
    • The CRM logs who asked, who approved, before and after counts.

    Rules that stay

    • No DialRush delete action exists in the bot. Old ReadyMode delete code is still in the repo. The control layer (not merged) refuses Elite accounts.
    • Julian's limits, as recorded in the project notes (06 DialRush context file, Nov 19, not re-checked against the file): Elite adds, money, bulk over 10 people or 1,000 leads, deletes and lead uploads need his typed yes. Thresholds TBD with Julian.
    • Counts and code words in logs, never names or phone digits.
    • Scripts go in word for word.

    TBD, not confirmed

      Sources: jg-financial-workspace (web/src, docs/crm), jg-dialer-bot (main, PR 30), Fable reviews of the control layer and the 5 minute feed, the DialRush panel spec, the Command Center plan and the project threads. Counts above come from the lists on this page.