Widget Messages Explained

This page lists every message a visitor can see in the chat widget, plus the warnings you can see in the dashboard - what triggers each one and what (if anything) to do about it.

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.

A conversational reply like “I’m here to help with [your site’s topic] - is there something about that I can help with?” is different: that’s the AI itself declining a question it judged unrelated to your site, not screening. You can widen what counts as on-topic with a custom prompt.

Added to replies

Unlike screening replies, this text is appended to an otherwise normal AI reply rather than replacing it.

Addition	Trigger	Notes
”Heads up: I’m an AI assistant, not a medical or health professional. For anything involving allergies, medications, or a health condition, double-check the details yourself and consult a qualified professional before relying on this.”	The visitor’s question touches allergies, medications, pregnancy, dosage, or another health/medical/safety topic	Appended once at the end of the reply; the assistant’s answer itself is unaffected.

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 Settings 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.

The widget hides itself (no launcher button) when:

The widget enabled toggle is off in the Settings 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”	Settings 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	Settings 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	Settings 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 or UK 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	Settings tab, Widget Key	Regenerating your `cwk_` key invalidates the current embed snippet - your widget stops working until you deploy the new snippet.

Getting Started

Integrations

Configuration

Monetization

Analytics & Data

MCP Tools

Trust & Performance

Account

Troubleshooting

Widget Messages Explained

In-Chat Messages Visitors Can See

Screening replies

Added to replies

Limit notices

Error notices

Why Isn’t the Widget Showing at All?

Dashboard Warnings

​In-Chat Messages Visitors Can See

​Screening replies

​Added to replies

​Limit notices

​Error notices

​Why Isn’t the Widget Showing at All?

​Dashboard Warnings

In-Chat Messages Visitors Can See

Screening replies

Added to replies

Limit notices

Error notices

Why Isn’t the Widget Showing at All?

Dashboard Warnings