General questions
founder@ytpanel.clickUse this for product questions, access issues, bugs, and ideas for improving the service.
Data and privacy
founder@ytpanel.clickUse this for deletion, correction, export, or personal data processing requests.
Partnerships and implementation
founder@ytpanel.clickFor team onboarding, integrations, white-label scenarios, and custom reporting discussions.
How to write in a way that helps us faster
A short subject line with the request type works best: bug, billing, privacy, or partnership.
Inside the email, include the channel or workspace link, the account email, the steps where the issue occurred, and the expected result. That usually saves one or two clarification rounds.
If the issue involves security or access, avoid sending sensitive data in plain text. A symptom description and a safe way to continue the conversation is enough.
Common contact questions
What should I include in the email?
Describe the workspace, account email, reproduction steps, and attach a screenshot if the issue is related to a UI error.
When should I expect a reply?
For general requests, the target is within two business days. For critical access or security issues, mark that clearly in the subject line.
Is there a support form?
Not yet. Email is the main communication channel for now. When we add a support form or help center, it will appear on this page.