Support Resources
Support resources for teams operating NexorONE®: Support access, documentation, videos, and structured channels for incident and change management.
For security and governance, access to detailed materials is typically restricted to authorized stakeholders.
Contact Support
The Support page is the primary channel for submitting tickets and requesting specific documentation packages.
What Support Covers
- Platform guidance and troubleshooting
- Incident triage and escalation
- Configuration and operational support
- Change requests and release coordination
- Documentation alignment to deployed scope
Support is delivered within agreed scope and governance. The regulated institution remains responsible for compliance and operations.
Open a Ticket
Submit incidents, questions, and requests with structured details for faster triage.
- Issue category and priority
- Environment (sandbox / prod)
- Steps to reproduce / evidence
Track Progress
Receive updates, assigned owners, and receive ticket resolution notes.
- Status and next actions
- Attachments and audit trail
- Release notes (when applicable)
Access Resources
Authorized users can access deployment-specific documentation and secure technical packs.
- Admin/user guides
- Integration documentation
- Change and release references
Documentation
Documentation is maintained as a general framework and may vary depending on your deployed scope, enabled modules, and governance requirements. For security, the most detailed materials are shared through authorized channels.
Operational Guides
- Administrator workflows and configuration
- User-facing workflows and navigation
- Reporting, exports, and audits
Technical Packs
- Environment notes and endpoint catalogs
- Integration policies and token guidance
- Change control and release notes
Support Videos
Short walkthroughs can accelerate operational knowledge and reduce onboarding friction.
Admin Basics
Common admin workflows: profiles, accounts, requests, reporting, and configuration patterns.
User Basics
User workflows: accounts, transactions, statements, messaging, and profile management.
How Support Works
Support is most effective when tickets include the right context. Below is the recommended structure for submitting issues.
For Incidents
- Environment: sandbox / staging / production
- Timestamp and user/account identifiers (non-sensitive where possible)
- Steps to reproduce + expected vs actual behavior
- Screenshots/log snippets (redact secrets)
- Business impact and urgency
For Requests / Changes
- Goal and scope (what success looks like)
- Modules affected and approval owners
- Compliance / policy considerations
- Desired timeline and rollout plan
- Testing and acceptance criteria
Avoid sending passwords, private keys, or full sensitive datasets. If sensitive evidence is required, we’ll provide a secure method for transfer.
Security & Responsible Reporting
If you believe you have found a security issue, report it responsibly with minimal exposure. We will coordinate investigation, mitigation, and communication within the agreed governance framework.
What to Include
- Clear description of the issue and affected component
- Steps to reproduce (safe and minimal)
- Impact assessment (what could happen)
- Evidence (redacted) and environment details
What Not to Send
- Passwords, private keys, or secrets
- Full customer datasets
- Unnecessary personal data
Operational Reminder
Strong security depends on correct configuration, access governance, and continuous monitoring. If you need a security review for your deployment, request a scoped session.
Support FAQ
Common questions from operations, compliance, and technical teams.
Need onboarding help? Request an operational walkthrough for your team.
Request Demo Contact SupportContact Support
Include issue details as well as steps to reproduce. You will receive a unique ticket number for further tracking.