Skip to main content
Fliqr AI enforces limits across several dimensions to maintain platform performance and reliability for all customers. This page documents those limits so you can design your integrations and flows within them. Most limits are per-account unless otherwise noted. If you are approaching a limit and need a higher quota, contact Fliqr AI support to discuss custom allocations.

​
API Rate Limits

When you exceed the rate limit, the API returns a 429 response with a Retry-After header indicating how many seconds to wait before retrying. Implement exponential backoff in any integration that makes frequent API calls.Each API key has its own independent rate limit. If you have multiple integrations, consider using separate API keys to avoid one integration consuming the allowance of another.

​
Contacts

Contact limits apply to the total number of contact records in your account, regardless of activity status. If you’re approaching your contact limit, review and delete contacts that are no longer needed, or contact support to discuss a quota increase.

​
Broadcasts

WhatsAppAll WhatsApp broadcasts must use pre-approved message templates. There is no Fliqr AI-side daily limit, but Meta enforces quality-based limits on your WhatsApp Business account:
  • New numbers start with a limit of 1,000 business-initiated conversations per 24-hour period.
  • This limit scales automatically based on message quality and volume over time (up to unlimited).
TelegramNo broadcast limit is enforced by Fliqr AI or Telegram for standard use. Telegram’s spam detection may throttle accounts that send mass messages to contacts who did not initiate the conversation.SMSNo Fliqr AI-side daily limit. Volume limits depend on your Twilio number type and registration:
  • Long code (10DLC): Up to 2,400 segments per minute after carrier registration.
  • Short code: Higher throughput; requires carrier approval.
Note: Carrier filtering applies to all SMS broadcasts. Contacts must have a documented opt-in.

​
Flow Builder

If a complex flow is approaching the 250-block limit, consider splitting it into a parent flow that calls sub-flows using the “Go to Flow” block. This keeps individual flows manageable and the logic modular.

​
AI Agents

The 500MB knowledge base limit applies per individual AI Agent. If your knowledge base exceeds this, split content across multiple agents and use routing logic to direct contacts to the appropriate agent based on their question category.Context window limits are set by the AI model provider. Long conversation histories may exceed the context window — Fliqr AI automatically truncates older messages when this occurs to maintain function.

​
File Uploads

This limit applies to files uploaded within the Flow Builder (e.g., attachments in a Send Message block). For larger files, host them externally and reference the URL in your flow instead of uploading directly.

​
Message History

Messages older than 12 months are deleted automatically. If you need long-term message archiving, export conversation data via the API or set up a webhook to stream new messages to your own data store in real time.
If you need a higher quota for any of the limits above, contact Fliqr AI support with your use case. Custom quotas may be available for Pro accounts.

​
What’s Next

Channel Errors

Diagnose and fix delivery and connection errors on each messaging channel.

FAQ

Answers to common setup and usage questions.