Chatbot With Rate Limiting: Three Different Limits Buyers Mix Up, and a Quick Quiz to Find Which One You Need (Free Limit Quiz)
Chatbot with rate limiting is asked for by three kinds of buyers who want three different things: some want to slow a flood of messages, some want API calls kept in check, and some just want a hard cap on what they spend. This guide separates the three, shows the fixed limits LiveChatBot enforces for each, and gives you a short quiz that points you to the control that fits your worry.
⚡ In short
- Rate limiting can mean message speed, API call limits or a spending cap. Decide which you mean first.
- LiveChatBot has built-in limits: 20 chat messages a minute per IP, 240 widget requests a minute per IP and 120 REST API requests a minute per key. They are fixed, not settings.
- Its usage limits are predictable: free visitors, one-time packs, and no automatic charges.
- Take the quiz to match your worry to a control you can use today.

Three meanings
Three limits that all get called rate limiting
The phrase comes from engineering, but small-business buyers use it loosely. Here are the three meanings you will meet.
1. Message speed limits
How many messages one visitor can send in a minute. This protects your team and your AI from floods, loops and scripted abuse. Technical teams call it throttling.
2. API call limits
How many requests your own software may send to a service in a minute or a day. If you connect the chat to a CRM or a sheet, this decides whether your integration breaks on a busy day.
3. Usage and spending caps
How much chat, how many AI replies or how many visitors you can use before a plan stops or charges more. This one is about your bill, not about speed.
Most worries on a small site are the third kind. Be honest with yourself about which you have, because tools solve them in very different ways.
Free quiz
Which limit do you actually need?
Answer four questions. The most common type of answer wins.
Message speed
What a chatbot with rate limiting does about message floods
A tool with message-speed limits slows or blocks a visitor who sends too much too quickly. It is useful when scripts hit the chat or an AI is exposed to loops.
LiveChatBot has this built in. Visitor chat messages, chat ratings and help-article votes are limited to 20 per minute per IP address. The widget as a whole accepts up to 240 requests a minute per IP, and the dashboard login allows 10 attempts a minute. Past a limit, extra requests are refused until the minute passes.
These are fixed limits that apply to every account. They are not settings, so you cannot raise, lower or switch them off, and there is no per-visitor rule or captcha on top. Everything else is manual and structural.
- Block the visitor or IP from the inbox. See how to block a visitor in live chat.
- Limit exposure. The where-it-shows settings let you choose devices and countries and hide the chat on chosen pages.
- Filter upstream. Ask your host or CDN for a bot filter or firewall rule. A host-level rule is the strongest answer to heavy scripted floods because it never lets the traffic reach the page.
For a longer view of abuse, read live chats free of spam and abuse.
API limits
Rate limits when you connect the chat to other tools
If your plan includes sending chat or ticket data elsewhere, API limits become the practical concern.
Push, don’t poll
Polling asks “anything new?” every few seconds and burns your allowance. Webhooks tell you when something happens. LiveChatBot sends ticket.created and ticket.solved webhooks, so a sheet or CRM can update only when needed.
Use Zapier for the no-code route
Connecting live chat to Zapier means Zapier manages the timing of requests, which removes most of the work of staying within limits.
Know the API limit
LiveChatBot has a REST API, limited to 120 requests per minute per API key. That is a fixed limit, not something you can raise, so batch your calls and use webhooks for events. Do not assume numbers from another product. See the integrations page for what exists today.
Spending
Usage limits that behave like a spending cap
For many owners, the real fear is cost. This is where predictable rules help more than clever throttling.
- Free plan: 2 websites per account, with 100 free visitors per website each month. A visitor counts once a month, when they trigger a new-visitor alert.
- Visitor packs: 100 for ₹99, 500 for ₹299, 1000 for ₹499, bought per website, one-time, and they never expire.
- Extra website: ₹199 for 6 months.
- Over the limit: tracking and alerts continue, and chat pauses for new over-limit visitors until a pack or the month reset. Nothing is charged automatically.
- AI replies: a small free monthly allowance per website, then AI packs. When it is used up, the free keyword bot answers from saved replies.
There are no per-seat charges, so adding an agent never changes the total. See pricing for current details.
Busy days
Planning a busy day without a chatbot with rate limiting
Not every spike is an attack. A sale, a festival offer or a mention on social media can bring ten times your usual visitors, and all of them want answers at once.
Before the day
Check your free visitors and decide whether to buy a pack in advance. Packs never expire, so an early purchase wastes nothing. Add the answers people will ask about to Knowledge, and make sure saved replies cover the basics for the free keyword bot.
During the day
Watch the inbox on your phone through the Android app. Assign chats to yourself with Assign to me, and use the Unassigned and Mine folders so two people do not answer the same visitor.
After the day
Look at what you were asked most often and update your Knowledge. A good spike teaches you more than a quiet month.
Test it
How to test a chatbot with rate limiting claim
Do not accept a feature name. Test it in a trial.
- Send 25 messages in under a minute from your own phone. Does anything slow you down? LiveChatBot refuses messages beyond 20 a minute per IP.
- Ask the vendor what happens to a flood: blocked, delayed or accepted?
- Ask whether a flood uses up your AI replies or visitor allowance.
- Ask for the API limit in writing, with the number per minute. LiveChatBot’s is 120 per key.
- Check whether limits can be changed by you. LiveChatBot’s cannot; they are fixed.
If answers are vague, treat the limit as unproven.
Frequently asked questions
Does LiveChatBot offer a chatbot with rate limiting?
Yes, as fixed built-in limits: 20 visitor messages a minute per IP, 240 widget requests a minute per IP and 120 REST API requests a minute per key. You cannot change them. It also offers blocking and predictable usage limits.
How can I stop a flood of chat messages?
The 20 messages a minute per IP limit slows a single source automatically. Block the visitor or IP from the inbox, and ask your host or CDN for a bot filter if the flood is spread over many IPs.
Will a flood use up my free visitors?
Visitors count once a month when they trigger a new-visitor alert. Check your visitors list during an attack, since the count depends on how the traffic behaves.
What happens when I reach a usage limit?
Tracking and alerts continue, and chat pauses for new over-limit visitors until you buy a pack or the month resets.
Are there API rate limits I should know about?
Yes. The REST API allows 120 requests a minute per API key, and the limit is fixed. Webhooks and Zapier avoid most problems.
Keep reading
Related guides
Chatbot With Captcha Integration: Do You Need One, What It Costs Real Customers, and What to Use Instead When Your Tool Has None (Free Decision Tree)
Chatbot With Automatic Language Detection: Browser Language Versus Typed Language, and Ready-to-Copy Welcome Lines in Five Languages (Free Copy Pack)
Chatbot With Spam Protection: Ask These Questions Before You Trust the Claim, and Set Up the Defences You Control Today (Free Defence Checklist)
Know your limits before you start
Free plan for two websites, one-time packs and no automatic charges. Start free on livechatbot.in.