Use this page for
Compatibility feedback, setup questions, structured product feedback, and business inquiries.
The contact route is now framed as a specific workflow, not a generic mailbox.
Feedback intake
Share the setup, expected result, and what blocked you.
Leave contact details only if you want a reply. Do not send passwords, private stream URLs, LAN addresses, or sensitive media paths.
01
Structured product feedback
Capture feedback type, industry, source details, message, and optional contact information for later follow-up.
02
Compatibility and workflow questions
Ask about ScopeDock camera sources, LoveMarkDown documents, CursorHop displays and shortcuts, or expected system behavior.
03
Business and collaboration inquiries
Use the same path for partner conversations, integration questions, or workflow discussions that need context.
Contact facts
What this page is for
These quick answers help you decide whether to use Contact, Support, or the download and compatibility page.
Not used for
General site usage measurement.
Messages you send here are handled separately from simple site activity measurement.
Best next step
Try the support page for your product first if you only need a direct answer.
Product-specific guidance is usually faster for common setup and fit questions.
Reply path
Leave contact details if you want a follow-up.
If you only need a quick answer, support and compatibility pages should still be the faster route.
Use these first
Try these routes first if you only need a direct answer
If you only need a quick answer, these pages will usually get you there faster.
- 01
Support
Choose ScopeDock, LoveMarkDown, or CursorHop support for product-specific setup and troubleshooting.
- 02
Download and compatibility
Use this path for platform support, source coverage, architecture choice, and known limits before testing ScopeDock.
- 03
Product page
Compare each NgSense app, its current availability, and the workflow it is designed to support.
- 04
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.
- 01 Setup details
Name the product and workflow
Include the app, installation channel, document or device path, display layout, and command involved when relevant.
- 02 Environment
Include platform and version details
Share the Mac model or chip, macOS version, app version, and any setup conditions that help reproduce the issue or question.
- 03 Outcome
Explain what you expected and what happened
A short contrast between expected behavior and actual behavior makes compatibility and bug triage much faster.
- 04 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.
Next step
Want a faster answer first?
Start with compatibility or support if you want direct answers faster, then use feedback when a device, setup path, or workflow still needs follow-up.