Contact
Operations, bugs, data requests, and collaboration inquiries
Use this channel for service operations, account issues, export errors, privacy requests, and collaboration inquiries. Clear reproduction steps and screenshots are more useful than a long description, so include the role you were using and the exact point where the issue occurred.
Support email
mow.coding@gmail.comThis inbox handles both product operations and development support. Do not paste raw sensitive response data directly into the message body.
Best uses for this channel
- Research-admin sign-in or access-control issues
- Participant enrollment or survey-response flow errors
- ZIP/CSV export, SkillBook, or AI feature problems
- Privacy, deletion, or anonymization requests
- Special-template, migration, or collaboration requests
Quick mail drafts
FAQ
What should I include in a support email?
Tell us which role you were using, which page failed, the reproduction steps, the expected result, and the actual result. A screenshot usually shortens the debugging loop.
Can I email raw survey response data?
Normally, no. Start by describing the issue and the minimum sample needed. If data review is necessary, send only the smallest safe and de-identified sample first.
Do bug reports and feature requests use the same channel?
Yes. Use the same email, but prefix the subject with tags like [Bug], [Feature], or [Access] so triage is easier.
Can I use this channel for collaboration or custom work?
Yes. Special-template requests, migration requests, and collaboration proposals all use this email channel.