Kinetix Messaging by Ppros

Every customer conversation in one inbox, inside WordPress. Kinetix Messaging connects your messaging channels to a shared team inbox in your WordPress admin. Your agents reply from one screen, an optional AI assistant answers from your own content, and conversations go to the right person automatically.

Features

Channels in one inbox

• Live Chat website widget, with a welcome message, starter buttons, and image, GIF, and PDF uploads.
• WhatsApp Business, Facebook Messenger, and Instagram DM through the Meta Graph API.
• Telegram, LINE, Viber, and WeChat.
• SMS through Twilio, Vonage, Sinch, Plivo, Telnyx, or MessageBird.
• Email over SMTP and IMAP, or inbound webhooks from Mailgun, SendGrid, Postmark, or SparkPost.

Team inbox

• Assign conversations to agents and organise agents into departments.
• A Messaging Agent role that gives team members the inbox and nothing else in wp-admin.
• Online and Away status for each agent. New chats are only auto-assigned to agents who are online.
• Quick replies, status (open, pending, resolved), and priority.
• Search and filter by channel or status. New messages appear without refreshing the page.
• Browser notifications with sound and an unread count in the tab title, so agents notice new chats in a background tab.
• Email alerts when a conversation is assigned to an agent, or when a customer has waited too long for a reply.
• Light and dark themes.

AI Support (optional)

• An AI assistant greets new conversations and answers from a knowledge base you control: articles you write, plus your published posts and pages if you choose.
• Detects which department a question belongs to and assigns an online agent from that team.
• Hands over to a human whenever the customer asks, with a wait message you write.
• Works with OpenAI, Claude (Anthropic), Gemini (Google), Grok (xAI), or any OpenAI-compatible endpoint, using your own API key.

Availability and automation

• Weekly business hours in your site’s timezone, including overnight shifts.
• An offline notice that tells customers when you’re back.
• Auto-replies for each channel.
• Share links and a [kmbp_channel_button] shortcode for any channel. It works in Gutenberg and Elementor.

Why Kinetix

• It lives in WordPress. No separate dashboard and no extra logins: your agents are WordPress users and the inbox sits in wp-admin.
• Your conversations stay in your database. Messages are stored in your own WordPress database, not on a third-party helpdesk.
• All your channels in one place. WhatsApp, Instagram, Telegram, SMS, email, and live chat share one inbox instead of six apps.
• AI on your terms. Use the AI provider you prefer with your own key, and pay that provider directly. AI is off until you turn it on, and customers can always reach a human.
• Free and open source. GPLv2 licensed, with the full source code public on GitHub.

Quick start

1. Install and activate the plugin.
2. Open Kinetix Messaging → Inbox and click the gear icon to open Settings. Choose a channel, paste its credentials, and switch it on.
3. Add teammates as WordPress users with the Messaging Agent role, and assign them to departments under Agents & Departments.
4. Optional: set business hours under Availability and switch on AI Support.

External services

This plugin is an omnichannel messaging inbox. It does not call any third-party API until a site administrator enables a channel and saves that channel’s credentials in the plugin settings. No external requests are made on ordinary WordPress page loads for visitors, except when Live Chat is enabled: the public widget then opens a WebSocket to livechat.pluginpros.co so visitors can chat. Outbound API calls otherwise occur only when an authorized agent sends a message, when the plugin registers or checks a webhook, when optional auto-replies are sent, when scheduled email polling runs (IMAP, if configured), when the optional AI Support feature is enabled with an administrator-supplied API key, or when an administrator optionally submits the deactivation feedback form.

Inbound messages are delivered to your WordPress site by the messaging provider via webhooks you configure in each provider’s dashboard. Those providers may send message content, sender identifiers, and profile metadata to your site.

The shared HTTP client (wp_remote_request) in the plugin is used to reach the services below.

Telegram

