gonuAdmin: operations & customer requests
Use the platform’s restricted operational pages to investigate accounts, usage and customer requests.
WHEN IT HELPS
Put it to work.
Distinguish a conversion problem, a configuration gap and a failed task before taking an account or billing action.
Before you begin
- Platform administrator access.
- A specific support question and permission to inspect the affected account.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Use Overview, Users, Organizations, Sessions and Devices for account context. Use Usage, AI Costs and Analytics for recorded activity; check metric definitions and date ranges.
Use Conversion funnel and Demo requests for acquisition/sales records. Use Audit Log, Errors, Logs and Health for operational evidence; Feedback and Support hold separate customer requests.
Settings, Security, Feature Flags, Billing, Plans and Coupons can affect product behavior or access. Review the actual form, affected account and confirmation before changing anything.
Admin / Investigation map
THE USEFUL RESULT
What you should leave with.
A more focused investigation and a deliberate, authorized operational action.
Know the boundaries.
- The presence of a dashboard is not a compliance certification or proof that every metric is complete.
- A demo request is an enquiry, not a booked meeting. Empty analytics must remain empty; do not infer users, ROI or successful payments from missing data.
IF SOMETHING DOESN’T WORK
A dashboard is empty or unavailable.
Check admin access, backend availability and the selected date/scope. Use the recorded source data or investigate the API error rather than treating empty counters as verified totals.
Contact support