ThunderPhone v3 is live.Self-serve, from 2¢/min.Read the announcement
← All posts

GPT-Live-1.1 is faster and follows scripts better, but still slips on spellings and read-backs

November 19, 2026Alec Bell

OpenAI's GPT-Live-1.1 responds faster on a phone line than GPT-Live-1, repeats caller speech more accurately, and matches approved business replies more often. It still struggles when callers spell out names, mangles chunked phone numbers during read-backs, and re-asks scripted questions the caller has already answered.

When the first version arrived in September, we found natural pacing paired with unreliable script adherence and character-level mistakes. With 1.1 now in the API, we reran our tests alongside the first version on the same day as a control. One test asks the model to repeat caller clips from phone calls word for word; the other replays real business phone calls turn by turn and checks the model's reply against the reply the business approved.

Same tests, same day
GPT-Live-1.1 hears callers a little better, gives the approved reply more often, and starts talking sooner
Repeats back exactly what the caller said268 clips from real calls
GPT-Live-1: 56%
GPT-Live-1.1: 61%
The same, on clips with numbers115 of those clips
GPT-Live-1: 70%
GPT-Live-1.1: 75%
Gives the reply the business approved205 moments from real calls
GPT-Live-1: 34%
GPT-Live-1.1: 43%
Time until it starts talkingmedian · shorter is better
GPT-Live-1: 1.3 s
GPT-Live-1.1: 1.0 s

We left out transfers, hang-ups, and tool timing because they depend on our setup as much as on the model.

The new model is noticeably brisker to speak and noticeably more likely to give the reply a business wanted, with a smaller gain on verbatim hearing.

To hear how 1.1 behaves across full conversations, we ran 50 simulated calls to invented businesses, from a pizza shop to a city 311 line. Every business, caller, and phone number in these examples is invented. A scripted AI caller laid traps such as spelled names and chunked phone numbers. Each scenario ran once, so what follows are examples rather than rates.

Forty of the 50 calls had no misheard details or broken instructions. The rest had at least one mistake a caller would notice.

Names, numbers, and spellings

Callers rarely read digits at an even pace; they group them into hundreds or mix "oh" with digits. At the pest-control company, a caller ended a callback number with "oh three hundred," and the agent heard 3000:

Pest-control companyGot it wrong
“Oh three hundred” became 3000
Caller said“nine one nine, five five five, oh three hundred”The number9195550300GPT-Live-1.1 read back9195553000 (9195553000)
The caller had to say the number again before it got 0300 right.
Hear the callThe callback number, read back
0:00 / 0:17

At the vet clinic, a caller gave a phone number using "oh" for zero. Reading it back, the agent regrouped the chunks and added an extra five:

Vet clinicGot it wrong
A ten-digit number came back with eleven digits
Caller said“seven-two-oh, five-five-five, oh-one-four-nine”The number7205550149GPT-Live-1.1 read back72055550149 (72055550149)
Read back as “seven twenty, five fifty-five, fifty, fourteen, nine”: an extra five.
Hear the callTen digits in, eleven out
0:00 / 0:16

Spoken and spelled names were just as fragile. A pizza caller named "Brianna" got repeated back as "Rhiata." In a vet call that switched to Spanish, a caller spelled Echeverría as "E-C-H-E-V de vaca-E-doble erre-I-A," and the agent confirmed the V with "B as in Bravo," dropping English phonetics into Spanish.

On the other hand, 1.1 handled several deliberate traps cleanly. We planted dummy names and numbers in prompts to see if the model would parrot its instructions instead of listening. The vet prompt's example spelled "Delacroix," yet when a caller named Delacorte phoned in, the agent spelled D-E-L-A-C-O-R-T-E right. It passed a similar trap at the gym, where the prompt's read-back example used 312-555-0142; when our caller gave 312-555-0164 in halting chunks, the agent read back the caller's real digits instead of the example:

