De mensagens manuais para fluxos de trabalho automatizados
Ferramentas de automação conectam seus aplicativos. O WhatsApp costuma ficar de fora porque roda em uma API separada. Para incluí-lo, você precisa de um número comercial verificado, uma chave de API autorizada a enviar mensagens por ele e um provedor na API oficial do WhatsApp Business.
A 360Dialog oferece os três. Fazemos o onboarding do seu número na API oficial do WhatsApp Business e entregamos a você uma chave de API do canal. A partir daí, a ferramenta que você já usa faz o resto: algumas se conectam por um módulo nativo do WhatsApp, outras por um único webhook. De qualquer forma, a mensagem sai do seu próprio número, não de um número compartilhado.
You're seeing messaging limits, number quality degradation, Meta restrictions, or poor delivery rates
A send has gone wrong before: throttled, flagged, or a number that stopped delivering
You're sending enough volume that a naive loop calling the API directly will eventually get you throttled or banned
You want queue depth, retries, and backoff handled, not hand-rolled
How it works
1
Connect your list
Upload contacts or connect your CRM. No code required.
2
Describe the campaign
Say who it's going to and what it should say, in plain English.
3
Send safely
Sendout paces delivery, respects the warming schedule, and slows down automatically if quality drops.
What is happening behind the hood: the audience gets resolved from the warehouse query, split into batches sized to your current tier, queued through the rate limiter, and dispatched with retry and idempotency handled automatically.
Book a demo
Frequently asked questions
Can I use this for order and delivery notifications, not just marketing?
Yes, that's most of what runs through here day to day: order confirmations, delivery updates and appointment reminders at volume, with the same safeguards as a marketing campaign.
→
What happens when I hit my tier limit?
Sends past your tier ceiling queue rather than fail. Once your tier goes up, quality rating stays healthy, or the 24-hour window resets, queued sends continue automatically.
→
Do I need to know what a quality rating or a warming schedule is?
No. Describe who you're sending to and what it should say, and Sendout handles the pacing, the warming and the quality checks behind it.
→
Why not just call the WhatsApp Business API directly, or use an unofficial library?
At low volume, you can. At real volume, you're rebuilding a token-bucket rate limiter, retry logic with idempotency, and quality-rating monitoring, the exact things that break silently at 2am and take a number down with them. Unofficial libraries carry the added risk of sitting outside Meta's terms of service entirely.
→
Can I embed this into my own product instead of using it standalone?
Yes. The API is built to sit inside any product that needs to send WhatsApp at volume.
→
