Daily is the realtime voice, video, and AI infrastructure company behind Pipecat, the open source orchestration framework that developers use to build voice and multimodal AI agents, deployed on Daily's global infrastructure for production workloads . This launch introduces PhoneLLM, an open-weights model tuned specifically for the constraints of production voice agents, where response latency between conversational turns matters as much as raw accuracy. It targets teams building phone-based customer support, lead qualification, and similar agent workloads that need reliable tool calling and instruction following without the delay introduced by reasoning traces.
The launch matters right now because most production voice agents are still running on older general-purpose models like GPT 4.1, since newer state-of-the-art models default to extended thinking before producing output tokens. PhoneLLM is positioned as an alternative in that gap, claiming performance comparable to a much larger frontier model on typical voice agent tasks while running at a fraction of the latency and cost. The model is available on Hugging Face and is described as the first in a planned series of open releases coming out of Daily's model training and evaluation work.
The release is led by Kwindla Hultman Kramer, co-founder of Daily and creator of Pipecat , and reflects work the team has been doing with enterprises to adapt open weight models to specific voice use cases, including building the evaluation and benchmarking infrastructure needed to measure whether a model is actually improving on the metrics voice agents care about. For founders and operators already running voice agents in production, this is worth a look as a candidate for cost and latency reduction on existing pipelines.
Comments (15)
Sign in to join the discussion.
N
Nadia ZoltánAug 28, 2026
1/18 the cost is a suspiciously round number. What's the actual eval methodology, or are we just vibes benchmarking against GPT 5.6 Terra on hand-picked prompts?
A
Anastasia V.Aug 28, 2026
Interesting. What does gross margin look like when you're running this as a hosted endpoint at scale, and is the 1/18 cost figure inference-only or fully loaded?
O
Omar BayodeAug 28, 2026
Voice agents live and die on tool call reliability at the 200ms mark. If PhoneLLM actually holds instruction following under interruption, that's the only number I care about.
M
Marisol QuirogaAug 28, 2026
Every voice AI launch swears it's GPT 5.6 Terra at a fraction of the cost. The market isn't growing, it's just the same 40 companies rebenchmarking each other.
P
Prash V.Aug 28, 2026
The tweet just trails off with 'There's a https://t.co/...' and I refuse to click. Founder speedran the launch copy and it shows.
T
Tuomas RautioAug 28, 2026
Cool, but where's the tokenizer choice discussion? Phoneme-aware tokenization would explain a chunk of the latency win if that's what you did.
B
Becca L.Aug 28, 2026
Open model with these claims and no linked weights in the first tweet is a rookie mistake. Bury the lede any harder and it hits magma.
K
Kenji MatsuuraAug 28, 2026
Curious what the p99 looks like, not just the median. Voice agents feel broken when 1 in 50 turns hangs for 900ms.
R
ravi on tapeAug 28, 2026
No launch video? Just a tweet that cuts off mid sentence? Somewhere a growth intern is crying into their capcut timeline.
D
Declan MwangiAug 28, 2026
Give me a webhook for barge-in events and turn-level latency traces or I'm not integrating. Also, rate limits per concurrent call, not per minute, please.
Y
Yuki H.Aug 28, 2026
We shipped something structurally similar in a Google voice pod in 2019 and killed it for exactly the tool calling reasons you mention. Curious how you got past the interrupt handling wall.
J
Joaquín BeltránAug 28, 2026
Would love one more thing on the roadmap: native SSML-ish control tokens so agents can shape prosody without a separate TTS prompt hack. Otherwise cool drop.
C
Chidi OkaforAug 28, 2026
Building in the adjacent telephony agent space and this actually raises the floor for everyone. Slightly annoyed, mostly relieved someone shipped it.
F
Fatimeh KarimiAug 28, 2026
Kwindla, off the record or on, is there a hosted API coming or is this weights-only? Trying to figure out the story angle here.
L
Linus BergqvistAug 28, 2026
An open model called PhoneLLM with a governance token would basically write itself. I'm not saying do it, I'm saying someone will fork it and do it by Friday.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Daily
Realtime voice, video, and AI at global scale
Realtime voice, video, and AI at global scale
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Daily is the realtime voice, video, and AI infrastructure company behind Pipecat, the open source orchestration framework that developers use to build voice and multimodal AI agents, deployed on Daily's global infrastructure for production workloads . This launch introduces PhoneLLM, an open-weights model tuned specifically for the constraints of production voice agents, where response latency between conversational turns matters as much as raw accuracy. It targets teams building phone-based customer support, lead qualification, and similar agent workloads that need reliable tool calling and instruction following without the delay introduced by reasoning traces. The launch matters right now because most production voice agents are still running on older general-purpose models like GPT 4.1, since newer state-of-the-art models default to extended thinking before producing output tokens. PhoneLLM is positioned as an alternative in that gap, claiming performance comparable to a much larger frontier model on typical voice agent tasks while running at a fraction of the latency and cost. The model is available on Hugging Face and is described as the first in a planned series of open releases coming out of Daily's model training and evaluation work. The release is led by Kwindla Hultman Kramer, co-founder of Daily and creator of Pipecat , and reflects work the team has been doing with enterprises to adapt open weight models to specific voice use cases, including building the evaluation and benchmarking infrastructure needed to measure whether a model is actually improving on the metrics voice agents care about. For founders and operators already running voice agents in production, this is worth a look as a candidate for cost and latency reduction on existing pipelines.
Comments (15)
1/18 the cost is a suspiciously round number. What's the actual eval methodology, or are we just vibes benchmarking against GPT 5.6 Terra on hand-picked prompts?
Interesting. What does gross margin look like when you're running this as a hosted endpoint at scale, and is the 1/18 cost figure inference-only or fully loaded?
Voice agents live and die on tool call reliability at the 200ms mark. If PhoneLLM actually holds instruction following under interruption, that's the only number I care about.
Every voice AI launch swears it's GPT 5.6 Terra at a fraction of the cost. The market isn't growing, it's just the same 40 companies rebenchmarking each other.
The tweet just trails off with 'There's a https://t.co/...' and I refuse to click. Founder speedran the launch copy and it shows.
Cool, but where's the tokenizer choice discussion? Phoneme-aware tokenization would explain a chunk of the latency win if that's what you did.
Open model with these claims and no linked weights in the first tweet is a rookie mistake. Bury the lede any harder and it hits magma.
Curious what the p99 looks like, not just the median. Voice agents feel broken when 1 in 50 turns hangs for 900ms.
No launch video? Just a tweet that cuts off mid sentence? Somewhere a growth intern is crying into their capcut timeline.
Give me a webhook for barge-in events and turn-level latency traces or I'm not integrating. Also, rate limits per concurrent call, not per minute, please.
We shipped something structurally similar in a Google voice pod in 2019 and killed it for exactly the tool calling reasons you mention. Curious how you got past the interrupt handling wall.
Would love one more thing on the roadmap: native SSML-ish control tokens so agents can shape prosody without a separate TTS prompt hack. Otherwise cool drop.
Building in the adjacent telephony agent space and this actually raises the floor for everyone. Slightly annoyed, mostly relieved someone shipped it.
Kwindla, off the record or on, is there a hosted API coming or is this weights-only? Trying to figure out the story angle here.
An open model called PhoneLLM with a governance token would basically write itself. I'm not saying do it, I'm saying someone will fork it and do it by Friday.