Troubleshooting: common problems and fixes
Fix common intoCHAT problems: a chat bubble that doesn't appear, a crawl that finds no pages, vague or wrong answers, a missing lead form and failing actions.
Most problems have a short list of causes. Work through the section that matches what you see. Your browser's developer console (F12) often names the cause directly. Messages the chat shows to visitors are quoted here in English; visitors see them in the widget's language.
The chat bubble doesn't appear
- The script isn't on the page. View the page source and search for
embed.js. Many site builders add custom code only to the published site, not to the editor preview. The script works in the head or the body; just before</body>is the recommended place. See Install with a script tag. - Wrong agent ID. The console shows
Chatbot not found.Copy the snippet again from the Share tab. - The site isn't in the allowed domains. The console shows
intoCHAT: this website is not in the allowed domains of this agent, so the chat is not shown.The agent is limited to other sites. On the Share tab, add this site's domain under Where this agent can appear, or empty the list to allow any website. A new domain can take up to a minute to reach the chat window. See Allowed domains. - The agent is private. The console shows
intoCHAT: this agent is private, so the chat is not shown.On the Share tab, switch off Private agent and click Save. - The visitor's country is blocked. The console shows
intoCHAT: this agent is not offered in the visitor's country (Share > Limits and access), so the chat is not shown.The country is under Blocked countries on the Share tab. Remove it and click Save. The country comes from the IP address, so a visitor using a VPN may appear to be somewhere else. See Limits and access. - Google Tag Manager. GTM removes the
data-chatbot-idattribute from script tags in Custom HTML tags, so the widget doesn't know which agent to load. The console shows "The embed script needs a data-chatbot-id attribute." Use the snippet from the Google Tag Manager guide. - Content Security Policy. If your site sends a CSP header, allow
https://www.intochat.aiinscript-src,connect-srcandframe-src. - Script optimizers. The script reads the agent ID from its own tag. If a plugin merges or rewrites scripts, exclude
embed.jsfrom it. - Ad or privacy blockers. Some browser extensions block third-party chat scripts. Test in a private window with extensions turned off.
- The bubble shows but the agent stops replying. Visitors see "Message limit reached" when your monthly allowance is used up; see Plans and limits.
An inline iframe or the direct link shows no chat
- The iframe stays empty or shows a browser error. The site isn't in the agent's allowed domains, or the agent is private. The browser then refuses to load the chat in the frame, and the console mentions
frame-ancestors. Add the site's domain on the Share tab under Where this agent can appear. - "This agent is private." Switch off Private agent on the Share tab. While it is on, only you and your team members can chat with the agent, in the Playground.
- "This chat isn't available in your region." The visitor's country is under Blocked countries on the Share tab. Remove it and click Save.
- "This agent doesn't exist anymore." The agent ID in the address is wrong, or the agent was deleted. Copy the code again from the Share tab.
- "The chat couldn't load. Please try again later." The agent's settings didn't load. Reload the page.
Visitors see a limit message
- "Too many messages. Please try again later." This visitor reached Limit messages per visitor on the Share tab. They can write again once their hour is over, counted from their first message. People on the same network share one limit. Raise the number or switch the limit off.
- "Too many messages right now. Please try again in a moment." intoCHAT's own hourly limits, which apply to every agent, were reached for this agent or for the visitor's IP address. Wait a moment and try again.
- "This chat has reached its limit for now. Please try again later." The agent reached its Monthly message cap for this agent. The card shows the count and the date it starts over. Raise the cap or switch it off; the agent replies again from the next message.
- "This chat isn't available in your region." The visitor's country is under Blocked countries.
- "Message limit reached": your plan's monthly messages are used up for all your agents. See Plans and limits.
- "The Playground couldn't reply" with a note about the monthly cap: Playground messages count toward the agent's cap. Raise it or switch it off.
See Limits and access.
The widget's text is in the wrong language
- Buttons and notices are in the wrong language. They follow Widget language on the Appearance tab. With Automatic, the chat bubble uses the
langattribute of your page's<html>tag first, for example<html lang="de">, then the visitor's browser languages. Many site builders set this attribute for you; check that it matches the page. To use one language everywhere, choose it under Widget language and click Save changes. - A page in another language shows English. The widget speaks English, German, French, Italian and Spanish. For any other page language it moves on to the visitor's browser languages, then English.
- The inline iframe or the direct link ignores the page language. They have no host page, so with Automatic they follow the visitor's browser.
- Your welcome message or other texts stay in one language. Texts you write are shown as written. Only the defaults are translated.
- The agent replies in a different language. Replies follow Reply language on the Setup tab, not this setting. By default that is the language the visitor writes in. To use one language for every reply, pick it under Reply in, switch on Always use this language and click Save changes. See Instructions.
See Appearance.
A website crawl finds no pages
- "No pages found": intoCHAT couldn't discover pages on that site. Check the address, or switch on Single page mode and add the important pages one by one.
- Everything filtered out: check Exclude URLs containing. A pattern such as
/matches every page. - "The page answered with an error (403)" or similar: the site blocks automated visitors. Ask whoever runs the site to allow it, or upload the content as a file or paste it as text instead.
- "No meaningful content found": the page has almost no readable text.
- "Monthly crawl limit reached": wait for the monthly reset or upgrade. Files, text and Q&A still work.
See Website crawl and Files.
Training doesn't finish
- You closed the page during training. Training continues on intoCHAT's servers. Open the Knowledge tab to see its progress.
- Sources stay waiting to be trained. Open the Knowledge tab: an interrupted run picks up again when you do. If the bar still reads "… sources waiting to be trained", click Train agent. Finished sources stay trained.
- A source shows Failed. Hover over the badge to see why. Click Retry failed, or use Re-index saved text on the source.
- A file or page you added is missing. It was still being read when you left the page. Add it again and wait until it shows as added.
See Managing sources.
Answers are wrong, vague or out of date
- Test the question in the Playground.
- On the Knowledge tab, use Preview the text on the source that should hold the answer. If the text isn't there, the page wasn't read the way you expected.
- For questions people ask often, add a Q&A pair. Q&A answers rank first.
- Click the star (Mark as priority) on the most reliable source. It then ranks above other matching knowledge and wins when sources disagree, without retraining.
- If a page on your site changed, click Refresh from website on its source; it reads the page again and retrains it if the text changed. For a changed file, upload the new version under the same name and train. Website and Notion pages are only read again on their own if auto-resync is on; files, text and Q&A never are.
- Delete outdated sources that contradict the current ones, and check your Instructions.
When nothing relevant is found, the agent says it doesn't know instead of guessing. That is intended: add the missing content. See Managing sources.
The lead form doesn't show
- Enable lead collection is on and you clicked Save lead settings.
- In Manual (visitor asks) mode the form appears only when the visitor asks to be contacted.
- Keyword rules check only the visitor's latest message.
- The form is shown at most 3 times per conversation, and not again once the visitor has shared details in that session. To test again, use a new private window.
- Temporary chats never show it.
- With hand-off by email on, a visitor who asks for a person is offered the hand-off instead of the form, unless a rule matches.
See Lead collection.
An action fails
- Open the action and click Send test request in 2. Try it to see the status and response.
- "URL points to a blocked or internal host": private and internal addresses are refused. Use a public URL.
- "This address redirects somewhere else": click Use this address.
- "Request timed out after 30s": the endpoint is too slow.
- The agent never calls it: check that the action is enabled and that When to use describes the questions it is for.
- Client-side actions only run fully on a page where the widget is installed, and fail in an inline iframe embed. See Client-side actions.
Hand-off by email doesn't work
- The agent never offers it. Check that Offer hand-off by email is on in the Setup tab and that you clicked Save changes. The agent offers it only when the visitor asks for a person, or wants a follow-up it can't give. Temporary chats can't be handed off. If live chat is on and someone has the Live chat inbox open, the agent asks your team to join instead, and offers the email hand-off only if the visitor would rather be contacted by email.
- The agent says it couldn't pass the conversation on. The agent already sent 20 hand-offs in the last hour, or the email couldn't be sent. Try again later.
- The agent says the team already has the conversation. This conversation was handed off less than 10 minutes ago.
- No email arrives. Check the recipients under Email when a new lead arrives on the Leads tab, and your spam folder. Emails sent from the Playground start with
[Test].
See Hand-off by email.
Live chat isn't offered
- The agent offers the email hand-off, or no person at all. Check that Offer live chat when someone from the team is online is on under Live chat in the Setup tab. Live chat is offered only while someone from your team is online: the Live chat inbox open in a tab, within the last 2 minutes, by someone with the Editor role or above. A tab in the background stops counting after about 17 minutes.
- Nothing happens in the Playground. The Playground doesn't show live chat. Test from your site or the agent's direct link.
- Nothing happens in a temporary chat. Temporary chats never request live chat.
- The visitor doesn't see my replies. If you took over a chat in which the visitor didn't ask for a person, their chat window shows your replies only after their next message or a reload.
See Live chat.
A webhook doesn't arrive
Click Recent deliveries under the webhook on the Leads tab. The error of a failed delivery usually names the cause.
HTTP 301: redirects aren't followed, or another3xxstatus: enter the final address the redirect leads to.No response within 10 seconds.: answer with a2xxstatus first and do slow work afterwards.The server's TLS certificate isn't valid.: fix or renew the certificate on your server.The webhook is turned off. Turn it on to deliver events.: switch the webhook on, then click Resend.- The address is refused when you save: use a public address that starts with
https://. Private and internal network addresses are not allowed. - Your signature check fails: compute it over the raw body before parsing the JSON, include the value of
X-IntoChat-Timestamp, and use the newest secret if you clicked New secret. If you reject old timestamps, check your server's clock. - Nothing arrives at all: check that the webhook is Active and that the event is ticked under Events to send. A returning contact sends no new
lead.created.
See Webhooks.
Lost your authenticator
- You have a recovery code. On the code step of the sign-in page, click Use a recovery code and enter one. Then turn two-factor authentication off and on again under Settings, Account to set up your new phone.
- You have no recovery code left. Email support@intochat.ai from your account's email address. Once support has confirmed it's you, they can turn off two-factor authentication for you.
- Codes are always refused. Set the time on your phone to update automatically: codes depend on the clock. Each code also works only once.
See Two-factor authentication.
Still stuck? Email support@intochat.ai and include your agent ID.