What Loquora Customers Tell Us — And How We Respond
We build Loquora on real support conversations — not assumptions about what users need. Over the past week, two customer conversations show especially well what problem the product solves, and where there's still room to grow.
When English is the problem, not the solution
One customer described a situation familiar to many international teams: the working language with colleagues in China is English, but that's exactly where most misunderstandings happen. Neither side speaks it natively, and in that situation you lose precisely the nuances that usually cause work conflicts. It would be nice to sometimes switch to direct communication — in Chinese.
That's exactly what Loquora was built for: translation happens directly between the source and target language, with no English layer in between. Russian↔Chinese is one of 32 supported language pairs, available just like any other.
The same customer's second scenario was different: being present at a Russian-language meeting for the benefit of English-speaking colleagues, and getting a real-time translation without speaking into the conversation yourself — just following along. For that you don't even need a voice clone: Loquora lets you turn on subtitles only — a live text translation of incoming speech overlaid on your screen, with no dubbing. That, by the way, is already available on the free plan.
Day-one delight — and what happens when something breaks
The second conversation was honest, and a little painful for us. The customer paid for a subscription, cloned their voice, tested it on a short call — and was thrilled: in their words, they hadn't paid for a subscription with that much pleasure and zero regret in a long time. Then, the very next day, after updating the desktop app on Windows, they ran into a recurring error that kept breaking calls one after another.
That's exactly the price a fast-growing product pays: the more often updates ship with new features, the higher the chance of hitting an unexpected edge case on someone's specific setup. We don't treat that as something to just accept — over the past week we closed a whole series of infrastructure issues: a race for the microphone on manual call start that made the app stop listening with no error in the logs, audio capture behavior when the main window is minimized to the background, and we noticeably increased the resilience of the translation engine itself — with automatic failover to a backup model if the primary provider has an outage.
This particular customer's issue is already fixed. But the principle matters more: we'd rather these things never surface at all — and we keep closing them as fast as we can.
If you've had a similar experience — good or bad — tell us. Feedback sent right from the app reaches the team instantly, and it's exactly what decides what we work on next week.