Technical Support
Technical Support
Technical and project support for NexaQore customers—clear channels, escalation into product and services, and guidance that respects regulated workflows.
When something blocks the floor—access, integrations, unexpected behavior—you need a path that owns the issue. Technical Support works with product and services so tickets do not bounce between teams.
Channels
- Email — sales@nexaqore.ai (support routing; dedicated support inbox available as your account matures)
- Services conversation — book a call for project-level or multi-ticket escalations
- Portal — customer support login is on the roadmap; until then, email and services contacts are the primary path
What to expect
- Business-hours response for standard requests; critical-path issues escalated faster
- Clear ownership and status—not a generic SaaS script
- Guidance that respects Part 11 workflows, change control, and audit trails
- Handoff to Flex for configuration work and to Implementation for project scope
When to use Support vs Flex
- Technical Support — outages, defects, access, unexpected platform behavior
- Flex / Care Program — planned config changes, admin backlog, master-data maintenance, small enhancements
Related
Ongoing configuration belongs in Customer Care Program (Flex). New environments start with Implementation.