Support

Support

How to reach a Coneqt engineer, what to send with a ticket, and how issues escalate — for live deployments and evaluations alike.

Last updated · 4 September 2026

Fastest for live issues

Support portal

Raise a ticket against a site, machine or user account. Your deployment engineer sees it directly.

Best for questions

Email

For configuration questions, report requests and anything that is not stopping production.

Line-down situations

Phone

Existing customers can call the number in the support portal when data has stopped and production is affected.

Support by tier

Every subscription includes support. The level attached to your tier is Standard on Basic, Priority on Professional and Dedicated on Enterprise.

Dedicated support means a named engineer who knows your plant. Response targets and any hours of cover are confirmed in your order form rather than promised on this page.

What to send with a ticket

The more of this you include, the faster it resolves:

The site and the specific machine or asset ID.
What you expected to see and what you actually saw.
When it started, and whether anything changed on the line or the network.
A screenshot of the dashboard or report in question.
Whether production is currently affected.

How issues escalate

Tickets are triaged on impact. Anything where data has stopped arriving from a live machine, or where a dashboard is materially wrong, is treated ahead of configuration and reporting requests.

If a ticket is not moving, ask for it to be escalated — that is a legitimate request and it reaches a lead engineer, not a queue.

Connectivity and edge behaviour

If the cloud link drops, edge components keep recording and resynchronise when the connection returns. A gap on a dashboard during an outage usually fills in by itself once the link is back.

If the gap does not fill within a reasonable period after connectivity returns, raise a ticket — that is not expected behaviour.

Adding machines, users and sites

Adding a machine is a support request, not a project. Licensing follows the per-machine, per-month model, and the new asset appears once it starts sending data.

User management is in the product on every tier. Site-wise dashboards and multiple sites require Enterprise.

Planned maintenance

We give reasonable notice of planned maintenance and schedule it to avoid disrupting monitoring wherever possible. Edge recording continues during platform maintenance.

Not yet a customer?

Evaluations get the same engineers. Tell us what you are testing and we will help you get a line reporting properly.

Start with one line. Scale to the whole network.

A two-week pilot on a single line, on your data, with your team. No rip-and-replace and no new hardware in most plants.

We use only what this site needs to work, plus aggregate traffic counts. No advertising trackers, and we do not sell audience data.