Dragwyb Click to Chat includes request controls intended to reduce excessive visitor traffic and limit the number of AI requests handled by the site. The plugin counts requests and estimates token usage; these controls are not a dollar-denominated spending cap. Use them alongside the usage and billing dashboards from your AI provider.
Open the usage controls
- In WordPress admin, open Click to Chat → AI Assistant.
- Choose Chatbot Settings, then the Advance subtab.
- Review the Security & Rate Limiting and AI Usage & Cost Controls sections.
- Set limits for your expected visitor traffic and save the chatbot settings.
Configure the per-visitor rate limit
The Rate Limit (Requests per minute per visitor) field limits how frequently a visitor can send requests. In version 1.2.0, its default is 20 requests per minute, and the interface accepts values from 1 to 300. Lower the limit if you need tighter throttling, but test normal conversations to avoid blocking legitimate use.
Enable daily and monthly usage controls
The AI Usage & Cost Controls switch enables or disables the plugin’s daily visitor limit and monthly site request ceiling. The version 1.2.0 defaults are:
- Daily Message Limit per Visitor: 50 messages per day by default. The interface accepts values from 1 to 500.
- Monthly Request Budget Ceiling: 5,000 requests per month by default, counted across the site. A value of 0 means unlimited monthly requests.
- Budget limit message: the message shown when a usage limit prevents further requests. Customize it to explain the next step visitors should take.
When the monthly ceiling is reached, the plugin can deny further AI requests until the monthly counter resets or the limit is changed. Disabling AI Usage & Cost Controls bypasses the daily and monthly checks; it does not mean the provider stops charging for requests.
Configure budget threshold emails
The Send Budget Threshold Email Alerts setting can notify administrators when monthly request usage reaches 80% and 100% of the configured ceiling. Use Alert Notification Email (Optional) to enter a recipient address. If the field is left blank, the plugin uses the WordPress administrator email. The setting defaults to enabled in the inspected version.
Delivery depends on the site’s mail setup. Verify the configured recipient and test mail delivery separately rather than assuming that enabling alerts guarantees an email will arrive.
Read the usage meter correctly
When usage statistics are available, the card shows Monthly Request Usage, today’s request count, and estimated tokens for the current month. The meter reflects plugin-side request counters and estimated token totals; it does not show a verified monetary cost or replace the provider’s billing page. For actual charges, review the usage dashboard for the active provider.
Test your limits safely
- Record the current rate limit, daily message limit, monthly ceiling, and alert recipient before changing settings.
- Use a test visitor or controlled session to check normal request behavior under the configured limit.
- Verify that the budget-limit message is appropriate when a limit is reached in a controlled test.
- Check the usage meter and provider dashboard independently to compare request counts and billed usage.
- If an alert is expected, confirm the recipient address and mail logs. Do not trigger a production usage ceiling merely to test an email.
For provider-level cost checks, see Manage AI Provider Costs. For the complete assistant configuration overview, see AI Assistant and Response Behavior. These are test recommendations; no live rate-limit, budget, or email test is claimed here.