In-Chat Messages Visitors Can See
Screening replies
These arrive as a normal chat reply. Screened-out messages never reach the AI and don’t count against your daily limits.| Message | Trigger | Notes |
|---|---|---|
| ”Please keep your question under 100 words.” | Question over 600 characters | The visitor shortens and resends. |
| ”I’m sorry, this doesn’t seem on topic. Can you ask another question?” | Off-topic, spammy, or prompt-injection content | The assistant stays focused on your site’s content by design. |
| ”Sorry, we provide English-only support right now.” | Non-English question | ChatAds only supports English chat today, independent of the english_only display setting. |
| ”You just asked that - try rephrasing or asking something new.” | The same question sent more than 3 times within a minute | Duplicate-flood protection. |
Limit notices
| Message | Trigger | Notes |
|---|---|---|
| ”You’ve used your N messages for today - come back tomorrow!” | The visitor hit your per-visitor daily limit (default 20/day, tracked by IP) | Input is disabled until the next day. Raise the limit from the Set-Up tab (requires domain verification). |
| ”Chat limit reached. Please try again later.” | Your team hit its plan’s daily message limit (100/500/1,500 per day) | Input is disabled; visitors who haven’t opened the widget that day don’t see it at all. Resets at midnight UTC. Upgrade for a higher limit. |
| ”You’re sending messages too quickly - please wait a moment and try again.” | Burst protection: more than 10 messages per minute from one visitor, or more than 300 per minute across your team | Momentary; the visitor can retry shortly. |
Error notices
| Message | Trigger | Notes |
|---|---|---|
| ”This chat widget isn’t available right now.” | The request was blocked: widget disabled, the embedding domain isn’t in Allowed Domains, or the request looked automated | Check the widget is enabled and the site’s domain is listed in Allowed Domains (subdomains must be listed explicitly; www. is matched automatically). |
| ”Sorry - our model is down! Try again soon.” | The AI provider is temporarily unavailable | Rare; resolves on its own. |
| ”Sorry, something went wrong. Please try again.” | Any other unexpected error | If persistent, contact support. |
Why Isn’t the Widget Showing at All?
The widget hides itself (no launcher button) when:- The widget enabled toggle is off in the Set-Up tab
- The page’s domain isn’t in your Allowed Domains list (when the list is non-empty)
- The current path doesn’t match your Page Rules (include/exclude paths)
- Show on mobile is toggled off and the visitor is on a small screen
- English browsers only is on and the visitor’s browser language isn’t English
- Your team already hit its daily message limit and this visitor hadn’t opened the widget yet that day
Dashboard Warnings
| Warning | Where | What it means |
|---|---|---|
| ”Any site can use your chat widget” | Set-Up tab, Allowed Domains | Your allowlist is empty, so any site could embed your key. Add your production domain(s). |
| Per-visitor limit locked at 20 | Set-Up tab, max messages per day | Raising the per-visitor limit requires domain verification: add a public domain to Allowed Domains and load the widget once on that domain. Localhost doesn’t count. |
| English-only warning | Set-Up tab | You turned off the English-browsers-only display gate. The widget will show for all languages, but chat itself remains English-only and affiliate links are US-only. |
| ”No Amazon Affiliate Tag configured” | Monetize tab | Amazon Affiliate Links is on but no Associates tag is set, so no Amazon links will be inserted. Add your tag. |
| ”Monetization disabled” | Monetize tab | The linked ChatAds API key that powers Amazon monetization was deleted or revoked. Click Re-enable to create a new one. |
| Key regeneration warning | Set-Up tab, Widget Key | Regenerating your cwk_ key invalidates the current embed snippet - your widget stops working until you deploy the new snippet. |