Report · 2 September 2026

Three accounts live, and the number box on the watch board

For: Dil, Ken, Beth · Date: 2026-09-02 · Page: bookedsolidinspector.com/watch.html

Dil asked for two things this morning. Both are done. One thing on GC is left amber on purpose, and it needs Ken.

1 · Property Masters, Staffordshire and GC are marked live

All three now read Live, with a date of today and dil as the person who marked them. Nothing was sent to any client to do it.

AccountWhat was writtenAnything else
Property Mastersmarked liveevery other step was already green
Staffordshiremarked liveevery other step was already green
GCmarked live; the two emails marked told by hand — Ken & Bethsee below

GC needed more than a date. Its row was red for three steps: the corporate CRM contact, the welcome email and the number-and-scenarios email. Chad was hand-held by Ken and Beth, so the two emails are now recorded as told by hand, the same way Giselle's are. The contact step fixes itself: the system now looks up a submitted client's corporate contact by email and records the id. That runs about twenty seconds after this deploy and every fifteen minutes after. It is a lookup only. No tag, no stage, no note, so nothing in GoHighLevel can fire off it.

One amber flag stays on GC, deliberately: "Running on built-in seed." Chad's number routes to the account called gc. Josh reads gc. Chad's finished form is under a second account called c. So Josh is not reading Chad's finished answers. Folding them together changes what Josh says on Chad's real line, and the gc record carries the pre-drywall price fix from 19 August that Chad's form may not. That is a ruling for Ken, not something a green tick should hide. Say the word and it is one script.

Two things worth knowing about how GC was marked live. The Build Board button would have refused it, because the gc record is still a draft. It was written directly on Dil's instruction. And the button itself had a fault: pressing Mark live on Staffordshire would have emailed Giselle a second copy of the number-and-scenarios email Beth sent her by hand on 28 August. The sweep learned to count a hand-send on 1 September; the button had not. Fixed.

2 · The number box

Every account with no number now has a small box on its row, right beside No number → default brain, visible with the row closed. Type the number, press Point it at Josh.

What happens, in order:

  1. The number is saved to a file on the data branch and is live the same second. No commit, no .env, no restart. The next call on that number reaches the client's own brain.
  2. Telnyx is read, never written. The row says whether the number is on the austin-voice app. If it is on some other app, it says so in red, because a number in our map on the wrong Telnyx app is the line that answers and plays silence.
  3. The email sweep runs at once. Email #2 (the number and the things to try on it) goes the same minute, through the same gate and the same once-only marker as always.
  4. The board refreshes and the rail shows the new step.

It stops one step short of "the end", on purpose. It does not mark the account live. That still waits on a real call on the line and a person pressing Mark live, which is Ken's rule from 1 September: marking an account live on a number nobody has dialled is how a client's first caller becomes our first test.

It never re-points a number. Type Chad's number into another account and it refuses with the owner's name. The order is the code map, then the .env, then the file, and none can move a number the one before it holds. Test accounts (xyz, pdf, our internal test slugs) are refused a number.

If a wrong number is typed, it cannot be re-pointed from the page. Edit phone-numbers.json on the dashboard-data branch, or ask.

Files