Email a person who works on VoiceSnap Pro
Bug reports, licensing, refunds, compatibility, and every “will it work with…” question. All of it goes to one inbox, and a person reads all of it.
How to reach us
Email is the only support channel, deliberately. It keeps the whole history of a problem in one thread, it works across timezones, and it doesn't make you create an account just to ask a question.
Bug reports, refund requests, licence questions, feature ideas, accessibility questions and press enquiries all land in the same place. There is no wrong address to pick.
Support inbox
support@voicesnap.proWhat to expect after you hit send
Usually within one business day
Most emails get an answer the same day they arrive. Write on a Saturday and realistically you'll hear back on Monday — we'd rather set that expectation than promise a number we can't hold to.
A person, not a ticket queue
There's no chatbot in front of the inbox, no case number to quote back at us, and no first-line script standing between you and an answer. Your email reaches the person who builds the part you're asking about.
Bug reports get a straight answer
If you report something reproducible, we'll tell you which it is: fixed, queued for a specific release, or something we've decided not to do. Silence isn't one of the options.
Right now, most mail is about launch
VoiceSnap Pro hasn't shipped yet, so today's inbox is mostly compatibility, licensing and “will it do X” questions. Ask them freely — pre-launch questions genuinely change what gets built.
What to put in a bug report
A dictation bug is one of two things: the words came back wrong, or the right words never reached your app. These eight lines tell us which — and turn most reports into a same-day fix instead of a week of clarifying questions.
01Your OS and its version
For example macOS 15.3 or Windows 11 23H2. On a Mac: Apple menu → About This Mac. On Windows: Settings → System → About.
02The VoiceSnap Pro version
It's in the app's settings panel. “The latest one” isn't a version number, and the exact build tells us straight away whether you've hit something already fixed.
03The app you were dictating into
Be specific: “the Slack desktop app”, not “Slack”; “a Chrome tab with Google Docs open”, not “the browser”. Text insertion behaves differently in native windows, Electron apps, browser tabs and remote sessions, so this line narrows it fast.
04Which microphone you were using
Built-in laptop mic, wired headset, AirPods, USB microphone — and whether the device connected or switched part-way through the session, which is a bug class of its own.
05What you said, and what appeared
Paste both lines verbatim, including the parts that came out right. The gap between the two is the actual report, and guessing at it from a paraphrase never works.
06Whether the dictation is in your notes library
This one line splits the problem in half. If the note is there but your field stayed empty, transcription worked and insertion was blocked — usually a permissions problem rather than a speech one.
07How often it happens
Every time, sometimes, or once. If you've found a way to make it happen on demand, write down the steps — a reproducible bug is nearly always a fixed bug.
08The language you were dictating in
Only worth mentioning if it wasn't English, but when it matters it matters a lot: it changes where we start looking.
Paste this into the email and fill it in
OS and version: VoiceSnap Pro version: App I was dictating into: Microphone: Language: What I said: What appeared instead: Is the dictation in my notes library? yes / no How often: every time / sometimes / once Steps to reproduce:
Screenshots help. Please don't send audio recordings of confidential material — the two text lines are more useful anyway.
Faster than an email
Three places that answer most questions before you have to write one.
Documentation
Setup, keyboard shortcuts, dictating in other apps, punctuation and formatting, voice commands, custom vocabulary, the notes library, microphone setup and a troubleshooting page.
Read the documentationFAQ
The questions that come up most: permissions on macOS, offline use, languages, what happens to your audio, what the one-time licence covers, and why a password field is off limits.
Read the FAQFree browser tools
Word counter, filler-word remover, transcript cleaner, subtitle converter and a speech-time calculator. All of them run in your browser, with nothing to install and nothing uploaded.
Open the free toolsWhat VoiceSnap Pro can't do yet
Better to read this here than to discover it on a deadline. Every item is a real constraint today, not a hedge.
There's no offline mode at launch. Transcription runs on servers, so dictation needs an internet connection.
macOS and Windows only. There is no iOS, iPadOS, Android or Linux build, and none is planned right now.
Password boxes and credential prompts can't be dictated into. Both operating systems block text insertion into secure fields, and we won't be working around that.
macOS asks for three permissions before your first dictation: Microphone, Accessibility and Input Monitoring. Miss one and the text won't reach your app.
Some remote-desktop and VM clients filter synthetic input, so text may not cross into the guest session. Dictate locally and paste across if yours does.
It's one-speaker, push-to-talk dictation. VoiceSnap Pro doesn't join calls, record meetings or separate speakers.
Nothing is downloadable yet. VoiceSnap Pro is pre-launch, so support today means questions and answers, not installers and licence keys.
This list gets shorter as things ship. If something here is a blocker for you, say so in an email — it's the clearest possible signal about what to build next.
Want to know when it ships?
Leave an address and you'll get one email on release day, with the founding price. No newsletter, no drip sequence, and your address isn't shared with anyone.
One launch email. No newsletter, no sharing your address.