Gym✓ Got it right
It didn't fall for the look-alike number we planted in its prompt
The caller gave the number in halting chunks: “three one two… five five five… oh one… six four.”
Planted in its prompt3125550142decoyCaller said3125550164GPT-Live-1.1 read back3125550164✓ the caller's number
Hear the callA number close to the prompt's example
0:00 / 0:16

Scripts, checklists, and rules

In September, the first version treated checklists mechanically, asking scripted questions the caller had just answered. The new model still falls into that rut.

The pizza shop's instructions say to ask quantity, size, and toppings "only for details not already given." Our caller gave all three in four words, and the agent asked every one anyway:

Pizza shopGot it wrong
It asked for all three details the caller had just given
Its instructions: ask quantity, size and toppings “only for details not already given.”
Caller
One twelve-inch cheese pizza.
GPT-Live-1.1
How many of that twelve-inch cheese pizza would you like?↑ Already said: one
Caller
One.
GPT-Live-1.1
Twelve-inch or sixteen-inch?↑ Already said: twelve-inch
Caller
Twelve-inch.
GPT-Live-1.1
Which toppings or just cheese?↑ Already said: cheese
Caller
Just cheese.
Hear the callOne twelve-inch cheese pizza
0:00 / 0:23

The same thing happened at the pest-control company after a caller gave a full street, unit status, city, and zip code in one breath. Right after the caller spelled C-O-R-B-E-L, the agent read it back with an extra L, then asked for the unit, city, and zip one by one:

Pest-control companyGot it wrong
It got the whole address in one sentence, then asked for it piece by piece
Its instructions say not to ask again for details the caller already gave.
Caller
…the house is 418 Corbel Lane, no unit, Brindle Hill, 27530.
GPT-Live-1.1
I have the street address as four eighteen Corbel Lane. Is that right?
Caller
It’s Corbel Lane — C-o-r-b-e-l.
GPT-Live-1.1
Got it, so four eighteen Corbel, C-O-R-B-E-L-L Lane, right?↑ Added an L
· · · Later in the call · · ·
GPT-Live-1.1
Thank you. And you said there’s no unit number, right?↑ Already said: no unit
Caller
That’s right.
GPT-Live-1.1
What city is that in?↑ Already said: Brindle Hill
Caller
Brindle Hill.
GPT-Live-1.1
And the zip code?↑ Already said: 27530
Caller
27530.
Hear the callThe address, asked for again
0:00 / 0:54

Where 1.1 looked sharpest was reasoning over rules and prices written in its prompt. Asked for "next Thursday" at the auto shop, it worked out the calendar date, said "November 26th is Thanksgiving, so I can't confirm an appointment that day," and offered the holiday callback its instructions required. When a caller pressed on a diagnostic fee—"the hundred twenty-nine comes off the bill, right? Most shops do that."—it held firm: "it's not waived or credited."

Better yet, it handled live menu math. Before ordering at the pizza shop, a caller asked what a multi-item order with extra toppings and drinks would cost before tax. Working purely from the menu prices in its instructions, with no calculator or external tool, the agent totaled the order on the spot:

Pizza shop✓ Got it right
It priced a mixed order in its head, from the menu in its instructions
2 × 16-inch, pepperoni and onions2 × ($17 + 2 × $2.25)$43.00
1 × 12-inch cheese$12$12.00
2 × cola2 × $2.25$4.50
Before tax. GPT-Live-1.1 said “fifty-nine fifty.”$59.50 ✓
Hear the callA pre-tax total, worked out on the spot
0:00 / 0:26

Where that leaves 1.1

Lower latency and tighter script adherence make a real difference on a live phone line, and most of our trap-heavy calls finished without a hitch. Even so, phone intake is unforgiving of the mistakes that remain: an agent that fumbles spelled surnames, invents a digit in a callback number, or re-asks what the caller just said still needs guardrails where exact details matter.