WhatsApp Business Calling

Messaging and supported Calling capabilities are configured automatically when a WhatsApp Business Account is connected. Calling still depends on Meta eligibility for each individual number. Messaging continues to work independently when Meta does not offer Calling.

Supported flow

• User-initiated calls arrive through Meta's calls webhook and are routed to the first enabled browser, SIP, queue, or existing AI-agent destination.
• Business-initiated calls require active user permission. Request permission first, wait for Meta's status, then initiate the call with an RFC 4566 SDP offer.
• TryVox stores lifecycle events and duration. Recording, transcription, and summaries are available only when the route uses a compatible TryVox media bridge; they are not Meta-native artifacts.

Configuration

Connect the WhatsApp Business Account once. TryVox discovers its numbers, enables messaging, and activates Calling automatically wherever Meta reports support. Business-initiated calls still require the customer's Meta permission; that mandatory permission is requested from WhatsApp Calling → Permissions.

Subscribe the Meta app to the WhatsApp Business Account calls webhook field and keep /webhooks/whatsapp publicly reachable over HTTPS. Production must set ENABLE_META_VALIDATION=true, META_APP_SECRET, META_VERIFY_TOKEN, ENCRYPTION_KEY, and a current META_API_VERSION supported by your Meta app.

After OAuth completes, TryVox lists every number on the selected WABA and synchronizes each number's verification, messaging, and Calling settings. Existing channels are updated in place and older connections are backfilled automatically. Users do not need a separate Calling connection, enable switch, or synchronization action.

The UI distinguishes messaging_ready, calling_ready, calling_setup_required, number_not_eligible, permission_missing, expired_token, unsupported_country, business_verification_required, and meta_configuration_error. The latest sanitized Meta response and synchronization timestamps are retained for troubleshooting.

Security and operations

Every API request is tenant-scoped by the gateway and channel ownership is rechecked in the service. Webhooks resolve the tenant from Meta's phone-number ID; tenant IDs from webhook bodies are never trusted. Keep customer webhook secrets encrypted and never log SDP or access tokens. Rate limits must be set conservatively and within Meta's permission-request limits.

Limitations

Calling availability, supported countries, permission windows, and request limits are controlled by Meta and can vary by business number. Enabling TryVox does not override them. Browser media requires WebRTC infrastructure; SIP, queue, recording, transcription, and AI-summary execution require the TryVox media bridge deployment.