Two messaging UX patterns most consumer apps converged on: pin a message to keep an announcement visible at the top of a thread, and pin a conversation to keep an important thread visible at the top of the inbox. Better Messages supports both — moderators pin specific messages in group conversations and chat rooms, while every user pins their own conversations to the top of their personal inbox.
A messaging plugin on a community site, a marketplace, or a paid membership platform has to answer one question repeatedly: who is allowed to message whom? The answers vary by site. A B2B directory might let businesses message each other freely but block consumer-to-consumer DMs. A paid community might let Pro members message anyone but block Free members from initiating. A LMS might let students message instructors but not other students. Better Messages handles all of this with a role-based access matrix, four kinds of restrictions, per-role rate limiting, and user-controlled DM-blocking.
GDPR (and the wave of similar laws — CCPA, LGPD, PIPEDA) means every WordPress site processing personal data needs three things: a clear privacy footprint, working data-export tools, and a working erasure path. For a messaging plugin, "personal data" includes message content, IP addresses, optional guest emails, and metadata about who talked to whom and when. Better Messages is built to fit cleanly into WordPress's built-in privacy tools, with all message data stored on your own server and zero default tracking.
Originally published when Better Messages added its initial PeepSo integration in v1.9.9.150 (mid-2021). This post has been kept up to date as the integration matured — PeepSo Groups messaging, the audio / video call buttons on PeepSo profiles, and the PeepSo Block Theme dark-mode mirror were all added in later releases.
Better Messages adds a WordPress-native real-time messenger to PeepSo sites, hooking into every PeepSo surface: the header navigation, every user profile, the members directory, the friends list, and PeepSo Groups. If you are using PeepSo Core: Chat, deactivate it after installing Better Messages to avoid a double-messenger conflict.
Originally published when Better Messages added the BuddyBoss Theme header replacement in v1.9.9.103–106 (early 2021). The post has been kept up to date as the integration matured — the live unread counter in the profile dropdown, the members-directory call icons, the bbPress reply integration, and the BuddyBoss ReadyLaunch rendering path are all later additions. ReadyLaunch support shipped in v2.15.10 (May 2026).
Better Messages turns BuddyBoss Platform messaging into a modern WordPress-native messenger — real-time delivery on its own WebSocket cloud (no third-party service to manage), group conversations, file uploads, voice messages, voice and video calls, AI bots, end-to-end encryption, web push, and a native mobile app. When activated, Better Messages takes over every BuddyBoss messaging link and auto-disables BuddyBoss Live Messaging to avoid a double-messenger conflict. The integration has two rendering paths — one tuned for the ReadyLaunch theme and one for the classic BuddyBoss Theme — and switches between them automatically based on which one is enabled on the site.
Originally published when Better Messages added the first dedicated Ultimate Member integration in v1.9.9.77 (early 2021). This post has been kept up to date as the integration matured — UM Friends, UM Followers, UM Groups, and the embedded profile Messages tab were all added in later releases.
Better Messages adds a modern real-time messenger to Ultimate Member sites, taking over every Ultimate Member surface: the profile Messages tab, the Private Message button on user profiles and the members directory, and the UM Friends / UM Followers / UM Groups extensions. If you are using the Ultimate Member Messages add-on, deactivate it after installing Better Messages to avoid a double-messenger conflict.
Every messaging surface eventually deals with the same UX requirement: let members opt out of messages from specific other members, without involving an admin. WhatsApp, Signal, Telegram, Discord, Slack — all of them have a "Block this user" option in the conversation menu. Better Messages has the same: users block each other directly, the block is one-directional, and admins can control which roles are allowed to block and which roles are immune to being blocked.
WordPress sites that want to do anything custom on top of their messenger — a third-party mobile app, a Slack-style bridge, a webhook integration, a custom moderation flow, a chat-to-email gateway — need a clean API. Better Messages exposes a full REST API at /wp-json/better-messages/v1/. Every operation the React front-end performs is a documented REST call, with WordPress nonce auth for logged-in users and per-request token auth for guests.
The biggest conversion gap on most WordPress sites is the moment a visitor wants to ask a question and the site asks them to register first. For directory listings, marketplace product pages, customer support pages, and public community spaces — the right answer is often "let them chat without signing up." Better Messages supports guest chat: visitors enter a display name (and optionally an email), then participate in chat rooms or start threads with listing owners / vendors / support, exactly as a registered user would.
A messaging plugin that cannot share files is barely a messaging plugin in 2026 — members expect to drag an image into a chat the way they would in WhatsApp, send a 50MB video without worrying about the connection dropping, and trust that the file is not accessible by random visitors guessing URLs. Better Messages handles all of that: drag-and-drop attachments, resumable TUS uploads for large files, browser-side image and video optimization (WebAssembly), automatic EXIF / GPS stripping, and proxy-based file access protection.