WhatsApp: choose and configure a provider

One default provider

The WhatsApp page offers Official Meta, ISP WA, Mail2Wa, and 360 Messenger. Select Use this provider as default in the chosen panel and save. Disabled skips WhatsApp sends and does not convert them to email or SMS.

Before switching, verify authentication, sender, templates, inbound flow, and queue. A configured but unselected provider is not automatically operational.

Key differences

Official Meta uses the WhatsApp Cloud API and an assigned or verified business number. Business-initiated conversations require approved templates and free-form replies follow the 24-hour window for the exact sender conversation. It integrates ISP Message, attachments, tickets, selected push recipients, and Meta conversation-category billing.

ISP WA uses a native ISP Billing messaging profile assigned and authenticated for the ISP. It provides inbound and outbound messaging, CRM number recognition, ticket creation or continuation, attachments, and shared locations without using the tenant’s Meta template catalog or Meta category/window charging model.

Mail2Wa is an external service configured with its own API key, authorized telephone number and email, credit balance, and QR pairing lifecycle. 360 Messenger is a simpler legacy API-key provider. Authentication, sender identity, templates, session state, billing, inbound handling, and recovery procedures are provider-specific and cannot be copied from one panel to another.

WhatsApp queue

The queue shows pending, processing, sent, retried, and failed work with its event, provider, attempt count, scheduled time, and available error information. Opening the page only inspects the queue; it does not send waiting messages.

Before retrying, correct the actual cause: provider authentication, inactive profile, recipient format, missing template, Meta conversation window, insufficient credit, inaccessible attachment, or a remote error. Repeating an unchanged job can create unnecessary attempts without improving delivery.

Numbers and recipient selection

Normalize CRM telephone numbers in international format and define which customer contact field is authoritative. Manual sends for invoices, reminders, and quotations may allow the operator to choose among eligible customer numbers, while some bulk Meta workflows deliberately use the primary contact.

Always verify recipient, consent, document ownership, and message purpose. A technically valid WhatsApp number may belong to a different contact or have been reassigned, so customer identity must not be inferred from formatting alone.

Scheduled dispatch, retries, and cleanup

A CLI dispatcher selects available jobs in bounded batches, prevents concurrent ownership of the same row, and releases processing jobs left locked beyond the safety threshold. Non-Meta providers use adaptive per-ISP throttling; Meta uses its own capacity handling.

A failed job returns to pending with increasing delay and becomes definitively failed after the third attempt. Cleanup logic for failed rows exists, but its former HTTP trigger is disabled; do not assume it is scheduled without an explicit operational configuration. Verify that the CLI dispatcher is scheduled, non-overlapping, and monitored through logs. Opening the Queue page does not dispatch messages.

Configure 360 Messenger

360 Messenger is the simplest legacy provider. Enter its own API key, explicitly select it as default, and save. It does not use the assigned Meta number, approved Meta templates, the 24-hour window, or an ISP WA profile.

Validate the key, international recipient format, consent, provider response, and queue outcome with one authorized message before enabling automated events or campaigns.

Module events

Invoices, payments, reminders, quotes, contracts, activities, reports, delivery documents, services, Radius, ISP Dude, and Proxmox may emit WhatsApp events when module, template, and provider allow them. Channel activation does not replace per-event setup.

Checklist

• Select one default provider
• Complete its authentication
• Verify sender and CRM contacts
• Configure templates and events
• Run one authorized test
• Review the queue
• Fix the cause before retry
• Protect attachments and credentials