Product name and screen or workflow affected
Useful help starts with the right detail.
Get assistance with an application, account, deployment or integration. We want to understand the problem clearly and resolve it without unnecessary back-and-forth.
Choose the best starting point.
Include the product name and the organisation concerned so we can route the enquiry.
Application assistance
Help with sign-in, feature use, permissions, data or unexpected behaviour.
Email us ↗02Technical integration
Discuss authenticated APIs, device connectivity, webhooks and data flows.
Email us ↗03Deployments and pilots
Arrange initial setup, staff orientation and controlled rollouts.
Email us ↗04Security and privacy
Report a potential security issue or ask about handling sensitive information. Do not include secrets in the first email.
Email us ↗A few details make troubleshooting faster.
You do not need to send passwords, panel codes, private keys or sensitive incident records.
Organisation, approximate incident time and timezone
Device type, operating system and browser or app version
What you expected to happen and what actually happened
Exact error text or a redacted screenshot where available
Whether the issue affects one user, a device or the whole team
Practical checks before you raise a ticket.
Some issues can be narrowed down immediately.
I cannot sign in. What should I check?
Confirm the correct product address and organisation, check connectivity, and follow your organisation’s authorised password or MFA recovery process. Never send credentials by email.
The application seems to show an older page.
Try a hard refresh and confirm the deployed application version. If the issue persists, share the affected URL and browser version.
A mobile or offline feature is not behaving as expected.
Record the app version, online/offline state and whether work is pending synchronisation. Avoid uninstalling or clearing app data until recovery options have been assessed.
Can I send a screenshot?
Yes, but remove passwords, personal details, sensitive operational information and any access codes before attaching it.
How are feature requests handled?
Describe the affected role, the current workflow, desired outcome and practical impact. That helps separate a usability issue from a new development requirement.
We’re ready to review your enquiry.
Use the dedicated support subject so the product and issue are clear from the start.
