# Everything else the 17 August meeting asked for

*For Ken and Dil. Written 2026-08-17, after reading the meeting transcript end to
end — including the first half, which the twelve-item list did not cover.*

The twelve items Dil listed are built and on
`claude/dashboard-portal-onboarding-5n91ic`. **Nine more things were decided or
asked for in that meeting.** Two of them block Tuesday.

---

## 🔴 1. The 13 testers have no phone number to call

Ken, and this is the whole shape of Tuesday:

> *"Could we give them a number temporarily before we ported it over? … We have a
> Telnyx number for Ted and Chad, right? Could we give them a Telnyx number like
> that temporarily?"*

And the rule underneath it, which he stopped Beth mid-sentence to say:

> *"**Nobody is going into the system. ISN is still scheduling their stuff.** The
> only thing we're doing is dummy testing our system. So we have to give them a
> phone number that **has nothing to do with what they're doing now**."*

Beth: getting a number takes **3 minutes**. Ken: *"That's solved. Damn, that was
easy."*

⚠️ **It is not solved. Nothing has been bought or wired.** A tester who says yes
on Tuesday night has nowhere to ring.

**And a number is only a third of the job.** `CLAUDE.md` records this from the
2026-07-28 incident, where a Delaware caller reached GC's Texas brain: a new
number needs (a) buying in Telnyx, (b) its SIP application set to `austin-voice`,
and (c) a row in `NUMBER_TO_INSPECTOR`. Miss the third and **it answers as the
wrong company.**

---

## 🔴 2. Provisioning a tester is still two hand edits and a restart

Ken heard Dil describe the process and stopped him:

> Dil: *"I just tell Claude, hey Claude, this client just completed their form…
> then Claude will create a dashboard."*
> Ken: *"Now, I heard something that **gave me a little bit of heartburn**, and
> that was trying to tell Claude Code somebody signed up and create a new
> dashboard. **How will we automate that?** … When somebody completes the
> onboarding form, it should **automatically** create their dashboard. We wouldn't
> have to say anything to Claude."*

**He is more right than the answer he got.** I checked. On submit, the onboarding
flow *does* create the client's GHL sub-account automatically —
`provisionSubAccount()` runs on its own. **But two things per client are not
automatic, and both are environment variables:**

| What | Where | Needs |
|---|---|---|
| Portal passcode | `INSPECTOR_PASSCODES` (JSON env var) | edit `.env` + restart |
| Number → company | `NUMBER_TO_INSPECTOR` in code, or `NUMBER_TO_INSPECTOR_EXTRA` | edit + restart |

**Thirteen testers is thirteen `.env` edits and thirteen restarts**, each one a
chance to typo a passcode or point a number at the wrong company. That is exactly
the manual step Ken was pointing at.

**The fix is not large:** move both into the onboarding store, which is already
where the client record lives, and have `provisionSubAccount()` write them. The
env vars stay as an override so nothing existing breaks.

---

## 🟠 3. Each tester needs DIFFERENT scenarios

> *"I would need Claude to develop some scenarios for us. He did really good…
> Here's your name, here's who you call, here's what you're gonna ask… **But we
> don't really want everybody asking the same thing, because we don't learn
> enough.** If we had scenarios different for each one of the testers, we could
> maximise what we could learn."*

And why it matters, from Chad's experience:

> *"After you call a couple of times, now you're doing Old Spice and you're doing
> your daddy… you kind of **run out of crap**."*

⚠️ **The 37-call review tells us exactly what to write.** Three things Chad never
tested, all of which Ken has raised:

- **the marketer / robocall** — Ken put it on his own list in this meeting
- **an angry customer or a complaint** — the whole reason stop-marketing exists
- **the pre-drywall**, which is a **known live fault**: Josh refuses to quote it
  though GC sells it at $425 flat. It has already cost a real job.

**This is a document I can write.** Thirteen sets, no overlap, weighted to what is
still unproven.

---

## 🟠 4. Testers need an instruction sheet

> *"We're going to need some instruction sheets."*

One page: here is your number, here is your login, here is what to try, here is
how to tell us what went wrong. **Not written.**

---

## 🟠 5. ⚠️ Do NOT install the web widget on a tester's website

Ken talked himself into this one and it is a firm no:

> *"I probably would prefer that they do **not** put it on their website, and
> here's the reason: somebody comes in there and goes live, and **they think their
> inspection's booked, and it ain't** — because they ain't on our system yet.
> They're booked through the ISN or Spectora, that's where they need to go. So I
> think **a website install is dangerous, so we won't do that.**"*

**A real customer of a real inspector books an inspection that does not exist.**
This needs to be on the White Glove checklist as a hard no for testers, and it is
not recorded anywhere yet.

---

## 🟡 6. An ambiguity about the MSA that only Ken can settle

He said two different things, an hour apart, and **my build followed the second
one** — so this is me flagging it rather than assuming.

**Early in the meeting:**

> *"It would be interesting to get the master service agreement signed **as part
> of the onboarding**, so that we could just make sure those workflows worked… that
> master service agreement has to be there in those checks, **even though it's just
> practice**."*

