WhatsApp Calling (Adapted for Kewbot)

This page summarizes the current WhatsApp Business Calling model and how to plan it in Kewbot.

What this means operationally

• Calling availability is rollout-dependent and may vary by provider/account.
• Messaging remains the core baseline; calling is an extension flow.
• Businesses should treat calling as an optional channel with controlled rollout.

Typical customer journey

1. Customer starts in WhatsApp chat.
2. A call option becomes available (provider and account dependent).
3. Call is handled by connected voice infrastructure.
4. Team continues follow-up in chat when needed.

Kewbot integration guidance

• Keep routing ownership clear: chat logic in Kewbot, media/call path in the voice provider.
• Define fallback when call setup fails (for example, return to chat with a template or live message).
• Capture call outcomes in your CRM/helpdesk process to preserve context.

Compliance and rollout notes

• Feature availability can depend on Meta/provider activation.
• Calling policies and technical requirements can change; confirm in your provider console before production go-live.
• Run pilot traffic before broad enablement.

Minimum go-live checklist

• Verified WhatsApp Business setup
• Provider-side calling activation
• Tested inbound and outbound call paths
• Defined fallback and escalation paths

Screenshot coming soon.