Account
Troubleshooting
Most issues fall into one of a handful of buckets. Start with the matching symptom below. If nothing helps, email support@quincer.com with the URL where the widget lives and a screenshot of the browser console.
Widget isn't showing on my site
- Is the script tag actually on the page? View page source and search for
chatbot-widget.js. If it's absent, the snippet didn't paste cleanly — re-paste from Widget → Deploy. - Is the API key present? The
window.ChatWidgetConfig.apiKeyvalue should start withcw_live_. - Check the browser console. Errors from
chatbot-widget.jsusually name the problem (bad key, CORS, config fetch failed). - Cache-Control. The widget file is cached at the CDN for 5 minutes. If you just rotated keys, wait a few minutes or hard-refresh.
“CORS policy: no Access-Control-Allow-Origin”
This almost always means the domain you're loading the widget on doesn't match
what Quincer has on record for the widget. Open Widget → Settings →
Allowed domains and add the origin (e.g. https://my-store.com).
Wildcards are supported: *.my-store.com matches any subdomain. Leaving the
list empty allows any domain (not recommended for production keys).
“401 Unauthorized” in the console
- Confirm the key in your snippet matches an active key under Widget → Deploy → API Keys.
- If you deleted a key, any site using it will stop working immediately. Generate a new one and re-paste the snippet.
- Widget keys (
cw_live_) and API keys (qn_live_) are not interchangeable. The widget only acceptscw_live_.
Shopify: Theme Editor opens but Quincer Chat block isn't listed
- Make sure the Quincer Chat app is actually installed. Shopify Admin → Apps → look for Quincer Chat.
- If it's there, reload the theme editor and look for the block under App embeds (not under Add section).
- If you're using a legacy (vintage) theme, app embeds aren't supported — use the manual script-tag install against
theme.liquidinstead.
Widget appears, but conversations don't arrive in the dashboard
Almost always a key mismatch: the widget is pointing at a different workspace than the dashboard you're viewing. Verify the first 10 characters of the API key on both sides match.
Meetings aren't being booked
- Is a calendar connected? Open Integrations. If Calendly / Google Calendar / Microsoft 365 all show Disconnected, the agent has no way to offer times.
- Is the BANT threshold right? A Hot score of 70 is a high bar — try setting it to 60 for the first week and observe.
- Is a Calendly event type picked? Under Integrations → Calendly → Settings, make sure a default event type is selected per persona.
- Rep on OOO? If the routed rep is outside business hours or on OOO, Quincer skips them. Add a fallback teammate to the territory.
HubSpot contacts aren't syncing
- Integrations → HubSpot → Test. If the test fails, click Reconnect to refresh the OAuth token.
- Check HubSpot's audit log for permission errors — if Quincer's scopes were reduced, some tools will fail silently.
- Check Integrations → HubSpot → Logs in Quincer for the exact API error.
Knowledge base says wrong things
- Open Knowledge → Chunks and search for the visitor's question. Look at the top-ranked chunks.
- If the right content isn't being retrieved, add a matching Q&A pair with the phrasing the visitor actually used.
- If wrong content is ranked high, delete or disable that source — it's likely outdated.
- See Debugging retrieval.
Agent gives off-brand answers
Tighten the persona's Role and Tone fields. Be specific (“never use the word ‘leverage’”) instead of generic (“be professional”). Add high-risk topics to the Boundaries list so the agent escalates instead of improvising.
Email follow-ups aren't sending
- Confirm Gmail or Microsoft 365 is connected (Integrations tab).
- Confirm Playbook → Email follow-up is set to Auto-send (not Drafts).
- Check your Gmail Sent folder — if the send succeeded, the email is with the visitor and may be in spam.
Dashboard looks broken / stuck on loading
- Hard refresh (Cmd+Shift+R or Ctrl+F5).
- Sign out and back in.
- Check status.quincer.com for ongoing incidents.
Still stuck?
Email support@quincer.com with:
- The URL where the widget is installed.
- A screenshot of your browser console (Chrome: View → Developer → Developer Tools → Console).
- The conversation ID if the issue is inside a specific chat (in the URL when you open a conversation).
- A description of what you expected vs. what happened.