Create a support ticket
Tell us what went wrong and a human on the support team will pick it up. Every ticket is acknowledged within one business day. If your request is about a specific API call, include its request ID — it is the fastest way for us to find it.
Three checks that solve most tickets
Worth thirty seconds first — if one of these answers it, you never have to wait for a reply at all.
Check the status page
Per-component health for the gateway, dashboard and providers, with incident history. If something is already a known incident, it is posted there first.
View service statusSearch the docs
API reference, SDKs and step-by-step guides — routing, caching, headers, limits and error handling are all written up.
Browse the docsRead the Help Center
The situations support sees most often, each solved in a paragraph. Yours may already be answered there.
Visit the Help CenterTell us what happened
Tickets go to support@nrouter.ai and are triaged by a real engineer. Signed in to the dashboard already? The in-app support drawer reaches the same team.
From send to a human reply
No ticket numbers disappearing into a portal — the thread continues over email, with the team that runs the gateway.
You send the ticket
It lands in the support inbox with its category and request ID attached — structured, not a bare email — so nothing has to be asked twice.
An engineer triages it
The category and request ID route yours to the right engineer. A request ID lets us pull the exact call before replying, instead of asking you to reproduce it.
You get a human reply
Within 1 business day, from someone who works on the product — no script, no first-line queue. Enterprise plans get priority handling with a named contact; the Help Center sets out the tiers.
Not a support question?
Sales, security, legal and privacy each have their own inbox and their own response commitment — the contact page routes you to the right one in one place.