Lurk is early, but support should still be simple. If something is broken, confusing, missing, or not working the way you expected, use this page to figure out where to go.Documentation Index
Fetch the complete documentation index at: https://lurkai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Fastest way to get help
For most issues, contact support at: support@lurk-ai.com Include:- what you were trying to do
- what happened
- what you expected to happen
- your browser/device
- screenshots or screen recordings if useful
- any error message you saw
Product issues
Contact support if:- a page is broken
- something will not load
- a search result looks wrong
- saved data is missing
- you cannot access your account
- a feature behaves differently than expected
- something looks broken on mobile
- you think Lurk is showing stale or incorrect information
Billing or account issues
For billing, subscription, account, or access issues, include the email tied to your Lurk account. Do not send passwords, private keys, API keys, or sensitive financial information over email.Security issues
If you believe you found a security issue, include SECURITY in the subject line. Example:- what you found
- where you found it
- steps to reproduce if possible
- screenshots only if they do not expose sensitive third-party information\
Feedback and feature requests
Feature requests are welcome, but Lurk is intentionally focused during beta. The best feedback explains:- what you were trying to do
- where the current product slowed you down
- what workaround you used
- how often the problem happens
- why it matters to your workflow
Response expectations
Lurk is an early product. Support is handled directly and prioritized by severity. Highest priority:- security issues
- account/access problems
- broken core workflows
- incorrect or stale product behavior
- general questions and feature requests
Before reaching out
Try:- refreshing the page
- logging out and back in
- checking your connection
- trying another browser
- checking whether the issue happens on desktop and mobile

