Kinetix Messaging by Ppros

By Plugin Pros

0+ active installationsVersion 1.4.6

Answer WhatsApp, Messenger, Instagram, Telegram, SMS, email, and live chat from one WordPress inbox, with AI replies and team routing.

Description

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, a country-code phone field, 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, files you upload, 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, DeepSeek, 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 and does not choose the development-environment reason.

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). DeepSeek, Grok, and Claude answer from keyword search instead.

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.

DeepSeek (https://api.deepseek.com/chat/completions) — Service provided by DeepSeek: Terms of Use, 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 a reason other than “This is a development or staging site” POSTs the feedback over HTTPS so Plugin Pros can email support@pluginpros.co. This includes local sites such as omnimailbox.test. Choosing Skip & Deactivate, closing the dialog, or choosing This is a development or staging site deactivates the plugin without sending anything.

Data sent (only if the form is submitted and the development-environment reason is not selected): 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.

Installation

  1. Upload the plugin files to /wp-content/plugins/kinetix-messaging-by-ppros, or install through the WordPress plugins screen.
  2. Activate the plugin through the Plugins screen in WordPress.
  3. Open Kinetix Messaging → Inbox and configure your channel settings.

FAQ

Is the plugin free?

Yes. The plugin is free and GPL licensed. Some channels charge for their own APIs (for example WhatsApp Business or SMS providers), and AI providers bill you directly for your API key. Kinetix adds no fees on top.

Where are my conversations stored?

In your own WordPress database. Messages pass through the channel you connect (for example Meta or Telegram), and through your AI provider only if you turn AI Support on. See External services for exactly what is sent where.

Do I have to use AI?

No. AI Support is off by default. Without it, the inbox works as a normal shared team inbox, with optional auto-replies and an offline notice.

Can I debug my messaging channel on a local machine?

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.

After starting the tunnel, update WordPress → Settings → General → Site URL to the tunnel HTTPS address, flush permalinks, and re-register the webhook for your channel.

Can I debug my messaging channel on a subdomain?

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/*.

If your staging subdomain shares a server with production, ensure WP_HOME and WP_SITEURL in wp-config.php (or Settings → General) point to the correct subdomain so that the REST URL used for webhooks is accurate.

What should I check if I can’t get Messenger and WhatsApp working?

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.

How do I add a messaging button to my WordPress pages?

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.

Optional attributes: label="Chat with us", style="link" (plain anchor instead of pill button), class="my-class".

Can multiple agents use the inbox at the same time?

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.

How do I send automated welcome or auto-reply messages?

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.
  • Live Chat — enable auto-reply in Settings → Live Chat → Messaging.

How do I add Live Chat to my website?

Open Kinetix Messaging → Settings → Live Chat, paste an API key from livechat.pluginpros.co, enable the channel, and save. The chat widget appears on every public page automatically. Visitor messages show up in the inbox; agent replies are sent back through the same live chat room.

Live Chat does not need a public webhook URL, so it can be tested on localhost as long as the site can reach livechat.pluginpros.co.

Screenshots

Changelog

1.4.6

  • Move AI Support to its own menu under Kinetix Messaging, next to Inbox.
  • Add DeepSeek as an AI provider. Replies use the DeepSeek chat API, and knowledge-base search uses keywords because DeepSeek does not provide embeddings.
  • Show an overview video on the plugin page.

1.4.5

  • Show the WhatsApp icon in the live chat window and on inbox messages, and open the connected phone number when the display field contains a business name.
  • WhatsApp Test connection registers the message webhook and shows why messages are not arriving.
  • Keep a numeric Webhook Verify Token as text so Meta can verify it.
  • Let the desktop pop-up switch turn on when the inbox is not served over HTTPS. Pop-ups still appear only while the inbox tab is in the background.
  • Add “This is a development or staging site” to the deactivation form. That choice sends nothing. Any other submitted reason, including from a local site, is emailed to support@pluginpros.co.

1.4.4

  • Include the contacts class that the 1.4.3 download left out. Without that file the plugin could not load.

1.4.3

  • Add Verify or Test connection on Settings for Messenger, WhatsApp, Instagram DM, LINE, WeChat, Viber, and SMS. Each check uses the saved credentials and shows the provider’s result. SMS checks the selected provider without sending a message.
  • LINE sending now uses the channel access token saved in Settings.
  • Return the Meta webhook challenge as plain text for Messenger, WhatsApp, and Instagram, so the Callback URL can be verified.
  • Use Meta Graph API v23.0 for Messenger, Instagram DM, and WhatsApp.
  • Upload several knowledge-base files at once under Settings → AI Support. Text, Markdown, CSV, HTML, JSON, RTF, DOCX, and PDF are each indexed as their own article.
  • Restyle the knowledge-base upload and article cards for light and dark mode.

1.4.2

  • Require a phone number before a Live Chat visitor can send a message. The country menu is sorted A–Z and shows the letter code first, such as BD +880 or US +1. The saved number is that dialing code plus the digits they type.
  • Add a Phone country code setting under Settings → Live Chat → Widget. That code is the default selection in the chat window.
  • Remove the starter prompt and starter buttons from the Live Chat window. The welcome heading stays.
  • Merge the same person across channels when a trusted email, a WhatsApp, SMS, or Live Chat phone number, or a logged-in WordPress user matches. The All view groups those conversations under one contact, and a reply still goes out on the latest thread’s channel.
  • Show the visitor’s email and then their phone in the conversation details.

1.4.1

  • Let Live Chat visitors and agents send images, GIFs, and PDFs. Files are saved in the WordPress media library and show in the chat widget and the inbox.
  • Accept JPEG, PNG, GIF, WebP, and PDF uploads up to 8 MB, and reject other file types.

1.4.0

  • Add browser notifications: a bell in the inbox sidebar turns on desktop pop-ups and a sound for new customer messages, set per agent and per browser. Clicking a pop-up opens the conversation.
  • Show the number of unread conversations in the browser tab title.
  • Keep checking for new messages about every 30 seconds while the inbox is in a background tab.
  • Notify agents about conversations assigned to them, and about unassigned conversations the AI isn’t handling unless they are set to Away.
  • Add Settings → Notifications with email alerts when a conversation is assigned to an agent. By default, the email is only sent when the agent is offline or away.
  • Optionally email a reminder when a customer has waited 5, 10, 15, 30, or 60 minutes without a reply. It goes to the assigned agent, otherwise the department’s agents, otherwise all agents, and is sent once per unanswered message.
  • Email links and ?conversation= links open that conversation directly in the inbox.

1.3.0

  • Add agent presence: agents set themselves Online or Away from their avatar in the inbox sidebar. Online agents stay available while the inbox or any admin page is open, including in a background tab, and go offline after about 3 minutes without activity or when the inbox tab closes.
  • Show each agent’s Online, Away, or Offline status in the assignee dropdown and in Settings → Agents & Departments.
  • Add Settings → Availability with weekly business hours in the site timezone, including overnight and 24-hour days.
  • Optionally treat the team as offline when no agent is online, even inside business hours.
  • Add an optional offline notice with {{hours}}, {{next_open}}, and {{customer_name}} placeholders, sent at most once per conversation every 12 hours. While it is on and the team is offline, the channel’s “an agent will reply shortly” auto-reply is skipped.
  • AI Support now assigns only agents who are online. When a department’s agents are all offline, the AI tells the customer when the team is back and keeps answering from the knowledge base.
  • When a customer asks for a human, the AI assigns an online agent from their department, or any online agent, and includes the offline notice if nobody is available.

1.2.0

  • Add AI Support (Settings → AI Support): when enabled, an AI assistant greets new unassigned conversations and replies on the same channel.
  • Support OpenAI, Grok (xAI), Claude (Anthropic), Gemini (Google), and any OpenAI-compatible endpoint, with preset base URLs and models for each provider.
  • Answer questions from a knowledge base (RAG) built from articles you add in settings and, optionally, your published WordPress posts and pages. Posts are re-indexed automatically when published, updated, or deleted.
  • Detect the right department from the conversation and assign the least-busy agent in it. If the department has no agents, assign an administrator to route it manually.
  • When no agents are set up in any department, the AI keeps answering from the knowledge base until a human is assigned.
  • Leave the conversation with a configurable wait message when the customer asks for a human, and stop replying once an agent is assigned.
  • Mark AI replies with an “AI” badge in the inbox and show whether the AI is handling or has handed off a conversation in the details sidebar.

1.1.2

  • Show HTML emails across the full conversation width instead of capping them at a chat-bubble width.
  • Show each conversation’s age from its last message, so opening a thread no longer makes an older conversation look a few hours old.

1.1.1

  • Fix a fatal error on activation from WordPress.org caused by a missing deactivation-feedback class in the 1.1.0 package.

1.1.0

  • Keep the conversation list and details sidebar visible on desktop, and hide them only on mobile when a thread is open.
  • Add an optional deactivation feedback popup on the Plugins screen that emails the reason to support@pluginpros.co.

1.0.9

  • Give each Live Chat visitor their own conversation room so new chats no longer attach to an old browser thread.
  • Auto-fill the widget name and email from the logged-in WordPress account and hide those fields when both are known.
  • Require a valid email before a guest can send a Live Chat message.
  • Show the conversation thread on mobile instead of leaving visitor messages off-screen, and keep the latest bubbles above the reply box.
  • Add Widget settings for the header tagline, welcome heading, starter prompt, and starter buttons.
  • Add step-by-step “Get a free API key” instructions on Settings → Live Chat → API Setup.

1.0.8

  • Add Live Chat channel with an on-site widget (livechat.pluginpros.co WebSocket rooms) and inbox delivery for visitor conversations.

1.0.7

  • Fix inbound IMAP messages using quoted-printable or base64 transfer encoding never being decoded, due to incorrect PHP IMAP encoding constants — a major cause of emails silently failing to sync or storing raw, unreadable content.
  • Fix imported email HTML rendering broken/mangled content: leaked <style>/<script> text (including @media blocks) appearing as visible text above messages, and garbled tag attributes left behind by double-processed quoted-printable content.
  • Add a dedicated inbound-email HTML sanitizer that repairs quoted-printable corruption and strips leaked style/script residue before falling back to wp_kses_post(), instead of relying on wp_kses_post() alone.
  • Add a one-time automatic migration that re-sanitizes all previously-stored email messages on update, so already-imported threads are repaired without waiting for a new message to arrive.
  • Add scoped CSS for imported email HTML (tables, lists, images, links, blockquotes) so messages render with sane spacing and stay within the message bubble.
  • Add manual “Sync now” button and background sync status panel to Settings → Email, with theme-aware styling so it’s visible in both light and dark mode.
  • Switch IMAP polling to a UID-based incremental sync so already-read messages fetched by other mail clients are no longer missed.
  • Add per-message error logging during IMAP polling instead of silently skipping failed messages.

1.0.6

  • Confirm compatibility with WordPress 7.1 and update “Tested up to” to 7.1.

1.0.5

  • Add Share & Embed panel to every channel settings page with a one-click copyable direct link (WhatsApp wa.me, Telegram t.me, Messenger m.me, etc.).
  • Add [kmbp_channel_button] shortcode for embedding a branded channel button or link on any page, with Gutenberg block and Elementor widget instructions.
  • Add delete message action in the conversation view (admin / settings-manager only).
  • Add delete conversation (thread) action in the conversation list (admin / settings-manager only).
  • Add dedicated REST endpoints: DELETE /kmbp/v1/messages/{id} and DELETE /kmbp/v1/conversations/{id}.
  • Add FAQ section to readme.txt and the in-plugin Help page covering local/subdomain debugging, Messenger & WhatsApp troubleshooting, multi-agent usage, shortcode embeds, and auto-replies.
  • Update plugin tags to include social-media, messenger, chat, and social for better discoverability.
  • Fix ChannelSharePanel text contrast in light mode via React context theme propagation.
  • Fix PHPCS warnings: unslash and sanitize $_SERVER header reads; escape RENAME TABLE identifiers with esc_sql().
  • Update .distignore to exclude editor-tooling directories (.agents, .codex, .cursor) and empty legacy lang/ folder from release ZIP.

1.0.4

  • Add delete conversation and delete message actions in the inbox (admin-only).
  • Add REST endpoints to permanently remove threads and individual messages.
  • Add Screenshots section to plugin readme.
  • Sanitize webhook request headers read from the server environment.
  • Harden legacy table rename migration for PHPCS compliance.

1.0.3

  • Replace short sme prefix with kmbp for options, tables, capabilities, and REST namespace.
  • Fix MessageBird legal URLs in readme.
  • Remove remote image URLs from admin embed snippets.

1.0.2

  • Address WordPress.org plugin review feedback (webhook permissions, enqueued admin CSS, menu position).

1.0.1

  • Initial release.
  • Document external messaging APIs and SMS providers in readme.
  • Ship src/ source and document build steps for compiled admin assets.