Use this page for
Structured product feedback, compatibility questions, and business inquiries.
The contact route is now framed as a specific workflow, not a generic mailbox.
Contact / Feedback
Feedback should land in the right system.
Use this form for bug reports, feature requests, compatibility questions, and business inquiries. Anonymous analytics and structured feedback stay separate.
This page now treats feedback as a specific product-support workflow instead of a generic contact box.
System boundary
Structured feedback now lands in the website backend.
TelemetryDeck remains for anonymous behavior events only. This contact form and the app feedback modal now post into the same website-owned feedback routes, not into analytics and not into Tina content storage.
Quick answer
Use this page when the product needs a reply, not just a page view
This page is for situations where a support article or compatibility note is not enough and the user needs a reply. That includes bug reports, feature requests, compatibility questions, and business inquiries that need context.
The website feedback loop is intentionally separate from anonymous analytics. In later phases, the same structured feedback model can be shared by both the website and the ScopeDock app, but it should still remain distinct from anonymous behavior measurement.
This page should also help people choose not to send feedback when they do not need to. If support, compatibility, or product guidance already answers the question, those pages should stay the faster route.
Contact facts
The contact page now clarifies what happens here and what does not
These direct answer blocks keep feedback routing, privacy boundaries, and support escalation understandable at a glance.
Not used for
Anonymous analytics payloads.
TelemetryDeck remains limited to anonymous behavior events and does not carry structured feedback content.
Best next step
Try support or compatibility first if you only need a direct answer.
The site now routes simple questions toward self-serve pages before escalating to structured feedback.
Backend status
Static-first pages with an integrated website feedback backend.
The website keeps content pages prerendered while /feedback and related routes stay server-backed for structured feedback intake.
Contact paths
What this page is for
The first website phase only includes the front-end form and interface adaptation layer. It does not store feedback in TinaCMS or mix it into anonymous analytics.
Structured product feedback
Capture feedback type, industry, message, and optional contact information for later follow-up.
Compatibility and workflow questions
Ask about camera types, protocols, source counts, or expected system behavior when deciding whether ScopeDock is a fit.
Business and collaboration inquiries
Use the same path for partner conversations, integration questions, or workflow discussions that need context.
Use these first
Try these routes first if you only need a direct answer
The contact page should not be the first stop for simple setup or compatibility questions when a faster self-serve path already exists.
Support
Start here for troubleshooting, quick-start guidance, and common product questions.
Download and compatibility
Use this path for platform support, source coverage, and known limits before testing ScopeDock.
Product page
Use the product page if you still need the clearest explanation of what ScopeDock is and who it fits.
Blog and guides
Read product updates, setup articles, and workflow guides before escalating to feedback.
Before you send
What helps us answer faster
Better feedback starts with enough context to understand the setup, the expected behavior, and the actual result.
Setup details
Tell us the camera and protocol
Include whether you are using USB UVC, RTSP, ONVIF discovery, or another device path when relevant.
Environment
Include platform and version details
Share the operating system, app version, and any setup conditions that help reproduce the issue or question.
Outcome
Explain what you expected and what happened
A short contrast between expected behavior and actual behavior makes compatibility and bug triage much faster.
Follow-up
Leave contact details if you want a reply
The form can collect optional contact information, but only use it when a real follow-up is needed.
Feedback form
Front-end and website backend layer
Keep the page static-first while posting to the website backend at
/feedback. If needed, you can still override the public endpoint with
PUBLIC_FEEDBACK_ENDPOINT. The app can reuse the same payload contract through
its own configured feedback endpoint.
Next step
Prefer self-serve first?
Start with compatibility or support if you want direct answers faster, then use feedback when something still needs follow-up.