Kinetix Messaging by Ppros
| 开发者 | sakibbd08 |
|---|---|
| 更新时间 | 2026年10月27日 17:49 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
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.
- 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.
- 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.
- 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.
- 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.
- Install and activate the plugin.
- Open Kinetix Messaging → Inbox and click the gear icon to open Settings. Choose a channel, paste its credentials, and switch it on.
- Add teammates as WordPress users with the Messaging Agent role, and assign them to departments under Agents & Departments.
- Optional: set business hours under Availability and switch on AI Support.
安装:
- Upload the plugin files to
/wp-content/plugins/kinetix-messaging-by-ppros, or install through the WordPress plugins screen. - Activate the plugin through the Plugins screen in WordPress.
- Open Kinetix Messaging → Inbox and configure your channel settings.
屏幕截图:
常见问题:
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 80gives you a public HTTPS URL. - Cloudflare Tunnel —
cloudflared tunnel --url http://localhost:80. - Expose —
expose share http://localhost.
Can I debug my messaging channel on a subdomain?
Yes — a public subdomain works well for staging or development, as long as:
- The subdomain resolves over HTTPS with a valid SSL certificate. Self-signed certificates are rejected by all platforms.
- Port 443 is open and reachable from the public internet (not behind a VPN or corporate firewall).
- No WAF, CDN rule, or security plugin is blocking unauthenticated POST requests to
/wp-json/kmbp/v1/webhooks/*.
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:
- 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.
- Webhook fields not subscribed — in Meta App → Products → WhatsApp (or Messenger) → Configuration → Webhooks, make sure
messagesandmessaging_postbacksare subscribed. - 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.
- Short-lived access token — user tokens expire after ~60 days. Generate a System User permanent token in Meta Business Settings → System Users.
- Wrong App Secret — the App Secret validates the
X-Hub-Signature-256header on every inbound webhook. A mismatched secret causes the plugin to silently reject all incoming messages. Double-check it in Settings → WhatsApp → API Setup. - 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.
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
/startto 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.
更新日志:
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.
- 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.
- 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.
- 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.
- 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.
- Fix a fatal error on activation from WordPress.org caused by a missing deactivation-feedback class in the 1.1.0 package.
- 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.
- 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.
- Add Live Chat channel with an on-site widget (livechat.pluginpros.co WebSocket rooms) and inbox delivery for visitor conversations.
- 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@mediablocks) 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 onwp_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.
- Confirm compatibility with WordPress 7.1 and update "Tested up to" to 7.1.
- 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.
- 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.
- Replace short
smeprefix withkmbpfor options, tables, capabilities, and REST namespace. - Fix MessageBird legal URLs in readme.
- Remove remote image URLs from admin embed snippets.
- Address WordPress.org plugin review feedback (webhook permissions, enqueued admin CSS, menu position).
- Initial release.
- Document external messaging APIs and SMS providers in readme.
- Ship
src/source and document build steps for compiled admin assets.