92 posts tagged with "Guides"

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.

GIFs are how casual conversation moves on social platforms — a reaction GIF answers a question faster than a sentence. WordPress sites running BuddyPress / BuddyBoss / PeepSo / Ultimate Member / FluentCommunity communities all hit the same gap: members expect a GIF button next to the message composer, and the native messengers do not have one. Better Messages adds a GIF picker that supports two providers — GIPHY (the world's largest GIF library, free API key) and KLIPY (a newer curated platform with optional ad-supported monetization).

Agencies, SaaS companies, and white-label community platforms running on WordPress need every part of the user experience to feel native — no "Powered by X" attribution leaking out of a plugin. Better Messages ships white-label by default: the messaging UI shows your site's branding only, with no plugin name, no "Powered by Better Messages" tag, and no third-party logo anywhere visible to end users.

WordPress sites serving members across multiple languages need the messenger UI in every member's language — buttons, menus, modals, error messages, the whole shell. Better Messages is fully translatable through the standard WordPress translation pipeline: every user-facing string is wrapped with the WordPress __() and _x() functions, exposed under the bp-better-messages text domain, and reachable through Loco Translate, WPML, Polylang, or a manually placed .po/.mo file.

Email notifications are the bridge between members who live in their inbox and a messenger they only open occasionally. Done badly, they spam — every message triggers a separate email and the recipient mutes the whole thing within a week. Done well, they batch intelligently, respect the user's online state, and look like part of your site's brand. Better Messages handles email notifications with smart grouping (one email per thread per batch window), online-state awareness (no email until the recipient has been away a while), and customizable templates (Simple visual mode, Custom HTML mode, or BuddyPress template integration).

A messenger that shows a pasted URL as a plain blue link is missing one of the modern messaging UX defaults: when someone shares a YouTube link, a Vimeo video, a tweet, or a product page, the messenger should expand it into a rich preview with the image, title, and (for videos) an inline player. Better Messages has supported embedded links via WordPress's native oEmbed system since the early 1.x versions — paste a URL, the preview appears in the message. Click the play button, the video plays inline without leaving the chat.

A messenger that lives only on its own page asks members to leave whatever they were reading to check messages. A floating chat window — the Facebook-style popup that follows the user across every page of the site, with multiple conversations open at once at the bottom of the screen — keeps the conversation present without breaking the reading flow. Better Messages has shipped floating mini-chat windows since the early days, with one-tap open from BuddyPress / BuddyBoss profiles and per-conversation popups that stick across page navigations.