Support

Send us a message

Tell us what happened and we will come back to you. Everything here reaches the same place.

Or email us directly

Email info@swisslogisticsconsulting.com. We aim to reply within two working days. Privacy requests are answered within 30 days — put “Privacy request” in the subject line.

What to include

• The route request you typed, word for word, and what you expected instead.
• Where you were using NoMap: the website, the Command API, or the NoMap Router connector in ChatGPT, Claude or another assistant.
• The approximate time, so we can find the request in our logs.
• A screenshot if something looked wrong on screen. Please leave out anything confidential.

Common answers

A place was not recognised. NoMap will not invent a UN/LOCODE. If the catalog cannot identify a place it says so and offers candidates — pick one, or name a nearby port or terminal. Tell us which place is missing and we will look at adding it.

A leg came back on a different mode. When no corridor can be calculated for the mode you asked for, the reply names the mode actually used. The distance belongs to the mode shown, not the one requested.

The figures look approximate. They are. Distances, durations, emissions and cost bands are planning estimates from published network data and stated assumptions — an overview, not navigational advice, and not a freight quote.

The connector is not responding. Calls are limited to 30 per minute per client, and rendering a map card can take up to a minute. If it stays unavailable, tell us the time and the request.

Documentation

The Command page documents both the public Command API and the NoMap Router connector: the tools, what each returns, and what NoMap deliberately does not do.

Reporting a security problem

Email the address above before disclosing anything publicly, and we will work with you on a fix and a timeline.