Product support

Start with the part of the workflow that is stuck.

Use the guides below for installation, watcher health, opportunity review, account access, plan usage, and billing. Keep sensitive information out of anything you share.

I

Installation

Confirm Google Chrome, the canonical store listing, extension permissions, workspace login, and supported Facebook tabs.

Open installation guide →
W

Watcher health

Check whether Chrome is awake, the expected tab is open, the extension is active, and the saved groups and filters are current.

Review watcher checks →
$

Account and billing

Log in to view the active plan, current usage, upgrade controls, and the billing-management path for the workspace.

Open Lurker settings →
Watcher troubleshooting

Check the visible operating conditions first.

Most watcher issues can be narrowed down without sharing Facebook content or private account details.

Watcher appears stale

Confirm Chrome and the computer are awake, the Facebook tab is still open, and the current extension is active. Use the extension's recovery guidance or restart the watch.

No notifications are detected

Open Facebook notifications yourself, confirm the tab URL is supported, and check whether the watched-group-only filter excludes the item.

Too many irrelevant posts

Review positive and negative keywords, narrow broad terms, verify group selection, and consider whether an available company-aware mode fits the workflow.

A relevant post was missed

Check watcher health and supported page conditions first. Then review available diagnostics and tune settings. Lurker does not guarantee complete coverage.

Role-address delivery verification is still pending

The support alias has been configured, but it will not be published until a message is confirmed in the destination inbox. Use the authenticated app and this support guide in the meantime.

Share safely

Keep sensitive information out of support messages.

Do not submit Facebook passwords, authentication cookies, access tokens, private messages, sensitive post content, customer data, payment details, or screenshots containing personal data unless AJAI specifically requests an artifact and provides a safe handling route.

For privacy and deletion-request information, read the Lurker privacy policy.

Still deciding where the problem lives?

Compare the public workflow with the current plan and usage shown in your workspace.