01 / Contact the team
Choose the right conversation
For evaluating Flowboard, discussing an agency workflow, partnerships, or company questions, email hello@flowboardhq.com. For a bug, account issue, feature request, or help with setup, email support@flowboardhq.com. If you want a product walkthrough, explain the workflow you would like to see and include your timezone.
Product and general inquiries
Describe your agency, the workflow you are evaluating, and the decision you need to make.
Write an email ↗Product support
Include the workspace context, the action you attempted, and the result you observed.
Write an email ↗02 / Contact the team
For a product or migration question
Mention the size of your internal team, the kinds of client work you deliver, and the systems involved in the current process. Explain what you need to preserve, such as task ownership, historical time, client files, or a specific approval interaction. These details make it easier to identify a real fit or a limitation early.
For migration, name the source tool and the types of records you want to move. Review the migration guide first, since import coverage differs by source and does not include every historical record. Do not email an access token or password. If a supported import needs authorization, use the appropriate in-product process.
03 / Contact the team
For a problem in the application
Include the workspace name, approximate time of the problem with timezone, the page or feature involved, and the steps that led to it. Describe what you expected and what happened instead. If a message appeared, include its wording. A sanitized screenshot can help when the issue depends on the visible interface.
Avoid sending passwords, authentication tokens, payment-card information, or unrelated client data. Redact sensitive material from screenshots and examples. If several teammates are affected, say so; if the issue appears limited to one action or browser, that distinction is also useful.
- What action were you trying to complete?
- What result did you observe?
- When did it happen, and is it still reproducible?
- Which people or projects appear affected?
04 / Contact the team
Get help with an availability issue
Report the issue to support with its time, scope, and the action that failed. The status page is updated manually, so please report a problem even if it has not appeared there yet. For an interrupted payment or import, check whether the expected record already exists before trying again.
Keep replies about the same issue in one email thread so the steps, screenshots and updates stay together. If the issue changes, reply with what works now and what still fails. Tell us whether teammates are seeing the same behavior and whether the problem is blocking a deadline or a client-facing task.
Report a service problem
Find the details that help us investigate an availability issue.
Explore this workflow ↗THE PRACTICAL DETAILS
Questions, answered.
What if the email button does not open?
Copy hello@flowboardhq.com or support@flowboardhq.com into your usual email service. The buttons use your configured email application, so they may not open a draft if you have not set one up on this device.
Can I request a demo or walkthrough?
Yes. Email hello@flowboardhq.com with the workflow you want to explore and your timezone. Mention the size of your team, the tools you currently use, and the part of your process you would like to see in Flowboard. We can arrange the walkthrough by email.
What should I include in a bug report?
Include the workspace context, approximate time and timezone, the steps you took, expected behavior, and actual result. Add a sanitized screenshot or error message when useful. Keep credentials and unnecessary client information out of the message.
Where should a security question go?
Email support@flowboardhq.com with the requirement or concern. The security page covers available controls and access settings. Describe any specific procurement or client requirement in your message so we can address it directly. Keep credentials and private client records out of the initial email.