Used when the Telegram channel is enabled. The plugin calls the Telegram Bot API (https://api.telegram.org/bot) to register the inbound webhook, send outbound messages, send optional auto-replies, and fetch webhook status.

Data sent: bot token (in the request URL), recipient chat ID, message text, webhook URL pointing to your site, and optional webhook secret token.

Service provided by Telegram FZ-LLC: Terms of Service, Privacy Policy.

Meta Graph API (WhatsApp, Messenger, Instagram)

Used when the WhatsApp, Messenger, or Instagram channel is enabled. The plugin calls the Meta Graph API (https://graph.facebook.com/v19.0/) to send outbound messages, send optional auto-replies, and look up sender profile information for inbound conversations.

Data sent: page or user access token, WhatsApp phone number ID (WhatsApp channel), recipient platform ID or phone number, message text, and API version path.

Service provided by Meta Platforms, Inc.: Terms of Service, Privacy Policy. Developer platform terms: Meta Platform Terms. WhatsApp Business terms: WhatsApp Business Terms.

LINE

Used when the LINE channel is enabled. The plugin calls the LINE Messaging API (https://api.line.me/v2/bot/) to send outbound messages and optional auto-replies.

Data sent: channel access token, recipient user ID, and message text.

Service provided by LINE Corporation: Terms of Use, Privacy Policy.

Viber

Used when the Viber channel is enabled. The plugin calls the Viber REST API (https://chatapi.viber.com/pa/) to register the inbound webhook, send outbound messages, and send optional auto-replies.

Data sent: authentication token, recipient user ID, message text, and webhook URL pointing to your site.

Service provided by Rakuten Viber: Terms of Use, Privacy Policy.

WeChat

Used when the WeChat channel is enabled. The plugin calls the WeChat Official Account API (https://api.weixin.qq.com/cgi-bin/) to obtain access tokens, look up user profiles, and send outbound messages.

Data sent: app ID, app secret, access token, recipient open ID, and message text.

Service provided by Tencent: Terms of Service, Privacy Policy.

SMS providers

Used when the SMS channel is enabled. Exactly one provider is used, based on the administrator’s choice in settings. The plugin sends outbound SMS and may send optional auto-replies through the selected API.

Twilio (https://api.twilio.com/2010-04-01/Accounts/) — Data sent: account SID, auth token, from number, recipient phone number, and message text. Service provided by Twilio Inc.: Terms of Service, Privacy Policy.

Vonage (https://rest.nexmo.com/sms/json) — Data sent: API key, API secret, from number, recipient phone number, and message text. Service provided by Vonage Holdings Corp.: Terms of Use, Privacy Policy.

Sinch (https://us.sms.api.sinch.com/xms/v1/) — Data sent: service plan ID, API token, from number, recipient phone number, and message text. Service provided by Sinch AB: Terms and Conditions, Privacy Policy.

Plivo (https://api.plivo.com/v1/Account/) — Data sent: auth ID, auth token, from number, recipient phone number, and message text. Service provided by Plivo Inc.: Terms of Service, Privacy Policy.

Telnyx (https://api.telnyx.com/v2/messages) — Data sent: API key, from number, recipient phone number, and message text. Service provided by Telnyx LLC: Terms and Conditions, Privacy Policy.

MessageBird (https://rest.messagebird.com/messages) — Data sent: access key, originator number, recipient phone number, and message text. Service provided by Bird (MessageBird): Terms of Service, Privacy Policy.

Email (administrator-configured)

The email channel does not use a fixed third-party API endpoint. When enabled, the site administrator supplies their own SMTP and/or IMAP server hostname and credentials. The plugin connects only to those administrator-configured mail servers to send outbound email or poll for inbound messages (every 5 minutes via WordPress cron, when IMAP is configured).

Inbound email may also be pushed to your site via a webhook URL you configure in an inbound-parse or route service chosen by the site administrator. Common options include:

Mailgun — Data sent: sender/recipient addresses, subject, message body, and attachments (as configured in your Mailgun route). Service provided by Sinch Mailgun: Terms of Service, Privacy Policy.

SendGrid — Data sent: sender/recipient addresses, subject, message body, and attachments (as configured in your Inbound Parse webhook). Service provided by Twilio SendGrid: Terms of Service, Privacy Policy.

Postmark — Data sent: sender/recipient addresses, subject, and message body (as configured in your Postmark inbound webhook). Service provided by ActiveCampaign, LLC (Postmark): Terms of Service, Privacy Policy.

SparkPost — Data sent: sender/recipient addresses, subject, and message body (as configured in your SparkPost relay webhook). Service provided by Message Systems, LLC (SparkPost): Terms of Use, Privacy Policy.

Data sent (general): depends on the mail server or inbound-parse provider the administrator configures (typically sender/recipient addresses, subject, and message body).

Live Chat (livechat.pluginpros.co)

Used when the Live Chat channel is enabled. The public site widget and agent replies connect to the livechat.pluginpros.co WebSocket service (wss://livechat.pluginpros.co/ws/chat/<room_id>/) using the API key saved in Settings. Visitor messages are also stored in your WordPress database so they appear in the inbox.

Data sent: API key, conversation room ID, sender name, sender type (visitor or agent), and message text.

Service provided by Plugin Pros (livechat.pluginpros.co). Sign in and generate an API key at livechat.pluginpros.co.

AI Support providers

Optional and off by default. AI is configured entirely inside this plugin (Settings → AI Support): the administrator turns the feature on, picks exactly one provider, and saves their own API key for it. Nothing is sent to any AI provider until that is done.

When enabled, the plugin calls the selected provider:

• when a customer message arrives in a conversation that has no human agent assigned, to decide which department it belongs to and to write a reply;
• when an administrator adds, edits, or re-indexes a knowledge-base article, and when a published post or page is saved while “Index WordPress posts & pages” is on, to create search embeddings (OpenAI, Gemini, and OpenAI-compatible endpoints only).

Data sent: the API key, the chosen model name, the customer’s latest message and up to the 12 most recent messages in that conversation, the names and slugs of your departments, and knowledge-base excerpts that match the question (from articles you add and, if enabled, your published posts and pages). No data is sent for conversations that already have a human agent assigned or where the customer asked for a human.

OpenAI (https://api.openai.com/v1/chat/completions and /v1/embeddings) — Service provided by OpenAI, L.L.C.: Terms of Use, Privacy Policy.

Grok by xAI (https://api.x.ai/v1/chat/completions) — Service provided by X.AI LLC: Terms of Service, Privacy Policy.

Claude by Anthropic (https://api.anthropic.com/v1/messages) — Service provided by Anthropic, PBC: Commercial Terms, Privacy Policy.

Gemini by Google (https://generativelanguage.googleapis.com/v1beta/models/) — the API key is sent as a URL query parameter, as Google’s API requires. Service provided by Google LLC: Gemini API Additional Terms, Privacy Policy.

OpenAI-compatible endpoint — the same data is sent to the base URL the administrator enters (for example Azure OpenAI, Groq, or a self-hosted Ollama server). The terms and privacy policy of that service apply.

Deactivation feedback

Optional. When an administrator deactivates the plugin from the Plugins screen, they may submit a short feedback form. Submitting the form POSTs the feedback over HTTPS so Plugin Pros can email support@pluginpros.co. This does not depend on the site’s PHP mail() / sendmail setup, so it also works on local development sites. Choosing Skip & Deactivate (or closing the dialog) deactivates the plugin without sending anything.

Data sent (only if the form is submitted): deactivation reason, optional comments, site URL, WordPress version, PHP version, plugin version, and the administrator’s name and email (used as Reply-To).

Primary endpoint: https://pluginpros.co/wp-json/kmbp/v1/deactivate-feedback — Service provided by Plugin Pros: pluginpros.co. Contact: support@pluginpros.co.

Source code

The human-readable source for the compiled admin UI lives in the src/ directory inside this plugin (React/JSX, CSS). The minified files in build/ are generated from that source.

Public source repository: https://github.com/sakib08/Omnichannel

Build tools

The admin inbox is built with @wordpress/scripts (webpack), React 19, and Tailwind CSS 4.

Regenerating build/ assets

From the plugin root directory:

1. Install Node.js 18+ and npm.
2. Run npm install
3. Run npm run build

This compiles src/ into build/index.js, build/index.css, and related files, and copies Tabler icon fonts into assets/tabler-icons/ (via a local build script; shell scripts are not shipped in the WordPress.org ZIP).

To create a distributable ZIP locally: npm run bundle

Third-party licenses

This plugin is free software released under the GPLv2 (or later). All bundled libraries and assets included in the distributed plugin are licensed under the GPL or another GPL-compatible license (MIT, BSD, etc.).

The following components are bundled in the distributed plugin (compiled into build/ or copied to assets/).

• React and React DOM — MIT License (GPL-compatible). Copyright Meta Platforms, Inc. https://github.com/facebook/react
• Tabler Icons (webfont in assets/tabler-icons/) — MIT License (GPL-compatible). Copyright Paweł Kuna. https://github.com/tabler/tabler-icons — See assets/tabler-icons/LICENSE.
• @wordpress/scripts build output — GPLv2 or later (WordPress ecosystem). https://github.com/WordPress/gutenberg/tree/trunk/packages/scripts

Development-only tools (npm packages used at build time, not included in the plugin ZIP) are not distributed with this plugin.