10 posts tagged with "WebSocket"

Voice messages are the right tool for chat moments when typing is slow or the relationship is personal — but they have one universal problem: the recipient cannot always listen. They are in a meeting, on a noisy train, or simply prefer text. Better Messages adds AI voice-message transcription to bridge the gap: any participant in a thread can click the transcribe button on a voice message and a text version appears below it, in any of 99+ languages, with results cached so the next viewer sees the text instantly. Two providers — Better Messages Cloud AI (included with the WebSocket license, no third-party key) or OpenAI (free with your own OpenAI key).

Most WordPress messaging plugins store every message in plaintext in the database. Anyone with access to the database — a site admin, a host's support engineer, an attacker who exfiltrates a database backup — can read every conversation. For most sites that is acceptable. For some sites — therapists with clients, lawyers with opposing parties, journalists with sources, founders discussing acquisition terms — it is not. Better Messages 2.13 introduced optional per-thread end-to-end encryption: messages are encrypted in the sender's browser, stay encrypted at rest, and are decrypted in the recipient's browser. The database holds ciphertext only.

Public chat surfaces — community lobbies, vendor support inboxes, course cohort chats — get spam, harassment, and inappropriate content the way any open input does. Manual moderation does not scale beyond a few hundred members. Better Messages adds AI-powered content moderation that automatically detects harmful messages and either flags them for admin review or holds them until approved. Two providers are supported: Better Messages Moderation AI (no API key required, included with the WebSocket license) and OpenAI Moderation API (free with your own OpenAI key).

WordPress communities that span multiple countries hit the same wall: the chat feed becomes a polyglot mess where half the members cannot read what the other half wrote. Static translation plugins (WPML, Polylang) translate site content but not user-generated message bodies. Better Messages handles this with AI message translation: each member sets their preferred display language; messages from other members are auto-translated by an AI provider on the fly. The sender writes in their language, the recipient reads in theirs — both sides see the original on hover.

Site owners running paid communities, course academies, and vendor marketplaces consistently hit the same wall: members live on their phone, not their browser. A site without a mobile app loses the daily-engagement signal — push notifications never reach the user, the site tab goes stale, members drift to Discord or Slack where the app experience is native. Better Messages ships native iOS and Android apps built on Capacitor that members install from the App Store / Play Store and use as the on-the-go front door to your community's chat.

Progressify turns a WordPress site into a Progressive Web App — installable to the home screen, capable of offline-aware browsing, and able to send web push notifications even on iOS Safari (where standard web push has long been limited). Better Messages auto-detects Progressify and routes private-message push notifications through it, so members who installed your PWA see new-message notifications the same way they see any other PWA notification.

WordPress sites that need video calls have three options today: link out to Zoom (loses the on-site context), embed Whereby / Daily / Twilio (third-party billing, separate UI), or roll your own (a multi-month engineering project involving a media server, TURN/STUN, signaling, and a UI). Better Messages adds a fourth path: voice and video calls inside the messenger threads members are already using, hosted on relay servers included in the WebSocket license, with both one-on-one and group call support.

Building a WordPress site with AI chat bots is now a one-day project, not a six-month one. The hard parts — model selection, API key management, streaming responses, conversation context, system prompts — are commoditized across providers (OpenAI, Anthropic Claude, Google Gemini). What is still missing is the WordPress-native messenger layer that puts the bot in front of your members where conversations already happen, in the same UI as private DMs and group chats. Better Messages closes that gap: configure an OpenAI / Claude / Gemini bot once, and it shows up as a regular user inside the messenger, with streamed responses, custom personality, and the same UX members already use for human DMs.

OneSignal is the most-installed web-push notification plugin on WordPress — it adds the browser permission prompt, manages subscriptions, and delivers push notifications through OneSignal's hosted service. The standard OneSignal WordPress plugin sends push notifications for new posts but does not natively know about private messages. Better Messages adds the missing piece: it auto-associates WordPress user IDs with OneSignal subscriptions as External User IDs, then dispatches a OneSignal push for every new private message so recipients hear about it even when their browser is closed or the site tab is in the background.

The single biggest UX gap between a WordPress messaging plugin and a serious modern messenger is delivery latency — how long it takes a sent message to appear in the recipient's window. A page-reload messenger feels like email. An AJAX-polling messenger feels like a fast email. A WebSocket-powered messenger feels like WhatsApp. Better Messages supports both shapes — AJAX polling on the free version (no separate server, runs on any WordPress hosting) and WebSocket on the paid version (instant delivery, online presence, typing indicators) — so any site can pick the right delivery mode for its scale.