Bulk Messaging
Send bulk WhatsApp messages using the alternative non-API channel for high-volume communication requirements.
Overview
Bulk Messaging provides an alternative method for sending WhatsApp messages outside the standard template-based WhatsApp Business API. This channel is designed for scenarios where template approval is not feasible, where you need to send custom content at very high volumes, or where your use case does not fit Meta’s template framework.
Bulk Messaging is a separate channel from the WhatsApp Business API. It does not require Meta template approval and operates under different rate limits and delivery mechanisms. The API template channel (via WhatsApp Campaigns) remains the recommended approach for compliance-first, branded messaging.
The bulk messaging channel is implemented as a developer/internal feature. Availability, sending limits, and behavior may vary based on your account configuration and plan tier. Contact your account manager to confirm your bulk messaging capabilities and balance allocation.
When to Use Bulk Messaging
Bulk Messaging is well-suited for scenarios where the standard API channel has limitations:
- High-Volume Sends — When you need to send messages to tens of thousands of contacts in a short time window, and Meta’s API rate limits (tied to your phone number quality tier) are a bottleneck.
- Custom Content — When your message content does not fit a template structure (e.g., dynamically generated reports, real-time pricing data, or content that varies significantly per recipient).
- Rapid Deployment — When you need to send immediately and cannot wait 24–48 hours for Meta template approval.
- Internal or Developer Notifications — System alerts, monitoring notifications, or internal team broadcasts that do not need the compliance layer of the API channel.
API Template Messages vs Bulk Messaging
| Aspect | API Template Messages | Bulk Messaging |
|---|---|---|
| Template Requirement | Meta-approved templates required | No template required |
| Message Content | Pre-defined structure with variables | Flexible custom content per recipient |
| Meta Approval Process | 24–48 hour approval cycle | Not applicable |
| Delivery Channel | WhatsApp Business API (Meta-endorsed) | Alternative non-API channel |
| Delivery Tracking | Full delivery, read, and failure tracking | Available per implementation |
| Analytics | Comprehensive campaign analytics dashboard | Varies by account configuration |
| Rate Limits | Governed by Meta phone number tier | Governed by account/plan limits |
| Compliance | Full Meta policy compliance | Independent of Meta template policies |
| Opt-In Requirement | Required by Meta policy | Recommended best practice |
| Cost | Deducted from plan WhatsApp balance | Deducted per account configuration |
| Best For | Branded, compliant business messaging | High-volume, flexible messaging needs |
For most business communications — especially those involving customers and prospects — use the API Template channel. It provides verified delivery, protects your brand reputation, and maintains Meta policy compliance. Reserve Bulk Messaging for scenarios where the API channel’s constraints are a genuine blocker.
Sending Bulk Messages
Step-by-Step
- Navigate to WhatsApp → Campaigns or the designated bulk messaging interface (depending on your account configuration).
- For bulk messaging, the system uses the non-API channel — ensure you are in the correct sending mode.
- Upload your contact list with message content. The bulk channel supports providing per-contact custom message text.
- Configure sending parameters:
- Message Content — Plain text or structured content per contact.
- Sending Rate — Control the messages-per-minute rate to manage throughput.
- Scheduling — Optionally schedule the send for a later time.
- Review your contact count and estimated cost.
- Launch the bulk send.
Sending Configuration and Parameters
| Parameter | Description |
|---|---|
| Contact List | Upload a CSV or select from your CRM contact segments. File must include phone numbers in international format (+919876543210). |
| Message Content | Per-contact message text. For bulk channel, this can be fully custom and is not constrained by template schemas. |
| Sending Rate | Messages dispatched per minute. A lower rate reduces the risk of delivery issues but increases total send time. |
| Concurrent Connections | Number of parallel sending threads. Higher concurrency speeds up delivery but may increase resource usage. |
| Schedule | Set a future date and time for the send to begin. Timezone-aware scheduling is supported. |
| Retry on Failure | Whether to automatically retry messages that fail on the first attempt. Each retry counts as a separate message for billing purposes. |
Rate Limiting and Batch Size Guidance
Unlike the API channel where Meta governs rate limits, the bulk messaging channel’s limits are determined by your Voxvaani account configuration and plan tier. General recommendations:
| Contact List Size | Recommended Batch Size | Estimated Send Time |
|---|---|---|
| 1–1,000 | Single batch | 5–15 minutes |
| 1,000–10,000 | 500–1,000 per batch | 30 minutes–2 hours |
| 10,000–100,000 | 2,000–5,000 per batch | 2–12 hours |
| 100,000+ | 5,000–10,000 per batch | 12+ hours |
Actual send times depend on your account’s configured rate limits, concurrent connection count, and network conditions.
Sending extremely large batches without pausing can strain the delivery infrastructure. Split very large lists into smaller, sequential batches with brief pauses between them. Monitor the progress dashboard and adjust the sending rate if you observe high failure rates.
Limitations and Considerations
- Delivery Guarantees — The bulk messaging channel does not provide the same level of delivery confirmation as the WhatsApp Business API. Read receipts and delivery confirmations may be limited or unavailable.
- Media Attachments — Support for images, videos, and documents in bulk messages varies by account configuration. Confirm media capabilities with your account manager before planning media-heavy campaigns.
- Opt-In Compliance — While the bulk channel does not technically require Meta’s opt-in verification, sending unsolicited messages is a poor business practice. Maintain opt-in records and provide an opt-out mechanism.
- No Template Sync — Bulk messaging does not integrate with the template management system. Message content is provided directly at send time.
- Plan Balance Consumption — Each bulk message deducts from your WhatsApp balance. If your balance drops to zero mid-send, remaining messages will fail. Monitor your balance before and during large bulk sends.
Monitoring and Delivery Tracking
During and after a bulk send, monitor the following:
- Sent Count — Total messages dispatched to the sending queue.
- Delivered Count — Messages confirmed as delivered (where delivery tracking is available).
- Failed Count — Messages that could not be sent. Review failure reasons to identify issues (invalid numbers, network errors, rate limiting).
- Progress Percentage — Overall completion percentage of the send.
- Balance Consumed — WhatsApp balance deducted so far. Compare against estimated cost to track budget.
Use Voxvaani’s analytics dashboard to review bulk messaging performance over time. Export delivery logs for external analysis or reconciliation with your CRM.
Troubleshooting
Messages Not Sending
Symptom: Bulk send is initiated but no messages are dispatched.
Possible Causes and Solutions:
- Insufficient Balance: Your WhatsApp message balance may be depleted. Check Wallet & Billing and top up if needed.
- Invalid Contact Format: Phone numbers must be in international format. Verify your uploaded list uses the
+prefix and country code. - Account Configuration: Bulk messaging may not be enabled for your account. Contact your account manager to confirm feature availability.
High Failure Rate
Symptom: A significant percentage of messages fail.
Possible Causes and Solutions:
- Invalid Numbers: Numbers that are not on WhatsApp will always fail. Clean your contact list and remove inactive contacts.
- Network Congestion: High sending rates during peak hours can lead to failures. Reduce the sending rate and try during off-peak hours.
- Carrier Restrictions: Certain phone number prefixes or regions may have delivery restrictions. Segment your list and test with known-good numbers first.
Delivery Not Confirmed
Symptom: Messages show as “Sent” but not “Delivered.”
Possible Causes and Solutions:
- Limited Tracking: The bulk channel may not support read/delivery receipts for all routes. Confirm tracking capabilities with your account manager.
- Recipient Offline: The recipient’s device may be offline or WhatsApp may be in background. Delivery may be confirmed later when the device reconnects.
- Recipient Block: The recipient may have blocked your business number, preventing delivery confirmation.