Limits and ban risk

The truth first

• The WhatsApp connection through Felku is not official. WhatsApp can restrict or ban a number at any time, without notice, and we can't reverse that.

• The guards below reduce the risk. No guard removes the risk, ours or any other provider's.

• The numbers are conservative assumptions, built from what's known in the market. They are not rules published by WhatsApp.

• A bigger plan doesn't buy more sending. Limits are the same on every plan, because selling a higher limit would be selling a higher risk.

What helps most: a dedicated number (not your main number), no other unofficial system linked to the same number, and talking to people who already talk to you.

Pacing

• Hours: on WhatsApp, sending hours are optional: if you turn them on (in Sending rules), it only starts conversations from 08:00 to 21:00, and replying to people who wrote keeps working; on Telegram, from 07:00 to 23:00. Both apply in the connection's time zone. Outside those hours, the send comes back as adiar, and the message says from what time (and in which time zone) it can go out. "Per day" caps reset at midnight in that same time zone.

• Interval: on WhatsApp, 25 to 45 seconds between one send and the next, drawn each time so it doesn't look like a bot. On Telegram, 4 to 7 seconds.

• Burst: after 5 sends in 10 minutes, a 5-minute pause on WhatsApp and a 1-minute pause on Telegram.

• "Typing": before each send, the chat shows "typing" for a few seconds, proportional to the text length.

• Too regular a rhythm: if sends get too evenly spaced, the next one is delayed a moment to vary.

WhatsApp caps, by connection age

The number starts slow and gets more room over time, counted from pairing:

On Telegram, the cap doesn't change over time:

6 messages per hour and 20 per day, from day one.

Other actions

• Editing a message counts as a text send (same caps).

• Mark as read, "typing", check number, react and delete have their own, much higher cap (600 per hour, 5,000 per day), and respect the sending hours and the contact list.

Conversations

• At most 3 automatic replies in a row without a new message from the person.

• Per conversation: at most 6 replies per hour and 30 per day.

• Too much automatic back-and-forth (6 exchanges in 30 minutes) pauses the conversation until you write in it.

• New conversations served: at most 3 per hour and 8 per day on WhatsApp; 2 per hour and 3 per day on Telegram. People already in a conversation keep being served.

What comes blocked

• Destination outside your contact list. It doesn't go out. You add the contact in the dashboard (contact list).

• First messages beyond the day's cap. A first message is one sent to someone on your list who never wrote to the number nor received a message from it. The cap is the owner's choice in Sending rules, up to 3 per day per connection (the day turns at midnight in the connection's time zone), the same on every plan and on the trial: a bigger plan doesn't buy more. The fourth is denied (first_contact_daily_cap), with the time it opens again. Replying to people who already wrote doesn't count toward this cap.

• The same message to many destinations: the same text (12 characters or more) to more than 2 people within 24 hours is denied. Vary the text.

• More than 1 link per message.

• High-risk actions (creating a group or posting to status, among others): switched off, and only a specific key permission unlocks them. For WhatsApp groups, communities and channels, every send or action also needs the owner's approval (Tools).

• During the free trial: the agent talks with you and 2 more contacts on WhatsApp and with 1 one-to-one chat on Telegram.

Circuit breaker and pause

Drops, send failures, reconnection loops or restriction warnings add points. At 5 points within 1 hour, the connection pauses on its own: every send is denied and reading continues. Only a person resumes it, in the dashboard. You or the agent can also pause at any time (felku_pause_connection).

Delaying is not a queue

When the answer is adiar, the field quando says from when the send can go out. The server doesn't keep the send to deliver later: the agent has to ask again. A send that could only go out more than 48 hours from now is denied (queue_horizon_exceeded).

How long received messages are kept

After that period, the message is deleted from the server. A message that reaches the server more than 15 minutes after it was sent is discarded; one that arrives in time waits for the agent in felku_read_new_messages until the end of the period above.

See your own usage

felku_get_policy_status shows how much has been used in the hour and the day, how many first messages went out today (first_contact: used, the day's cap and when it resets), the next allowed time and whether the connection is paused.