**Later in the meeting:**

> *"We're just letting them do the dummy account… when they come back in, they
> need to select their plan and get paid, and **they would check the agreement
> there**. They could skip the onboarding form."*

**These are reconcilable** — the agreement is *required* at purchase, and he would
*also* like it exercised during onboarding to prove the workflow runs. **The
tester path I built has no MSA at onboarding.** If he wants the practice run, it
is a small change. **His call.**

---

## 🟡 7. "Do not mention the word cancel"

> *"You can't piss AI off unless you get the wrong Deepgram setting. Just don't
> mention the word cancel. **We should put a warning on Josh. Do not mention the
> word cancel.**"*

Said half as a joke, but he is describing a real behaviour someone has seen.
⚠️ **A tester will say "cancel" on Tuesday** — it is the most natural word in a
scheduling call. **Worth ten minutes finding out what actually happens before
thirteen people discover it at once.**

---

## 🟡 8. The website needs simpler English, and a video per segment

Chad's verdict, which Ken repeated twice:

> *"I read what you wrote, and I read the website, but I was struggling with it
> because **I couldn't understand the concept.** I had never seen it."*
> Ken: *"I need to be able to produce a video for each segment of the website. We
> need to rethink that website. **We need to get it in simpler English.**"*

⚠️ **Explicitly NOT for Tuesday** — *"right now, for the 13 testers, I don't
care"* — they know him and will listen. It matters for everyone after.

---

## 🟠 9. Record Tuesday's Zoom — Ken only wants to give this pitch once

> *"We should **record the Zoom and get the transcript**, and from that we can
> start making some decisions on how to improve the presentation. **I just want to
> make it once** for people to come on… **break it down into segments. Use it for
> marketing the product.**"*

And why, in his own words:

> *"I took **two hours** with Chad. I'll take as much time as they want, but **I
> can't do this over and over.**"*

⚠️ **If the recording is not switched on, the asset does not exist and cannot be
recreated** — he says the tone will be different on a video for strangers than
with people who already know him. **Somebody has to press record.**

He also wants to learn from it: *"we wanna make sure the substantive points are
hitting with them… we need to focus in on those points."*

---

## ✅ 10. Cliff and Deepgram Flux are dead. Staying with ElevenLabs.

This one is a **decision, not a task** — it closes the item that has been open
since the 13 August handoff.

Dil tested it and reported back:

> *"The voice is okay, the expression is okay, **but it cannot be done** … Telnyx
> is not compatible … it sounds like a radio … like a very old record."*

Ken: *"That old AM radio sounded pretty nasally, huh? … **Okay, so then what we
have is what we have until something else comes out.**"* And later: *"since we're
not using Deepgram, **we're staying with 11 Labs**."*

**Two things follow:**

- ⚠️ **`CLAUDE.md`'s 2026-08-13 entry still describes the Flux switch as work in
  flight, blocked on a Pipecat upgrade.** It should be marked closed — the blocker
  is now moot because the voice itself was rejected on quality.
- **Pipecat 1.6.0 was tested anyway and Dil says it is fine.** That upgrade may
  still be worth taking on its own merits, but it is no longer needed *for Flux*.

This is also why the **voice-audition page** matters more, not less: ElevenLabs is
where the improvement has to come from now, and Ken asked to hear the options.

---

## 🟡 11. Two things that are Ken's and Beth's, not ours

- **Ken owes the legal text.** New terms of service, new disclosures, and the MSA
  check-marks: *"I need tomorrow to plug all of those in… shouldn't take me 2
  hours."* Plus *"two or three other things"* he said he would point out directly.
  **The MSA gate is built and waiting for exactly this** — the clause array is
  empty on purpose.
- **Beth's email sequence is missing one.** Ken: *"we don't have a one right
  before 8 o'clock that says we're getting started, please jump on a call now."*

---

## What I would do next, in order

**Before Tuesday:**

1. **Buy the numbers and wire them** (§1) — pointless to onboard anyone without
   this, and it is three steps per number, not one.
2. **Automate the passcode and the number mapping** (§2) — Ken asked for it by
   name, and thirteen manual edits is where a tester ends up hearing another
   company's prices.
3. **Write the thirteen scenario sets and the instruction sheet** (§3, §4) —
   weighted to the marketer, the angry caller and the pre-drywall.
4. **Find out what "cancel" does** (§7).

**And from the call review, in the same pass:**

5. The price-band error — one booking is $50 wrong right now.
6. The AI disclosure — Ken ruled it Monday, it is in neither brain.

**On the night:** somebody presses record on the Zoom (§9). It cannot be
recreated afterwards.

**Waiting on a human:** the MSA text (Ken), the onboarding-MSA question (§6, Ken),
the email sequence (Beth).

---

*Source: the full 17 August meeting transcript, 3,926 lines, 1h37m — read end to
end. Two uploads of it were supplied and they are byte-identical, so nothing in
this note is drawn from a partial copy.*