WhatsApp User
Customer starts or continues an expected support conversation.
3CX Middleware
Connect 3CX with Transactional WhatsApp Messaging
Route inbound WhatsApp support messages into 3CX and reply from 3CX within the active conversation window while keeping responsible messaging controls active.
Flow
3CX support flow
Inbound WhatsApp conversations can move into 3CX support workflows, while replies still pass back through WhatsApp Gateway controls.
WhatsApp Gateway
Records the message, handles opt-outs, and prepares a normalized support event.
3CX Support Workflow
Agents receive the event in the configured 3CX destination.
Controlled Reply
Replies go through purpose, limit, suppression, and conversation-window checks.
What It Does
Connect 3CX conversations to controlled WhatsApp delivery
Forward inbound WhatsApp messages into 3CX workflows
Reply to active WhatsApp conversations from 3CX
Send controlled missed-call or voicemail replies only inside the active conversation window
Keep fair-use limits, opt-outs, and policy checks active
Best Use Cases
Built for support, service, and operational workflows
Missed call follow-up inside active conversations
Support queue updates
Agent replies in active WhatsApp conversations
After-hours acknowledgement
Voicemail received notification
Internal team alerts
Customer service updates
Call-event automation
How It Works
Five-step setup
Step 1
Configure 3CX integration in customer dashboard
Step 2
Rotate and copy webhook secret
Step 3
Select WhatsApp instance
Step 4
Enable inbound, outbound, or call events
Step 5
Monitor events and policy logs
Responsible Messaging
Responsible controls stay active
3CX middleware is not a marketing or campaign sender. 3CX-style WhatsApp replies require the WhatsApp user to message first and are limited to the active conversation window. All outbound WhatsApp messages from 3CX pass through WhatsApp Gateway responsible messaging controls, including message purpose validation, fair-use limits, suppression checks, pause controls, and policy logging.
Security Highlights
Designed for controlled machine-to-machine webhooks
Webhook secret validation
Optional IP allowlist
Optional HMAC signing
256KB payload limit
Rate limiting
Sanitized logs
Admin monitoring
Developer Example
Outbound message event
POST /integrations/3cx/webhook/{integration_id}
X-WhatsApp-Gateway-3CX-Secret: ********
Content-Type: application/json
{
"event_type": "outbound_message",
"to": "+966500000000",
"message_text": "Your support ticket has been updated.",
"message_purpose": "support",
"conversation_id": "3cx-chat-123",
"agent_extension": "101"
}Ready to connect 3CX with WhatsApp Gateway?
WhatsApp Gateway is independent and not affiliated with WhatsApp, Meta, or 3CX.