SOLVED: 🌍 Non English Voice Latency Test Results: 350ms vs 3700ms

Cemre Sancaktar

Jun 15 (edited) • 🏰 Homebase

@Jorden Williams

I took my time to make a real life test to see if non english voice latency issue really exists.

I created a very simple prompt with 1 tool attached and made an outbound call where user speaks first.

English processor took 350 ms to respond (fastest reply ever)

I than changed the processor to Turkish processor, result was 3700ms (Way too much, for short prompt)

I have been testing my actual prompt in Turkish - I see up to 6 seconds of latency.

So Non English Voice Latency issue really exists.

I have a vision of reaching 100 customers in my market.

I don't think it will be possible with 6 seconds delay on outbound calls, any demo I make, customers complain about the latency, I tell them that will be fixed when in production.

I now see that only you can fix this problem, please make it a priority for me and for all non-english speaking Assistacrats working everyday to take your brand global. Thanks.

Feel free to test the bot yourself, Assistant ID: 1749933230652x552003326730567700

39 comments