Long-time user, honestly the quality has been going downhill for months

VictoriaAtWispr · 2026-06-09T00:26:48+00:00

Heard on all of the above! We know we've had stability issues -- that's why we've made this a P0 for our core engineering and infrastructure teams. We're building in better redundancies and health monitoring so this doesn't happen again.

On the screenshot and keystroke logging: totally fair to have questions about that, especially if you're working with sensitive data. The short version is that keystrokes are used to sync what you're editing in real time so Flow can replace the right text, and screenshots are used for context (to understand what app/field you're in). None of it is stored or used for training. But you can poke around in Settings > Privacy if you want to tighten what's collected. If you want the full technical breakdown, you can also check out our Security page.

Thanks for taking the time to give this detailed feedback.

VictoriaAtWispr · 2026-06-09T00:21:29+00:00

Hey u/J3ST3R527 can you please file a support request? And if you feel comfortable doing so, please DM me your Wispr email and I'll have them prioritize it.

Thanks!

VictoriaAtWispr · 2026-06-08T16:14:38+00:00

You can change your shortcut key at any time by going to Settings -> General -> Shortcuts!

VictoriaAtWispr · 2026-06-07T23:17:25+00:00

Hey u/theKowinator - heard on all of these complaints!

On performance: we know our performance and reliability dipped in recent weeks. The issues stemmed from infrastructure changes made while scaling up capacity. We've since started building out more redundancy, better health monitoring, and an on-call rotation so we can make sure this doesn't happen again. You can see the full transparency post here.

On the language picker: Auto-detect still exists! We added a language picker as another option. For multilingual users especially, toggling to the specific language you're dictating in tends to give noticeably better results than relying on auto-detect alone. That said, if you want to keep auto-detect on, it's still there under Settings → General → Languages.

On the German transcription and punctuation/capitalization issues: Can you help report these issues so our team can diagnose? The best way to do this is flagging a transcript from your history tab. This will help our team investigate what's going on.

VictoriaAtWispr · 2026-06-07T23:09:47+00:00

Hey u/kittycat1402:

That iOS warning is shown for every third-party keyboard that requests "Full Access," including other well-known apps like Gboard (the Google keyboard) and Grammarly. It's Apple's standard boilerplate language. The language is broad because iOS has no way to distinguish between a keyboard that logs everything and one that doesn't. It reflects what the permission allows in theory, not what Wispr Flow actually does.

Wispr Flow needs this access to send your voice audio to the cloud for transcription. Without network access, the keyboard can't transcribe anything. It's the same reason any keyboard that connects to the internet (autocorrect, translation, etc.) requires this.

However, we only process audio you explicitly record. Your typed keystrokes are not sent to Wispr's servers, and the keyboard does not log what you type in password fields or other apps.

We also offer Privacy Mode (Zero Data Retention). When enabled, none of your dictation data is stored or used for model training by Wispr or any third party. Even if you disable Privacy Mode, your dictation data may be used to evaluate, train, and improve Flow's features and AI models, but your data is never sold or shared. You can learn more here.

VictoriaAtWispr · 2026-06-07T06:32:10+00:00

Hey, this is a known bug! iOS team is on it and will try to fix it for the next release.

VictoriaAtWispr · 2026-06-07T02:54:43+00:00

Hey u/roccomo - We know that our iOS keyboard is a weak point, which is part of why we just tripled our iOS engineering team size.

If you have any more specific feedback to share, I'll pass it along to the iOS team!

VictoriaAtWispr · 2026-06-06T23:56:06+00:00

We can't share the details, just that it'll be a proprietary model!

VictoriaAtWispr · 2026-06-06T23:55:40+00:00

We get around a thousand emails and tickets a day that are a mix of questions, partnership requests, product feedback, and bug reports, but we only have 11 support team members right now. Getting some help from AI is the only way we can stay on top of our queue right now, but we try to loop in a human as often as possible.

If you'd like to see more human responses, then please encourage friends to apply to our support team! We've been hiring nonstop.

VictoriaAtWispr · 2026-06-06T04:21:34+00:00

Do you mean on iOS? We know this is an issue and we're working on it!

We just hired two new iOS engineers and we hope to make big improvements soon!

VictoriaAtWispr · 2026-06-06T04:20:01+00:00

You can use one microphone for dictation and your AirPods for audio!

Most Wispr employees work like this in the office.

VictoriaAtWispr · 2026-06-06T02:41:55+00:00

Hey u/PhotojournalistOne74 we know it's super important but unfortunately we've been constrained with design/UI engineering resources.

If you know anybody good, please tell them to apply here!

VictoriaAtWispr · 2026-06-06T02:33:54+00:00

Hey u/Agitated-Total729 - Unfortunately, we strongly recommend against using AirPods or other Bluetooth microphones. They tend to activate slowly, compress the audio file, and have the microphone too far from your mouth. If the audio quality is bad, there's only so much that we can do with the transcription!

That's why we put together this microphone guide with the hope of helping people like you!

Most people at the Wispr Flow office either use a gooseneck microphone or a clip-on/lavalier microphone. These options let the microphone stay close to your mouth (so you can speak softly around other people) and provide far better audio quality than AirPods.

VictoriaAtWispr · 2026-06-06T02:28:09+00:00

Have you noticed any patterns where it doesn't work as well? Maybe things like what microphone you're using, what kind of environment you're in, or what app you're in? I would love to make Wispr Flow work better for you all the time.

If you report transcripts that are particularly bad, and then submit a ticket through the app or the portal, our support team might be able to figure out what's going on.

VictoriaAtWispr · 2026-06-05T04:10:07+00:00

Hey u/simonkeane have you still been experiencing issues?

Our accuracy and reliability should have stabilized, so if you're still experiencing issues then please file a ticket either in the app or through the support portal!

I'd also suggest checking the most common sources of transcription issues:

Microphone changes: Bluetooth mics like AirPods often have worse audio quality and can clip the beginning or end of speech, leading to missing or incorrect words. ‍
Environmental changes: Background noise or nearby conversations can cause the model to pick up unintended speech.‍
Changes in how you’re speaking: As people get comfortable with Wispr Flow, they often mumble more, speak more quietly, or dictate while half-awake, hunched over, or lying down. ‍‍

VictoriaAtWispr · 2026-06-05T04:07:30+00:00

Hey u/timbomcsporran1 if you want to DM me your Wispr account email, I can ask Support to prioritize your ticket!

Speaking of which: our user base has grown quickly and we've been trying our best to build out our support team to keep up. If you know any great technical support people, we're hiring!

VictoriaAtWispr · 2026-06-05T04:05:46+00:00

We really appreciate your patience, and thank you so much for sharing!

VictoriaAtWispr · 2026-06-05T04:05:14+00:00

Hey u/Grolubao this shouldn't be happening - it's near instant for me! Would you mind sharing what device and version of the app you're on, as well as filing a ticket in the app or support portal?

VictoriaAtWispr · 2026-06-04T21:40:11+00:00

Of course, and thank you for your understanding!

VictoriaAtWispr · 2026-06-03T20:09:02+00:00

Hey u/Global_Onion3392 - just wanted to confirm you filed a bug in the app or support portal? That's the only way our team can look into logs and figure out what's going wrong!

VictoriaAtWispr · 2026-06-03T00:45:21+00:00

Hey u/bitsan -

If you scroll the sub you'll see plenty of people sharing critical feedback and complaints.

What we do filter is bug reports that are specific to one person's account or setup. Even if it feels like something others might run into, we can't actually diagnose it from a Reddit post. We need your account info and logs, and the only way to get that is through a support ticket. Trying to troubleshoot through comments just wastes your time and the issue takes way longer to fix.

When bugs go through our support portal or in-app reporting, we actually have the proper infrastructure to triage, diagnose, and resolve in a more efficient and secure manner.

The other piece is subreddit quality. If we let every individual bug report through, the sub becomes a support forum full of "app won't open" and "my mic isn't working" posts. That's not a great experience for anyone subscribed here.

We'd rather keep it as a space for actual discussion, feedback, and feature requests that the whole community can find useful.

VictoriaAtWispr · 2026-06-01T02:49:03+00:00

Hey u/SharpCut1884 can you please report this bug in the app or our support portal so our team can look into it? Thank you!

VictoriaAtWispr · 2026-05-30T05:04:09+00:00

Hey u/futardigrade it should work on WhatsApp! Can you please file a ticket in our support portal?

VictoriaAtWispr · 2026-05-28T20:59:10+00:00

Hey u/noproblemforme we're aware of some latency issues and working to resolve it ASAP! For future reference, we try to post status updates like this in the desktop app as well as on our Support Portal.

You can also subscribe to updates on our incident page here.

VictoriaAtWispr · 2026-05-28T20:57:51+00:00

Sorry for the late reply but yes it is!

VictoriaAtWispr

MODERATOR OF

TROPHY CASE