Support
Support pathways before the customer portal exists.
Use this static page to route sales, onboarding, technical support, and incident escalation conversations without creating a public ticketing system.
Support pathways
Static routes for the first support conversations.
Each pathway uses the public contact route until authenticated account management and ticketing are designed later.
Prospects and executive sponsors
Sales And Deployment
Use this path for private intelligence fit, pricing, deployment discovery, and buyer questions.
- Discuss sales, buyer fit, sector constraints, and deployment readiness.
- Keep sensitive detail out of public website messages.
- Agree secure support channels during onboarding.
Deployment sponsors and administrators
Onboarding
Use this path for early onboarding, source scoping, user roles, matter design, and handover planning.
- Discuss setup sequence, training expectations, source boundaries, and operational owners.
- Keep sensitive detail out of public website messages.
- Agree secure support channels during onboarding.
Technical reviewers and operational owners
Technical Support
Use this path for appliance host planning, local HTTPS, storage, model runtime, connector scope, and maintenance questions.
- Discuss technical context without sending logs, secrets, documents, or regulated data through the public site.
- Keep sensitive detail out of public website messages.
- Agree secure support channels during onboarding.
Named customer contacts
Incident Escalation
Use this path for urgent routing expectations before a future authenticated ticketing system exists.
- Share high-level urgency and contact details only; keep incident evidence and sensitive data in approved secure channels.
- Keep sensitive detail out of public website messages.
- Agree secure support channels during onboarding.
Support boundary
What this public support page does and does not do.
- Customer portal coming later; this static website does not authenticate customers.
- Support ticketing coming later; this static website does not create tickets or persist support cases.
- Do not submit secrets, patient data, client files, matter details, investigation evidence, or regulated records through the public website.
- Approved secure channels should be agreed during onboarding for sensitive support exchanges.
Boundary
No public ticketing or sensitive submissions.
This public website provides product information and support routing only. Do not submit confidential client, patient, case, investigation, student, regulated, or commercially sensitive data through this public website.