Support
Execution-first support.
We keep workflows healthy with clear response paths, practical guidance, and escalation routes that match the kind of issue you are facing.
Where to send what
Pick the category that matches your problem first. That usually gets you to the right queue faster than a general message.
Getting started
Setup and onboarding
Use this path when you need help understanding the product, setting up a pilot, or preparing your team for rollout.
Day to day
Workflow issues
Use this path when a task, approval, or visibility problem is preventing someone from completing their work.
Access and data
Data or permission questions
Use this path when the issue is about roles, visibility, imports, exports, or the shape of the canon data.
Highest priority
Security or incident reports
Use this path for suspected vulnerabilities, data loss risk, or anything that may need an urgent response.
Resolution path
How a request moves through support.
We acknowledge the request
We confirm receipt, classify the issue, and make sure the right context is captured before work begins.
We diagnose the root cause
We review the workflow, the data, or the permission model to find the place where the process started to break down.
We close the loop
We explain the fix, share any follow-up steps, and note whether a process change is needed to prevent the issue from repeating.
What to include
A better first message saves time.
- The role or user group affected.
- The workflow that stopped working.
- Any screenshot, timestamp, or error text you saw.
- Whether the issue is blocking a daily task or just causing confusion.
Frequently asked questions
What if I am not sure where to send my request?
If in doubt, send it to hello@nagu.co. We will route it internally and make sure the right person sees it.
Can I use the contact page for a demo request?
Yes. The form and the email address both work for demo requests, partnerships, and general evaluation questions.
How should I report a security issue?
Send the issue directly to security@nagu.co and include the steps to reproduce, the affected page or workflow, and any evidence you have.