Skip to main content
WhatsApp is not a megaphone. The more sending looks like a bot, the higher the risk. Notifique adds brakes between your code and the recipient, queue, delay, and limits.

​
In brief

  • Risk exists in both modes; unofficial needs more care with volume and new SIMs.
  • On the official line, Meta also enforces rules (templates, 24h window, billing, quality).
  • You need opt-in, allowed content, and gradual use on new numbers.
  • Notifique does not guarantee zero blocks if usage violates policies.
Connection modes: Connection modes.

​
What increases risk

Follow Meta policies and Notifique Terms. Opt-in and lawful content are not optional.

​
New numbers and SIMs

New SIMs and new Business accounts are watched more closely. The platform applies automatic warm-up (20 msgs/day for the first 3 days), a safety ceiling, not a day-one target.

​
Before connecting the API (3–7 days)

Use the number on the phone, without the API:
  1. Complete the profile (photo, name, description)
  2. Chat manually with real contacts
  3. Avoid activating the SIM and connecting the API on the same day

​
After connecting

Check warmup on GET /v1/whatsapp/instances/:id (active, sentToday, daysRemaining).

​
Opt-in and conversations

Notifique does not block all cold outreach automatically, you model consent in your product. Inbound message webhooks help you know who already opened a chat.

​
How Notifique helps

With a fixed instanceId, the pool does not apply. Pools are optional. Details: Sending Pools.

​
Unofficial connection only

Ban screen on the phone? Do not keep requesting codes on the same instance. Wait or use another healthy number.

​
Official connection only

Meta controls quality, templates, and billing: Details: Official Meta templates.
Sandbox (sk_test_) does not run real Meta gates. In production (sk_live_), treat META_* as Meta account or policy signals.
Full catalog (pools, Meta, campaigns): Error responses.

​
Best practices

  1. Warm up the SIM on the phone before the API
  2. Start slow on the API (5–10 sends/day in the first days)
  3. Prioritize people who already contacted you or opted in
  4. Separate transactional from marketing (instance, pool, or priority)
  5. Monitor failure webhooks (message.failed)
  6. Use idempotency to avoid duplicate sends

​
What Notifique does not do

  • Does not guarantee zero blocks with abusive content or volume
  • Does not replace recipient consent
  • Does not control bans or quality decisions made by Meta on the official line

​
Next steps