Kinetix Messaging by Ppros

No — messaging platforms (Telegram, Meta, LINE, Viber, WeChat) deliver inbound messages via webhooks, which require a publicly reachable HTTPS URL. A local machine (localhost, 127.0.0.1, .test, .local) is not reachable from the public internet, so inbound webhook deliveries will fail silently. To test locally, use a tunnel tool to expose your machine temporarily:

• ngrok — ngrok http 80 gives you a public HTTPS URL.
• Cloudflare Tunnel — cloudflared tunnel --url http://localhost:80.
• Expose — expose share http://localhost.

Yes — a public subdomain works well for staging or development, as long as:

1. The subdomain resolves over HTTPS with a valid SSL certificate. Self-signed certificates are rejected by all platforms.
2. Port 443 is open and reachable from the public internet (not behind a VPN or corporate firewall).
3. No WAF, CDN rule, or security plugin is blocking unauthenticated POST requests to /wp-json/kmbp/v1/webhooks/*.

Both channels run on the Meta Graph API. Work through this checklist:

1. Verify Token mismatch — the token in Settings → WhatsApp/Messenger must exactly match the one entered in the Meta App → Webhooks configuration. Copy-paste it; do not retype.
2. Webhook fields not subscribed — in Meta App → Products → WhatsApp (or Messenger) → Configuration → Webhooks, make sure messages and messaging_postbacks are subscribed.
3. App in Development mode — while in Development mode only admins and testers of the Meta App can send messages. Submit for App Review to go live with real users.
4. Short-lived access token — user tokens expire after ~60 days. Generate a System User permanent token in Meta Business Settings → System Users.
5. Wrong App Secret — the App Secret validates the X-Hub-Signature-256 header on every inbound webhook. A mismatched secret causes the plugin to silently reject all incoming messages. Double-check it in Settings → WhatsApp → API Setup.
6. Phone Number ID vs. WABAID (WhatsApp only) — the Phone Number ID and WABA ID are different values. Check both in Meta Business Manager → WhatsApp → API Setup.

Use the built-in shortcode [kmbp_channel_button channel="whatsapp"]. Open Kinetix Messaging → Settings → (any channel) → Share & Embed to get the exact shortcode for that channel, with one-click copy. The panel also shows ready-to-paste snippets for:

• Gutenberg — add a Shortcode block and paste.
• Elementor — drag the Shortcode widget and paste.

Yes. Assign the built-in Messaging Agent role (or the kmbp_access_messaging capability) to as many team members as needed. Each agent logs into WordPress independently and opens the Kinetix Messaging inbox. Conversations can be assigned to specific agents via the right-hand panel in the conversation view. The inbox polls for new messages every 8 seconds so all agents see updates in near-real time without refreshing.

Most channels have a dedicated auto-reply option in their settings panel:

• All channels — enable the Auto-reply toggle and write your message in the text field that appears. The message is sent automatically when a new conversation starts.
• Telegram — enable Auto-reply on /start in Settings → Telegram → Features. The welcome message fires when a user first sends /start to your bot.
• Messenger / Instagram — set a greeting in the Automation tab.
• Email — configure the auto-reply subject and body in Settings → Email → Templates.