Troubleshooting

Check: correct URL from Settings; secret header if required; valid JSON body with required fields (e.g. name). Test with curl or Postman. 401 = bad secret; 400 = bad payload; 404 = wrong URL.

Refresh the page. Confirm the source (form, webhook, Make) is sending to the right account and URL. Check Filters on the Leads page. If from webhook, check execution logs in Make/your app for 200 responses.

Ensure the campaign is On. Check trigger (e.g. “lead created” only for new leads). Check filters (source, tag). Look for errors in the Campaigns area. Verify plan limits.

Confirm email and password. Use “Forgot password” if needed. Clear cookies/cache or try another browser. If you’re redirected to billing, your subscription may have lapsed.

Confirm the script is on the page (view source, check for your LeadLock script). Check for JavaScript errors (browser console). Ensure the script loads after the DOM. Try a hard refresh or another page.

Use the Contact page (e.g. /contact) or the link in the Help Center. You can also use the in-app chat if available. Include what you were doing and any error message.

Symptom: Numbers or lists on the dashboard do not match what you expect. Likely cause: Page loaded with old data or filters hide some leads. Fix: Refresh the page. Check that you are not using a filter (e.g. my leads only) that excludes the lead. Confirm the lead exists in Leads and has the expected stage. If it still fails after a refresh, contact support with what you see versus what you expect.

Symptom: You cannot see a section or get an access error. Likely cause: Plan limit, role, or account mismatch. Fix: Check Billing for plan limits. Confirm you are in the correct account or workspace. If you expect access, contact support with your role and what you are trying to open.

Symptom: You updated the site or config but still see old behavior or old content. Likely cause: Browser cache, CDN cache, or the wrong branch or build is deployed. Fix: Hard refresh (Ctrl+Shift+R or Cmd+Shift+R). Clear browser cache. If you deploy code: confirm the correct branch and build are deployed; wait for the deploy to finish; clear any CDN or cache in front of the app. If you edited the wrong file or an old branch, fix the source and redeploy. When updates still do not appear after that, check deployment logs and consider contacting support with your deploy steps.

Contact support when: you have followed the troubleshooting steps for your issue and it persists; you see an error message (include it and what you were doing); you suspect a billing or access problem; or you need help with a deployment or integration. Use the Contact page or the link in the Help Center; include what you were doing, any error reference code, and steps you already tried.

Each help topic (Leads, Webhooks, Automations, Chat Widget, etc.) has its own troubleshooting section. See also Billing, Integrations, Advanced/Developers.