Why notes on test accounts don’t get written
- Typing breaks the test. You’re halfway through a sign-up flow with a code about to expire; stopping to write “DOB set to 2012, verified, stuck at checkout” feels like a detour.
- The context fades fast. Two days later nobody remembers which address was the youth account on staging, or which one already has a subscription.
- Hand-offs suffer. A teammate picking up your test accounts has addresses and personas, but not the story of what you did with them.
Speaking a note takes a few seconds, so it actually happens.
How it works
Wispr Flow is a dictation app for Mac, Windows, iPhone and Android. You hold a key, speak, and it types cleaned-up text wherever your cursor is: filler words removed, punctuation added, lists formatted.
- Install Wispr Flow and finish its setup.
- In Proxy Mail QA, click an address on the Accounts page to open its details, then click into Notes.
- Hold the Flow key (Fn on a Mac, Ctrl + Win on Windows, by default), say your note, and let go. The text appears in the Notes field.
- Click away from the field. The note saves on its own.
The same works for an address’s Label, which shows on its row: say “Checkout test, staging” and it’s there.
What to say
A note that answers four questions is enough for anyone to pick the account up later:
- What it’s for: “Youth account for the age-gate tests.”
- Where: “On staging.”
- What state you left it in: “Email verified, date of birth set to 2012, no subscription.”
- What you found: “Checkout fails when the postcode has a space. Logged as bug 482.”
You can say it all in one breath, filler words and all. Flow tidies it into something like:
Youth account for the age-gate tests, on staging. Email verified, date of birth set to 2012, no subscription. Checkout fails when the postcode has a space; logged as bug 482.
Tips for QA teams
- Teach Flow your words. Add product names, environment names and ticket prefixes to Flow’s personal dictionary so they’re spelled right every time. Flow can share a dictionary with your team.
- Use a snippet for your note template. A Flow snippet expands a spoken shortcut into saved text, such as a “For / Where / State / Found” skeleton you then fill in by voice.
- Dictate the bug report too. The same key works in your bug tracker and in Slack, so the note on the account and the ticket it links to are written the same way.
- Keep passwords out of notes. Put them in the Saved password field instead.
Privacy
Proxy Mail QA is for test accounts only, so notes should never contain real people’s personal data. That matters doubly with dictation: Wispr Flow processes what you say on its own service. Wispr says it is SOC 2 Type II and ISO 27001 certified, and lets you choose whether your data helps improve Flow (Settings → Data and Privacy). Check your company’s policy on dictation tools before you start.