Static contact
Talk to BlackBox Node without creating a data intake channel.
Use these static contact paths for demo, deployment, pricing, and support enquiries. The public website does not host forms, accounts, tickets, uploads, or appliance controls in Milestone 2.
How to use contact
Keep the first conversation high level.
The contact page is designed for the first commercial conversation only: who you are, the sector you operate in, the kind of deployment you want to discuss, and how we can reply. Sensitive material belongs in approved secure channels agreed later.
Conversion paths
Choose the right non-sensitive next step.
Each action opens an email route. Nothing posts to a hidden backend or creates an account, ticket, payment, or appliance action.
Request Demo
For buyers who want a walkthrough of the private appliance model, sector fit, and current MVP direction.
- Organisation name
- Sector
- Preferred contact details
- High-level deployment interest
Discuss Deployment
For technical or governance reviewers who want to talk through environment, hardware, data boundaries, and rollout shape.
- Target environment
- Approximate user group
- Relevant sector
- High-level governance concerns
Request Pricing
For commercial conversations around placeholder tiers, hardware, onboarding, support cadence, and enterprise scope.
- Likely tier
- Team size band
- Support expectations
- Preferred billing discussion
Support Enquiry
For product website questions, onboarding coordination, and non-sensitive support routing before authenticated ticketing exists.
- Product website question
- Onboarding context
- Non-sensitive issue summary
- Preferred reply route
Contact pathways
Static routing for sales, pricing, support, and incidents.
Prospects and deployment sponsors
Sales And Deployment
Use this route for demo, fit, and deployment-readiness conversations before any client data or appliance access is involved.
- Private appliance fit
- Sector-specific landing page follow-up
- Deployment readiness
- Procurement conversation
Commercial reviewers
Pricing Request
Use this route to discuss placeholder tier fit and commercial packaging without creating a purchase or payment workflow.
- Tier mapping
- Hardware discussion
- Support scope
- Commercial component separation
Early customers and public site visitors
Support Enquiry
Use this route for non-sensitive support routing while the future customer portal and ticketing system remain outside Milestone 2.
- Website questions
- Onboarding coordination
- Guide clarification
- Non-sensitive troubleshooting
Named customer contacts
Incident Escalation
Use this public route only to request a secure incident channel. Do not include logs, secrets, case details, regulated records, or evidence in the public email.
- Request secure channel
- Share non-sensitive contact details
- Reference existing commercial relationship
- Avoid attachments and sensitive evidence
Boundary
No public data intake.
This public website is for product information and non-sensitive commercial enquiries only. Do not submit confidential client, patient, case, investigation, student, regulated, or commercially sensitive data through this public website.
- Do not include confidential client, patient, case, investigation, student, regulated, or commercially sensitive data.
- Do not attach source documents, logs, credentials, secrets, incident evidence, patient records, legal files, or investigation material.
- Use high-level context only: organisation, sector, intended deployment shape, and preferred reply details.
- A secure support or deployment channel can be agreed later during onboarding or contracted support.
- The public site does not post to a backend, create tickets, provision accounts, process payments, or control appliances.
Future extensions
Portal features come later, with design and governance.
Customer Login
A future authenticated portal may support account management after identity, retention, and data-handling requirements are designed.
Support Ticketing
A future ticketing system may support structured support cases after authentication, persistence, secure channels, and retention rules are approved.
CRM Integration
A future CRM integration may be added only after privacy, consent, retention, and operational ownership are defined.