A useful support request says what you tried, where you tried it and what happened. Start with the app version, platform and the feature involved rather than sending an entire private workspace.
A precise description usually helps more than a large unreviewed bundle of private data.
Provide a reproducible description
Explain the steps in order and quote the visible non-sensitive error when relevant. Say whether the problem concerns capture, a local model, an alert or a store response. Those use different systems, so a narrow description helps support investigate the right one.
Keep sensitive material out
Do not send provider keys, passwords, verification codes or a full plain JSON export just to explain a screen problem. Use a harmless example or a redacted screenshot when appropriate. Contact hello@lasyaaitech.com through your chosen mail app; support communication is separate from automatic in-app sending.
Choose optional services deliberately
Describe one concrete attempt in a support message: which platform and version you used, which feature you opened, what you selected and what non-sensitive result appeared. For a reminder issue, include the reviewed schedule and relevant permission state rather than an entire private document. For a model issue, identify the selected mode and visible readiness result without exposing provider credentials. A harmless example can be more useful than a large export containing unrelated records. Review any screenshot for private content before attaching it. This gives support enough information to understand the failing step while keeping your request focused on the app behavior you observed, rather than sharing sensitive material that is not needed to investigate it.
One step at a time.
- 01
Note the platform, app version and feature you used.
- 02
Write the shortest steps that reproduce the issue.
- 03
Include only non-sensitive error details or a safe example.
- 04
Send your reviewed request to hello@lasyaaitech.com.
A little reference.
Keep the context and your next action together.
| Choice | Use it for | Check before saving |
|---|---|---|
| Useful context | Platform, version and steps | Keep it specific |
| Private information | Keys, passwords and personal records | Do not include casually |
| Safe example | A harmless reproduction | Use instead of full workspace |
Should I email my API key to prove AI is failing?
No. Users do not need to share provider keys. Describe the selected mode and visible error without exposing credentials.
These guides explain product workflows. Review extracted names, dates and amounts. Features depend on your device, permissions and optional service setup.
A little more clarity, in your pocket.
Bring your next screenshot, document or voice note to OneTap Life.
Find your app