Notifications and support
Follow workspace messages, open support requests, and continue previous conversations.
Console keeps product messages and support conversations inside the signed-in workspace. Use notifications for events that need your attention and support for a conversation with the Flova team.
Read notifications
Open Notifications from the Console navigation. Notifications can cover plan status, quota usage, payment, and support. A new notification has a New marker. Select View when the message links to billing or another page, then mark it read. Use Mark all as read for the remaining messages.
Notifications are workspace scoped. If an expected message is missing, check that you are in the workspace where the event happened and move through the notification pages.
Open a support request
- Open Support.
- Enter a short subject.
- Choose a category: billing, account, device and firmware, technical issue, or other.
- Describe what happened, the device or template involved, and the action that led to the problem.
- Add an attachment when a log or screenshot helps.
- Send the request.
Keep API keys, Client Secrets, passwords, Wi-Fi credentials, and activation codes out of the message and attachments. Share the device name, template name, timestamp, and safe diagnostic details instead.
Continue a conversation
The Support page lists your workspace's requests with their category, last update, and status. Open a request to read the full conversation and attachments. Reply from the same page when support asks for more information.
The status tells you who should act next:
| Status | Meaning |
|---|---|
| Waiting for support | Flova support will review or answer the request. |
| Waiting for your reply | Add the requested details to continue. |
| Resolved | The request is closed. Sending another message reopens the conversation. |
Write a useful report
Include the exact Console page, the template or device name, the time of the failure, the visible error, and what you expected to happen. For telemetry issues, include the channel's technical key and whether the device was online. For OTA issues, include the release version, rollout status, and the affected device result.
Support can investigate a clear timeline more quickly than a general report such as "it does not work". Do not send secrets while providing that timeline.
For setup and device behavior, also see Quick start, Devices, and Live monitoring.