Contact support and report bugs
Reach a person at IoTFlows, request training, and file a bug or a feature request.
Support runs on two channels. Email support@iotflows.com for anything needing a reply, an attachment, or an account change. The feedback popover in the dashboard header sends a note without leaving the page, but it is one way.
Contact support
Email support@iotflows.com. Locked out instead? See Sign in to IoTFlows.
To send a note from the dashboard:
- Select the feedback icon in the header, to the left of the settings gear.
- Type your note in Feedback / Feature Request.
- Select Send Feedback, then wait for the confirmation "Thanks for your feedback".
IoTFlows records the page you were on.
Waiting on an answer? Use email. The popover opens no reply thread and takes no files, and its icon is hidden on narrow screens.
Request training
Email support@iotflows.com to book onboarding or training. Name the products your team uses, how many people attend, and which shift they work, so the session lands on their shift.
Report a bug
- Reproduce the problem once and note the exact time.
- Email
support@iotflows.comwith every row of What to include that applies. - Attach a screenshot. Attachments go by email; the popover takes text only.
Always include the timestamp and your organization timezone. Most reports about a wrong number resolve to a shift boundary, and support cannot check that without both. See Set shifts and your organization timezone.
Request a feature
Send feature requests through the feedback popover, which is titled Feedback / Feature Request. Describe the problem you are trying to solve rather than the feature you have in mind. You do not need to email the request as well.
What to include
| Report type | Include | Why |
|---|---|---|
| Every report | Organization handle, and your client: web, iOS, or Android | One account can see several organizations, and behavior differs per client |
| A number looks wrong | Asset name, timestamp with timezone, the shift and date selected | Support replays the window you were looking at |
| A machine reads offline | Asset name, device serial, when it last reported | Separates a dropped network from a stopped machine |
| Someone cannot see a page | Their email, their role, the page | Most cases are a role gate, not a fault |
| Feature request | The problem, and how often it costs you time | Frequency orders the queue |