DTMF verification and microphone audio feedback issues
Problem
User encountered barriers when attempting DTMF verification; microphone failed to capture own audio, and post-registration functionality was unclear, preventing continued use. Despite UI/UX praise, technical obstacles hindered the experience.
Pain points
- DTMF verification code input failed due to device microphone not capturing own audio
- No clear expected functionality after registration; user uncertain if WebRTC P2P voice number is provided
- Hidden interaction patterns (e.g., *#06#) undocumented, causing user confusion
Questions to verify
- Was the user able to successfully pass DTMF verification? Was microphone audio capture a hindering factor?
- What is the expected functionality after registration? Was a WebRTC P2P voice number obtained?
- Does the product provide guidance or documentation to help users discover hidden features like *#06#?
Evidence
quote · @anonymous
I couldn't get past the DTMF captcha. My device's microphone didn't listen to its own audio and I was lazy to get a second device.Did anyone register? What happens after, do you get a sort of WebRTC P2P voice number? I like this UI/UX a lot but no idea what this is haha
quote · @anonymous
Not sure what I just registered for but hope it's cool
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.