Home
# VA routing on DialRush: run sheet for Julian (version 2, on the reviewed control layer)
**NOT RUN ON REAL DIALRUSH.** Everything here was tested only on a fake practice page. The screens these actions need (the
Create Playlist window, the playlist page, the file list) have not been mapped on the real site, so the bot may answer
"Screen not as expected ... Nothing was changed". That is the safe outcome: send the message back so the screens can be mapped.
## What works and what is refused today (no refusal was loosened; one exact write label, Save Priority, was added to the allow-list)
| Step | Today |
|---|---|
| 1 Create "VA Inbound" | **Refused by the guard.** "Create Playlist" is a forbidden label. The bot will say it never presses it. Needs Julian's or Matteo's decision to allow that one label. |
| 2 Attach one lead file | **Refused.** The attach button's exact label is not known, so it is not on the write allow-list. Once the exact label is seen on the real site it can be added to the list (not as anything with "lead file" in it: the guard refuses that wording). |
| 3 Set priority | Can run (once the playlist page is mapped). |
| 4 Assign agents (and unassign) | Can run. Uses the existing Assign Playlist and "Remove from playlist" clicks. |
| 5 Turn a playlist on / off | **Refused by the guard.** It never presses an on/off switch. |
Because 1, 2 and 5 are refused, the first real try that can work is step 4 (or 3 after mapping).
## First, confirm these on the real site (before anything is switched on)
1. **The number at the end of a playlist row ("<name> <speed> <number>") is ASSUMED to be the priority.** Nothing has proved it. Step 3 reads that number before and after, and the bot stops with an error if the number DialRush shows after the change is not the one asked for. Check it by hand on one playlist first.
2. The playlist page: the priority box, its Save Priority button, the file list and the Add File button (all guessed, marked UNVERIFIED in the selector file).
3. The Create Playlist window: its fields and submit button.
4. The row number read for a speed other than Predictive.
## Before anything (needs Julian's own yes)
1. Railway already has `DIALER_BACKEND=dialrush` and the DialRush login variables.
2. **Turning routing on is a config change plus a redeploy of the live bot.** In `config.yaml` `dialrush: routing:` goes from `false` to `true`. It needs Julian's own yes (nobody else's, and not a tool's) before anyone does it.
3. **Only Julian can use these five.** His Discord user id goes in the Railway variable `DIALRUSH_ROUTING_USER_ID` (no id is stored in the code). Empty or unset means nobody can. Anyone else who asks gets "can only be asked by Julian", and anyone else who presses Confirm is refused. The layer's other functions are not affected.
4. Every step works the same way:
- You ask in plain English. Add "dry run" to see what it would do without a change.
- A real request makes the bot look at the screens first (a dry run), then it posts a card with **Confirm** and **Cancel**. Only Julian, who asked, can press. Confirm is the yes (the layer's own button, not a typed phrase). It expires after 5 minutes.
- The bot answers "N of M done" and posts one line (counts and a code word, no names) to the log channel.
- Never done by the bot: Elite playlists (any name with "elite"), names with seat / billing / money words, uploads, deletes, more than 10 agents in one request.
## Step 1. Create the "VA Inbound" playlist (refused today)
- **Command:** "Create the VA Inbound playlist."
- **You press:** Confirm on the card (you will not get that far today: the bot says it never presses "Create Playlist").
- **If it were allowed:** a new Predictive playlist "VA Inbound", priority 1, off. Refused if one with that name exists. Read back from the Content Library list.
- **Undo:** the bot never deletes a playlist. A manager deletes it in DialRush.
## Step 2. Attach one lead file to a playlist (refused today)
- **Command:** "Add lead file `<file name>` to playlist `<name>`." One file per request.
- **You press:** Confirm.
- **Today:** the dry run shows the playlist and says the button is not allowed; a real run stops with "isn't known ... nothing was changed".
- **If it were allowed:** the file is added to that playlist only. A file already in another playlist is refused (moving a file is not prepared). Nothing is uploaded, no lead file is ever deleted.
- **Undo:** take the file off by hand in DialRush (the bot has no remove-file action on purpose).
## Step 3. Set a playlist's priority
- **Command:** "Set playlist `<name>` to priority `<1 to 5>`." (add "dry run" to test)
- **You press:** Confirm. The dry run and the card show the old value (the number in the playlist's row).
- **You should see:** "priority set. 1 of 1 done." The bot reads the row again; if the number differs it **fails** and says what DialRush shows.
- **Changes:** that one playlist's priority.
- **Undo:** set it back to the old value the dry run gave you (new request, new Confirm).
## Step 4. Assign agents to a playlist
- **Command:** "Assign `<name1>, <name2>` to playlist `<name>`." Up to 10; 11 or more is refused with no way around it. Add "and take them off `<old playlist>`" only if you want that.
- **You press:** Confirm.
- **You should see:** "agents assigned. N of N done." An agent already on the playlist is skipped and counted as done. A name that matches two accounts asks which one.
- **Changes:** those agents go onto that playlist. They are taken off the old one only when you asked, and after each one the bot reads the old playlist again and fails that agent if they are still on it. Accounts are never removed.
- **Undo:** assign them back to the old playlist (new request, new Confirm). To only take someone off a playlist use the existing "remove from playlist".
## Step 5. Turn a playlist on or off (refused today)
- **Command:** "Turn playlist `<name>` on" (or off).
- **Today:** the dry run reports whether it is on or off (from DialRush's own playlist list). A real run stops: the guard never presses an on/off switch.
- **If it were allowed:** only that switch, read back afterwards.
- **Undo:** the other direction.
## Live transfer (not code, not built)
The VA playlist's **script** and the **transfer to a licensed agent** are set up inside DialRush by a person, not by the bot. **Hours are still to be decided.** Nothing here starts dialing or changes a script.
## Waiting on you
- Julian's own yes to turn routing on (config change plus redeploy), and his Discord id in `DIALRUSH_ROUTING_USER_ID`.
- Decide whether the guard may allow, as exact labels, "Create Playlist" (step 1) and the on/off switch (step 5). Until then they stay refused.
- Once the attach button's exact label is seen on the real site, say so and it can go on the allow-list (step 2).
- Decide the live-transfer hours.