Talk to the people who built it.
Two routes, so a network emergency does not queue behind a pricing question. Both reach the team that writes the software.
Technical support
[email protected]A router that will not enrol, a reading you do not believe, a bill that does not match what the network did. Anything where the product is in front of you and not behaving.
Include the router identity and the RouterOS version if you have them — it is almost always the first thing we ask for.
Other enquiries
[email protected]Evaluating HELIX NMS+ against your own estate, migrating from Splynx, account and billing questions, partnerships, or anything that is not a device misbehaving.
If you are evaluating, the size of your fleet and which RouterOS versions you run tells us most of what we need.
Already running it?
Most things are faster from inside the console, where the request arrives with the device, the tenant and the log line already attached to it.
Privacy, terms and data requests
Enquiries about the privacy policy, the terms, or a request concerning your own data go to [email protected], which is the address named in both documents.
HELIX NMS+ is published by Helix Cloud Solutions.