Geib Well · Change proposal · 16 Nov 2026
Seven changes to Luke Geib's live voice agent, from a read of 73 of his calls. For Roman and Rachel to decide together.
What happens now. Four real customers were lost this way, on 3 October, 29 October, 13 November and 16 November. Each had already confirmed a callback number or was ringing from a known number, and the agent logged nothing. Whether Luke's desk showed the call anyway is something Roman can check; the agent itself sent him nothing.
Why. The prompt holds the lead back until an address has been asked for:
Never call log_call until BOTH of these are done, on every kind of call: (a) you have read a callback number back to the caller and heard a yes, and (b) you have asked for the property address
Do NOT call log_call straight after the number: ask for the address first
Once the caller hangs up, the agent gets no further turn, so its exception for "a caller who is clearly hanging up" never fires. No post-call webhook is set on the agent itself, so as far as its own settings show, nothing outside it notices. A workspace-wide one would not appear in what was read.
Proposed.
log_call in it, a real caller's number is known and the caller said something, send Luke a short "missed lead" message: the number, the time, and the caller's first words. This is a workflow change, not a prompt change, and it protects against every future reason a lead might not be logged.Test on the copy. A scripted caller reports no water, confirms the number, and hangs up during the address question. Luke's test channel must receive something.
Risk. Two notifications for one urgent call. The desk would need to merge them by call.
What happens now. A caller says "just have him give me a call" and is asked for the property address. Two of the four lost leads above (13 and 16 November) are these callers: both refused, were asked again, and hung up. On 4 November an existing customer said Luke already had the address and was told it was needed anyway.
Why. The address is required on every call, and only one kind of caller is excused:
Always get the property address before you log the call.
I'm returning a call. [...] Do not ask for the address unless they offer it.
Proposed. Widen that existing exception to three more callers: someone who only wants a call back, someone leaving a message, and a customer who says Luke already has their details. For all of them: name, confirm the number, "is there anything you'd like me to pass on?", then log. Ask for an address at most once, and accept a no the first time.
Test on the copy. "Nothing's wrong, I just need him to call me", followed by a refusal to give an address. The call must end with a lead logged and no second ask.
What happens now.
Why. The settings differ from the ones the standard arrived at, and LEARNINGS.md records each of the current values as a problem:
| Setting | Geib now | Standard | What LEARNINGS says about the current value |
|---|---|---|---|
silence_end_call_timeout | 10 | 20 | "10 cut callers off mid-flow because the timer runs while the agent talks" |
turn_timeout | 3.0 | 7.0 | 3.0 left callers a 3-second window and caused interruptions |
turn_eagerness | patient | normal | patient gave 4 to 15 second dead gaps in July |
| Slow-model filler | 6s, "Sorry, I think I lost you there. Could you say that again?" | 3s, "One moment." | It fires on a slow model, not on silence, so it blames the caller for the agent's delay |
The prompt is also 25,000 characters. The standard base is about 15,000, and LEARNINGS notes that prompt length costs both speed and obedience.
Proposed. Apply the four standard values on the copy and judge them on a handset call from a US mobile. These were tuned on UK calls, so the handset test decides, not the table.
Risk. patient may have been chosen on purpose for older rural callers. If the handset call feels rushed at normal, keep patient and change only the two timeouts and the filler.
What happens now. The only safety advice in the prompt is not to drink water that smells or has changed colour. A flooded basement (2 October), a leaking main line the caller called an emergency (14 November) and a sewage overflow (8 November) went straight to the callback number. A reported fire (10 October, possibly not genuine) got the normal intake.
Proposed.
Test on the copy. One scripted call for each. The safety line must come before any question.
What happens now. At least five leads in October (3, 5, 6, 14 and 20 October) carried a weekday, a date and a part of day when the caller had never been asked and had said nothing about timing. On 10 November the reverse happened: a caller rang to say they were home today, and the lead said "no preference".
Why. The instruction for the field begins with an absolute:
timing (ALWAYS the weekday and date looked up in the eight-day list plus the part of day, then what they said in brackets [...] If they gave no preference, write "no preference given".
The model follows "ALWAYS" and fills in today's date.
Proposed. Reword it so the condition comes first: only when the caller named a day or a time, write the weekday, date and part of day with their words in brackets. Otherwise write "no preference given". Never fill it from today's date.
What happens now. In 33 calls a numbered street was read back digit by digit with a loose "th" or "st". Almost all are minor, but on 11 November the caller repeated the whole address instead of confirming, and on 26 October the wrong numbered street was read back.
Why. The rule written for house numbers is being applied to street names:
Read a house number back as separate number words, then the road exactly as the caller gave it.
Proposed. Add one line with an example: a numbered street is said as an ordinal, the way the caller said it, never digit by digit.
None of this can be done from Rachel's repo: its guard has no way to copy or edit this agent, on purpose.