Better Messages plugin review and common issues

Check the Better Messages status in the plugin admin panel (Better Messages → Status). It shows whether WebSocket is connected or falling back to AJAX polling. WebSocket failures occur when: (1) the hosting environment blocks WebSocket connections (common on shared hosting); (2) a reverse proxy (Cloudflare, CDN) terminates WebSocket connections without forwarding them to the origin; (3) server-side firewall blocks WebSocket ports. When WebSocket is unavailable, Better Messages falls back to AJAX polling (which still delivers messages but with a slight delay). For true real-time messaging on shared hosting, contact hosting support about WebSocket support.

Go to Better Messages → Settings → Integration and verify BuddyBoss is selected as the active integration. Better Messages provides a “Replace BuddyBoss Messages” option that disables the BuddyBoss default messaging and activates Better Messages in its place. If already selected: (1) clear all caches; (2) verify both BuddyBoss Platform and Better Messages are updated to their latest versions; (3) check Better Messages documentation for any version-specific integration notes; (4) temporarily deactivate other BuddyBoss add-ons to rule out conflicts.

Video calls use WebRTC technology requiring: (1) HTTPS on both parties’ connections — WebRTC does not function on HTTP; (2) browser permission for camera and microphone — verify both users have granted media permissions; (3) firewall or network restrictions may block WebRTC media streams (UDP ports used for peer-to-peer media) — corporate or school networks often block these; (4) Better Messages Pro’s video calling uses a TURN server for fallback when direct peer connection fails — verify the TURN server configuration in Better Messages Pro settings; (5) test on a non-corporate network to rule out firewall restrictions.

Better Messages has native Dokan integration. Go to Better Messages → Settings → Integration and enable Dokan. With Dokan integration active: customers who view a vendor’s store page see a “Send Message” button; clicking it opens a Better Messages conversation with the vendor; messages are linked to the Dokan store context; vendors manage conversations from their Dokan vendor dashboard using the Better Messages interface. Conversation history is preserved and accessible to both parties. Configure in Better Messages → Settings → Dokan whether conversations are pre-seeded with order information.

Better Messages → Settings → Permissions allows configuring who can initiate conversations. Set the minimum user role to “Subscriber” (the lowest registered user role) — this ensures only logged-in users can access the messaging interface. For BuddyBoss/BuddyPress communities, messaging is naturally tied to community membership. For standalone WordPress sites, Better Messages can display a “Please log in to message” prompt to unauthenticated visitors. Additional permission rules can restrict messaging based on membership level when integrated with MemberPress or Paid Memberships Pro.

No — Better Messages works with or without BuddyPress. It can be used as a standalone messaging system on any WordPress site, providing user-to-user messaging based on WordPress user accounts. When BuddyPress, BuddyBoss, Ultimate Member, or PeepSo is active, Better Messages integrates with those platforms’ user systems and friend/connection structures. Without a community plugin, Better Messages provides direct messaging based on WordPress user IDs with a user search function to find conversation partners.

Better Messages is a member-to-member messaging system primarily designed for community use — not specifically for customer support workflows. For customer support (operator-to-visitor chat with ticketing, queue management, and CRM integration), dedicated support chat plugins like Crisp, Intercom, or Tidio Chat are more appropriate. Better Messages is excellent for community member conversations, marketplace vendor-customer messaging, and team communication within a WordPress-based platform.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.