`, ``) is universally supported. Even older devices render formatted messages correctly.
### Does formatting appear in email notifications?
Yes — email notifications include the formatted HTML, so bold and italic render correctly in modern email clients. Inline code and code blocks render in monospace.
### Can administrators restrict which formatting options are available?
The toolbar is hard-coded in the frontend. To restrict (e.g. disable code blocks), hide the corresponding buttons with custom CSS targeting their class names in **Appearance → Customize → Additional CSS**.
## See also
- [Markdown support](/docs/features/markdown-support/) — typed syntax alternative to the toolbar
- [Message reactions](/docs/features/message-reactions/) — emoji reactions on messages
- [Reply, edit, forward](/docs/features/reply-edit-forward/) — message-level actions
- [Mentions](/docs/features/mentions/) — @-mention picker
---
## Translate WordPress Chat Into Any Language
# Translations
Better Messages is **fully translatable using WordPress's native i18n system**. Every user-facing string is wrapped with standard WordPress translation functions, so any translation tool — [Loco Translate](https://www.wordplus.org/loco-translate), WPML, Polylang, or hand-edited `.po` files — works out of the box. Translations are distributed through WordPress.org's translation platform: when your site language matches a published translation, WordPress installs the `.mo` file automatically into `wp-content/languages/plugins/`.
## What it adds
- Every user-facing string is translatable through standard WordPress tools
- WordPress.org auto-installs translations for the site language whenever they're available
- Customize beyond translation — rephrase strings to match your brand voice
- Compatible with Loco Translate, WPML, Polylang, and any `.po/.mo` workflow
- Text domain: `bp-better-messages`
- RTL languages (Arabic, Hebrew, Persian, Urdu) mirror the entire UI automatically
## Available translations
Better Messages is community-translated on [translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/bp-better-messages/). The plugin ships with the source `bp-better-messages.pot` template; WordPress.org fills in `.mo` files for every locale that has been translated to the required coverage threshold. To see the current status of your locale (and contribute missing strings), visit the WordPress.org translations dashboard for the plugin.
## How it works
WordPress determines which language to load based on the site's WordPress language setting (or per-user language if a multilingual plugin is active). Better Messages relies on the standard WordPress `.mo` lookup — the file in `wp-content/languages/plugins/` (auto-installed from WordPress.org, or a custom file you place there) is loaded for the current locale.
| Translation source | Priority |
|---|---|
| Loco Translate site-specific overrides | Highest — overrides everything |
| Custom `.po/.mo` in `wp-content/languages/plugins/` | Higher than the WordPress.org default |
| WPML / Polylang per-user language | Per-user override |
| WordPress.org auto-installed translation | Default fallback when no custom file exists |
## When to translate
| Audience | Approach |
|---|---|
| Single-language site | Bundled translation activates automatically with site language |
| Multilingual site (per-user language) | Use WPML or Polylang — each user sees their language |
| Brand-customized strings | Loco Translate — override individual strings even in English |
| Untranslated language | Hand-create a `.po` file via Loco Translate or POEdit |
| RTL site | See [RTL support](/docs/features/rtl-support/) — direction auto-mirrors |
## How to translate
### Using Loco Translate (recommended)
1. Install and activate the [Loco Translate](https://www.wordplus.org/loco-translate) plugin
2. Navigate to **WP Admin → Loco Translate → Plugins → Better Messages**
3. Click **New language** to add a translation
4. Translate strings using the built-in editor
5. Save — strings activate immediately
### Using WPML or Polylang
These plugins automatically detect translatable strings from Better Messages and include them in their translation workflows. Each user sees the language they selected.
### Manual translation
Place your `.po/.mo` files in `wp-content/languages/plugins/` following WordPress naming: `bp-better-messages-{locale}.po`.
## Frequently asked questions
### Can different chat rooms have different languages?
The plugin renders in the user's session language, not per-room. To force a specific language per-room, hook the standard WordPress `locale` filter (or `determine_locale`) and return a custom locale based on the request context — Better Messages will then load the matching `.mo` file.
### Are AI bot replies translated?
The AI bot replies in whatever language the conversation is in (the LLM detects context). UI strings around the message (timestamps, sender labels) are translated via standard i18n.
### How do I contribute translations back to the project?
Translations are managed via Loco Translate locally. To contribute back to the bundled set, contact support — community translations are accepted and bundled in future releases.
### What if a string isn't translated yet — does it break the UI?
No — untranslated strings fall back to English. The UI never breaks; users see English text for any string not yet translated in their language.
### Does the mobile app respect translations too?
Yes — the mobile app uses the same translation files. The OS language determines what's loaded.
## See also
- [RTL layout support](/docs/features/rtl-support/) — Arabic, Hebrew, Persian, Urdu
- [AI message translation](/docs/features/ai-message-translation/) — auto-translate user messages between languages (WebSocket version)
- [Translate WordPress chat blog post](/blog/translate-wordpress-chat-multilingual/) — feature overview
---
## Unread Conversations Filter in WordPress Chat
# Unread Conversations Filter
Better Messages adds an **unread filter toggle** to the conversation list — one click hides every read thread and shows only the ones with new messages. Essential for users who run busy inboxes (community managers, marketplace vendors, support reps, instructors) where dozens of threads compete for attention.
## What it adds
- One-click filter button in the conversation list header
- Toggles between "All conversations" and "Unread only" views
- Configurable unread counter — count unread **messages** OR unread **conversations**
- Works across DMs, group chats, and chat rooms
- Filter state remembered per-session — survives page reloads
- Live updates — a new message arriving changes the filter result instantly (WebSocket version)
## How it works
The unread filter is a UI-only toggle that doesn't delete or archive anything — it temporarily hides read threads from the rendered list. The underlying data is unchanged. Clicking "All conversations" restores the full list.
| Counter mode | What the badge shows |
|---|---|
| **Unread messages** | Total count of unread messages across all threads (e.g., "47") |
| **Unread conversations** | Count of conversations with at least one unread (e.g., "12") |
The two modes serve different mental models:
- **"Unread messages"** is the traditional inbox count — useful when each message represents a task to address
- **"Unread conversations"** matches the Slack/Discord style — counts distinct threads regardless of message volume in each. Useful for community managers where one chatty thread shouldn't dominate the badge
## When to use each counter mode
| Site type | Suggested counter mode |
|---|---|
| Support / help desk | **Messages** — each message is potentially a question to answer |
| Community manager dashboard | **Conversations** — focus on which threads need attention, not how chatty each is |
| Marketplace vendor inbox | **Messages** — each buyer message is a potential sale |
| LMS instructor | **Conversations** — each student thread is one "context" to mentally load |
| Personal messaging | **Conversations** — matches the iMessage / WhatsApp pattern |
## How to enable
Navigate to **WP Admin → Better Messages → Settings → Messaging**.
- **Enable Unread Filter** — Show the unread filter button in the conversation list
- **Unread Counter** — Choose between counting unread **messages** or unread **conversations**
## Frequently asked questions
### Does the filter affect search and notifications?
No. Search results show matches across all threads regardless of the filter. Notifications continue to fire for new messages in read or filtered threads — the filter only changes the visual presentation of the list.
### What counts as "read"?
A conversation is read when the user has opened it and the latest message has appeared in their viewport for at least 1 second. The read flag is per-user — your read state doesn't affect other participants.
### Can I have separate counter modes for different users?
No — the counter mode is a site-wide setting. To support per-user preferences, customize the React component via the [JavaScript hooks](/hooks/js-filters/).
### Is the filter available in mini-chat popups?
Mini-chats show a single conversation at a time, not a list, so the filter doesn't apply there. The unread count badge on the mini-chat trigger respects the configured counter mode.
### Does the unread filter respect muted conversations?
Yes. Muted conversations don't contribute to the unread count and are not surfaced by the filter even when they have unread messages.
## See also
- [Conversation muting](/docs/features/conversations-muting/) — silence noisy threads without leaving
- [Search](/docs/features/search/) — find specific messages across all conversations
- [Site notifications](/docs/features/site-notifications/) — how unread state ties into in-app notifications
- [Favorite messages](/docs/features/favorite-messages/) — bookmark messages independent of read state
---
## Block Users in WordPress Chat
# User to User Block
Better Messages gives every chat user a built-in **Block** action that stops another user from sending them messages. The block is one-directional and reversible, with role-based controls for which user roles can block and which roles are immune from being blocked — so site staff and moderators can always reach users for safety reasons.
## What it adds
- One-click **Block** action from any conversation, profile, or message author menu
- One-directional logic — the blocker can still message the blocked user if they choose
- Blocked users cannot start new threads with or send messages to the blocker
- Role-based permission to use the Block action (e.g., paid members can block, anonymous can't)
- Role-based immunity from being blocked (e.g., moderators, support staff, admins)
- Unblock at any time from the user's personal block list
## How it works
When user A blocks user B, the plugin stores a one-directional block record in the database. From that moment:
| Action | Outcome |
|---|---|
| B tries to start a new thread with A | Blocked — UI hides the "Send Message" button on A's profile |
| B sends a message to an existing thread with A | Blocked — message rejected with a user-friendly notice |
| A sends a message to B | Allowed — the block is one-directional |
| B sends a message to a group chat that includes A | **Allowed** — group conversations are not affected |
| A unblocks B | Communication resumes immediately, prior history preserved |
The "Immune Roles" setting overrides the block — a user in an immune role (typically administrators or support staff) can still message a user who blocked them. This prevents the block feature from being used to evade moderation contact.
## When to use
Common deployment patterns:
| Site type | Configuration |
|---|---|
| Dating / fan community | Everyone can block; only admins immune |
| LMS with cohort discussions | Students can block peers but not instructors (instructor role immune) |
| Marketplace (Dokan / WCFM) | Vendors can block buyers; site admin and shop manager immune |
| Public support forum | Anonymous/guest users can't block (low trust); registered users can |
| Telemedicine / coaching | Clients can block other clients; coach + support staff immune |
## How to enable
Navigate to **WP Admin → Better Messages → Settings → Restrictions**.
- **Allow Users to Block** — Enables the Block action throughout the messenger UI
- **Roles That Cannot Block** — User roles whose users do NOT see the Block action (typically guest/anonymous)
- **Immune Roles** — User roles whose users are exempt from being blocked (typically Administrator, Shop Manager, custom moderator roles)
## Frequently asked questions
### Is the block visible to the blocked user?
No — the block is silent. The blocked user sees the same UI but their "Send Message" attempts fail with a generic "Cannot send message" notice rather than naming the blocker. This is intentional to avoid retaliation.
### Does blocking affect group chats?
No. Group conversations and chat rooms are not affected by user-to-user blocks. If user B and user A are in the same group, B's messages still appear to A. To exclude a user from a group, the room admin should remove them directly.
### Can administrators see who has been blocked by whom?
Yes — the block records are stored in the database and can be inspected by an admin via direct SQL or by extending the admin UI. There's no built-in admin "View all blocks" screen in the current version.
### Can a user be blocked by many people?
Yes, there's no cap. Each block is an independent A→B record. A user who is blocked by 100 others simply cannot message any of those 100, but can message everyone else normally.
### What happens if I block someone then we're both in a guest conversation?
Guest conversations follow the same rules as regular conversations — direct messages are blocked, but if both users participate in a multi-party guest chat (chat room), messages are still delivered.
## See also
- [GDPR-compliant messaging](/blog/gdpr-compliant-wordpress-messaging/) — privacy controls including blocking
- [Block users feature post](/blog/block-users-wordpress-chat/) — full feature write-up
- [Role-based access](/blog/role-based-access-wordpress-chat/) — granular role permissions across the messenger
- [Auto-delete messages](/docs/features/auto-delete-messages/) — message lifetime controls for privacy
---
## Verified User Badges in WordPress Chat
# Verified User Badges
Better Messages displays **verified-user badges** next to display names throughout the messenger — in conversation headers, member lists, mini-chat tooltips, and message author labels. The verification status is pulled from your community plugin (BuddyPress, PeepSo, BuddyBoss, Ultimate Member, etc.), so there's no separate database to maintain — verified once in your community plugin, badged everywhere in chat.
## What it adds
- Verified badge icon shown beside the user's display name in every messenger surface
- Automatic sync from the connected community plugin — no manual badge management
- Visible in DMs, group chats, chat rooms, mini-chats, and members directories
- Helps users distinguish official accounts, paid members, or trusted contributors at a glance
- No additional setting in Better Messages — the integration handles the lookup transparently
## How it works
When Better Messages renders a user item (in a conversation header, a message author label, a recipient picker, or a members directory), it calls the connected community plugin's "is user verified" check. If the plugin reports the user as verified, the badge icon is appended next to the display name.
The badge styling matches your community plugin's visual treatment, so verified users look consistent across the site:
| Plugin | Source of verification |
|---|---|
| **BuddyPress** | xProfile "Verified" field, or BuddyPress verified user extensions |
| **PeepSo** | PeepSo Profile Verification add-on |
| **BuddyBoss** | BuddyBoss "Verified Members" feature |
| **Ultimate Member** | UM "Verified Users" extension |
If multiple community plugins are active, Better Messages uses whichever one declares the user verified — verifying in any one source is enough.
## When verification badges matter
| Site type | Why verified badges help |
|---|---|
| Community / social network | Distinguishes original creators from look-alike accounts |
| Marketplace (Dokan / WCFM) | Marks officially-vetted vendor accounts vs new sign-ups |
| LMS | Shows instructors / TAs apart from students at a glance |
| Membership site | Visually rewards paying members with status |
| Fan / paid newsletter community | Signals creator accounts vs subscribers |
## Frequently asked questions
### Can I add a custom verified-badge source from my own plugin?
Yes — hook the `better_messages_is_verified` filter, which receives `(bool $verified, int $user_id)`. Return `true` for any user your plugin considers verified, based on whatever logic you choose (custom user meta, role check, external API, etc.).
### What does the badge icon look like?
The badge is a small checkmark icon rendered next to the user's name. It scales with the surrounding text and respects the messenger's light/dark theme.
### Are verified badges shown to non-logged-in users?
Yes — in chat rooms with guest access, guests see verified badges on participants too. The badge is a visual property of the message author and is rendered for all viewers.
### Does verification gate any messenger feature?
No. Verification is a display-only signal. To gate features by verification, combine the `better_messages_is_verified` check with the `better_messages_can_send_message` filter to allow or reject a send based on the sender's verified status.
### Why doesn't a verified user show the badge?
Check that the community plugin's verification field for that user is set correctly, and that the integration declaring verified status is enabled. The plugin reads the verification flag via the `better_messages_is_verified` filter — make sure that filter is hooked by the integration responsible for verifying users.
## See also
- [Role-based access](/docs/features/role-based-access/) — gate features by WordPress role
- [BuddyPress integration](/docs/integrations/buddypress/) — full BuddyPress integration details
- [PeepSo integration](/docs/integrations/peepso/) — PeepSo integration details
- [BuddyBoss integration](/docs/integrations/buddyboss/) — BuddyBoss integration details
---
## White-Label WordPress Chat Plugin
# White Label by Default
Better Messages is **white-label out of the box** — your end users see a messaging experience that looks like part of your site, with **no "Better Messages" branding, no "Powered by" link, and no attribution anywhere in the user-facing UI**. Combined with color customization and full string translation, you can make the messenger feel entirely custom-built for your platform.
## What it adds
- No "Better Messages" or "Powered by" attribution shown to end users
- Full color customization via the WordPress Customizer
- Every UI string is translatable / overridable to match your brand voice
- No outbound branding links from the chat interface
- Seamlessly inherits your active theme's design tokens (fonts, border radius, color scheme)
- Optional **white-label mobile app build** — ship your own iOS/Android app with your branding (WebSocket version + dedicated service)
## What's visible to end users
| UI element | What it says |
|---|---|
| Plugin labels | Your brand's terminology (configurable via translation strings) |
| Notification emails | Your site name and brand colors |
| Popup notifications | Your message preview, no plugin name |
| Mobile app (default web) | Branded as your site name |
| Mobile app (custom build) | Fully your brand — own app icon, name, splash screen |
| Admin UI (WP Admin) | Contains "Better Messages" branding (admin-only, not user-facing) |
The only place "Better Messages" appears is in the **WP Admin settings panel** (since admins need to know what they're configuring). Your end users never see the plugin name.
## How to customize for full brand match
### 1. Colors
**WP Admin → Appearance → Customize → Better Messages** — set the accent color used across buttons, links, badges, highlights.
### 2. UI strings
Translate or override any visible text using:
- [Loco Translate](https://www.wordplus.org/loco-translate) plugin — visual translation editor
- [WPML](https://wpml.org/) for multilingual sites
- A custom `.po` file in your child theme
Every visible label, button text, placeholder, and error message is translatable.
### 3. Notification email branding
Default emails use your WordPress site name and the same email layout your site uses for other transactional emails. If BuddyPress or BuddyBoss is installed, Better Messages registers its emails as standard BuddyPress email posts — you can edit subject, body, and styling at **WP Admin → Emails**. Without BuddyPress, a simple HTML template is used; you can also intercept the outgoing mail with the standard WordPress `wp_mail` filter.
### 4. Mobile app branding (advanced)
For sites that want a fully branded iOS / Android app with their own icon, name, and bundle ID, a [white-label mobile app build service](/docs/category/mobile-app/) ships a customized version of the native app on the App Store and Google Play under your brand. WebSocket version required; contact support for scope and pricing.
## How to enable
White label is **already on by default** — no setting to flip. Just install and customize colors/strings as you wish.
## Frequently asked questions
### Is there any "Powered by" link visible to my users?
No. The plugin shows zero attribution in the user-facing interface. The only branding appears in the WP Admin settings panel where admins log in — invisible to end users.
### Can I use my own logo in the messenger?
The messenger doesn't display a logo by default — it lives inside the page layout of your active theme, so the surrounding header/branding is whatever your theme already shows. To add a logo inside the chat surface, target the messenger DOM with custom CSS (for example a `::before` block on the conversation header) under **Appearance → Customize → Additional CSS**.
### What about the mobile app — does it say "Better Messages"?
The default native app on the App Store and Google Play is listed under the generic Better Messages name. Push notifications and the in-app messenger still show **your site's name** (taken from your WordPress site title), but the store listing and app icon are the generic ones. The white-label mobile-app build service ships your own listing, icon, and bundle ID — see the mobile app docs.
### Are notification emails branded?
Yes — emails use your WordPress site name, accent color, and site URL. The footer doesn't link back to Better Messages.
### Can I rebrand the admin panel too?
The admin panel keeps the "Better Messages" name (so site owners know which plugin they're configuring). To deep-customize the admin, fork a child plugin — not a supported scenario for most use cases.
## See also
- [Easy customization](/docs/features/easy-customization/) — colors, layouts, custom CSS
- [Mobile app](/docs/category/mobile-app/) — including the white-label app build service
- [White label blog post](/blog/white-label-wordpress-chat-plugin/) — feature deep-dive
- [Translations](/docs/features/translations/) — modify every UI string
---
## Better Messages Developer API — REST, Hooks, Filters
# WordPress-Native Developer API
Better Messages is built on **standard WordPress conventions** — every meaningful event in the messaging workflow is exposed as a PHP action, every data point is filterable, and every server interaction has a REST endpoint. Theme authors, plugin developers, and site builders can extend or override behavior without forking the plugin.
## What it adds
- REST API — full programmatic access to threads, messages, users, and settings ([REST reference](/rest-api/))
- PHP actions — hook into events like message sent, conversation created, participant added ([PHP actions reference](/hooks/php-actions/))
- PHP filters — modify data like message text, user permissions, displayed names ([PHP filters reference](/hooks/php-filters/))
- JavaScript hooks — extend the frontend with `wp.hooks`-style actions and filters
- Custom CSS hooks — every UI surface has stable class names for styling
- Standard WordPress coding patterns — no proprietary frameworks, no compiled-only formats
## Hook prefix
Hooks were originally prefixed `bp_better_messages_*` (legacy from BuddyPress origins). The current prefix is `better_messages_*`. Both prefixes are still honored for backwards compatibility — existing customizations don't break on upgrade.
```php
// Modern form (preferred — most new code uses this)
add_action('better_messages_message_sent', 'my_message_listener');
// Legacy form (still works — many established hooks live under this prefix)
add_filter('bp_better_messages_after_format_message', 'my_custom_renderer', 10, 4);
```
## What you can build with the API
| Customization | Hooks involved |
|---|---|
| Restrict who can send a message | `better_messages_can_send_message` filter (return `false` to block) |
| Add a custom message renderer (e.g. Markdown extensions) | `bp_better_messages_after_format_message` filter |
| Trigger an integration on every new message | `better_messages_message_sent` action |
| Auto-archive old threads | WP-Cron + REST API `DELETE /threads/{id}` |
| Display a custom badge next to user names | `bp_better_messages_display_name` filter |
| Override the verified-badge source | `better_messages_is_verified` filter |
| Notify external system on conversation creation | `bp_better_messages_new_thread_created` action |
| Customize the AI-bot mention placeholder behaviour | `better_messages_ai_providers_info` filter |
## REST API at a glance
The REST API lives at `/wp-json/better-messages/v1/`. Authenticated requests use the standard WordPress REST authentication (cookie + nonce for logged-in users, application passwords for external apps).
Key endpoints:
- `GET /threads` — list conversations for the current user
- `POST /threads` — create a new conversation
- `GET /threads/{id}/messages` — fetch a thread's messages
- `POST /threads/{id}/messages` — send a message
- `GET /users` — search users for the recipient picker
Full reference with request/response shapes is at [/rest-api/](/rest-api/).
## Frequently asked questions
### Is the REST API rate-limited?
WordPress's REST API doesn't rate-limit by default. Better Messages adds soft limits on a few endpoints (recipient picker, search) to prevent abuse. Rate limits are filterable — see the developer reference.
### How do I authenticate REST calls from a separate frontend app?
Use WordPress's [application passwords](https://wordpress.org/documentation/article/application-passwords/) feature. Each user can generate a per-app password and you authenticate via Basic Auth on the REST endpoint.
### Can I create messages on behalf of a user without their session?
Yes — server-side PHP code (running as the bot or as an admin) can call `Better_Messages()->functions->new_message()` directly, bypassing REST authentication.
### Do hooks fire for AI bot messages?
Yes. AI bot messages flow through the same hook pipeline as user messages — your custom action handlers will be invoked.
### Where can I see the full hooks reference?
See the [Hooks & functions reference](/hooks/php-functions/) in the sidebar, organized by PHP actions, PHP filters, PHP functions, JS actions, JS filters, and JS functions.
## See also
- [REST API reference](/rest-api/) — full endpoint documentation
- [PHP functions reference](/hooks/php-functions/) — internal functions you can call
- [PHP actions reference](/hooks/php-actions/) — events you can hook into
- [PHP filters reference](/hooks/php-filters/) — data you can modify
- [WordPress chat REST API blog post](/blog/wordpress-chat-rest-api-developers/) — practical examples
---
## What is Better Messages? Real-Time Messaging Plugin for WordPress
# What is Better Messages?
**Better Messages** is a real-time private messaging and chat room plugin for WordPress. It powers private one-to-one conversations, group chats, public and private chat rooms, voice messages, voice and video calls, AI chat bots, end-to-end encrypted threads, and native iOS / Android mobile apps — all on top of the standard WordPress stack you already run.
Whether you are building a social network, online community, marketplace, membership site, LMS, directory, or any other site where users need to talk to each other, Better Messages provides the messaging layer.
## What it powers
A short list of the major capabilities:
- **Private one-to-one conversations** and **group chats** with shared history
- **Chat rooms** — persistent public or members-only rooms with role-based or guest access
- **File sharing** with EXIF / metadata stripping, resumable TUS uploads, and proxy-protected URLs
- **Voice messages** (separate add-on, works on both versions)
- **Voice and video calls** — one-on-one and group, inside any thread (WebSocket version)
- **AI chat bots** powered by OpenAI, Anthropic Claude, and Google Gemini (WebSocket version + AI add-on)
- **Better Messages Cloud AI** — content moderation, message translation, voice transcription (WebSocket version)
- **End-to-end encryption** — opt-in per thread (WebSocket version)
- **Web push** and **mobile app push notifications**
- **34+ native integrations** with the major community, marketplace, LMS, directory, and creator-platform plugins
- **REST API** and **PHP / JavaScript hooks** for developer customization
- **Fully translatable** via standard WordPress tools (30+ community translations ship with the plugin)
- **White-label** by default — no plugin branding shown to end users
## Two versions
Better Messages comes in two flavors that share the same plugin codebase. The mode is determined by which license you activate — no reinstall, no separate plugin.
### Free (AJAX) version
The free version, available on [WordPress.org](https://wordpress.org/plugins/bp-better-messages/), uses **AJAX polling** for real-time messaging. The browser asks the server every few seconds for new messages — no separate server infrastructure required. Runs on any WordPress hosting, including shared hosts.
### WebSocket version
The WebSocket version is a paid license that switches real-time delivery from AJAX polling to **instant WebSocket push** on a hosted cloud relay. The relay is **included with the license** — no separate server to deploy, no third-party realtime service to configure or bill against, and no extra load on your WordPress hosting (the WebSocket connection talks to the cloud relay, not to your origin). Beyond instant delivery, the WebSocket version unlocks one-on-one and group voice / video calls, AI Chat Bots, Better Messages Cloud AI (content moderation, message translation, voice transcription), end-to-end encryption, web push notifications, mini-chat popups from profiles and members directories, mobile-app real-time delivery, and the white-label mobile app rebuild service.
Pricing for the WebSocket version starts at **$14.99 / month**, or **$11.99 / month** billed annually ($143.88 / year). Single-site license, paid via Freemius. See the [full pricing page](/docs/pricing/) for plan-by-plan details and a feature comparison.
### Self-hosted plan
For sites with strict data-sovereignty requirements (GDPR Article 9 regulated data, HIPAA-adjacent workloads, jurisdictional rules about which servers may transit data), consider upgrading to the **self-hosted plan**. The WebSocket layer runs on infrastructure you control instead of the Better Messages cloud relay. Pricing is **$25 / month** billed annually ($299.99 / year) and includes a one-time installation service. See the [pricing page](/docs/pricing/#self-hosted) for full details.
For most sites the default cloud WebSocket version is GDPR-compatible by itself — the relay is blind to message content (no storage, no inspection), and all message data lives only in your WordPress database. See [Privacy & GDPR](/docs/features/privacy-gdpr/) for the full data-flow picture.
## Get started
1. **[Install Better Messages from WordPress.org](https://wordpress.org/plugins/bp-better-messages/)** — it works immediately on any WordPress site.
2. Open **WP Admin → Better Messages → Settings → General** and set your **Messages Location** (the WordPress page where the messenger lives) or use a community-plugin profile tab if you run BuddyPress / BuddyBoss / Ultimate Member / PeepSo.
3. (Optional) Pick the integration for your community / marketplace / LMS / directory plugin under **Better Messages → Settings → Integrations**.
4. (Optional) Activate the WebSocket version under **Better Messages → Account** for instant delivery, calls, AI features, and the rest of the paid feature set.
## Where to go next
- [Installation guide](/docs/getting-started/installation/)
- [Conversation types](/docs/getting-started/conversation-types/) — DMs, group chats, chat rooms
- [User inbox](/docs/getting-started/user-inbox/)
- [Integrations catalogue](/docs/category/integrations/) — all 34+ supported plugins
- [Features catalogue](/docs/category/features/) — every messenger feature in detail
- [REST API reference](/rest-api/) — for developers
- [Hooks & functions reference](/hooks/php-functions/) — for theme / plugin authors extending Better Messages
- [Blog](/blog) — 80+ posts on features, integrations, and use cases
## Who builds Better Messages
I'm **Andrij Tkachenko**, an **indie developer from Ukraine**. Better Messages is my full-time work — and has been since the first version shipped on WordPress.org on **January 5, 2017**. Nine years and counting, one developer, one continuous line of development.
Working independently is what makes the plugin move fast on what matters most. A feature ships when it is ready. A bug fix lands the same day it is reported. A security patch goes out the same hour. Roadmap priorities adjust to what real WordPress sites actually need — not to what fits a quarterly chart somewhere else.
Security and reliability are personal commitments. I investigate every reported vulnerability, write the disclosure, and ship the fix. I monitor the WebSocket cloud and debug incidents on the live infrastructure when something goes wrong. After nine years of running this plugin in the wild, I have a hands-on understanding of what makes a WordPress messenger dependable, and I take that seriously.
Most of Better Messages' functionality is **free on WordPress.org**, and stays that way. If you need WebSocket features — instant delivery, voice / video calls, AI features, end-to-end encryption — upgrading to the WebSocket version is also a great way to support continued development of the plugin, which I greatly appreciate.
If you have any questions or need help, reach out at **support@better-messages.com**.
---
## Conversation Types in Better Messages — DMs, Groups, Chat Rooms
# Conversation Types
Better Messages supports several conversation types, each suited to a different community pattern. All types share the same messaging surface — file sharing, reactions, replies, mentions, calls, AI bots — but differ in how participants are added and how persistent the thread is.
## Private (one-to-one) conversations
The default type. Two users start a thread from the new-conversation screen, exchange messages with full history, and the conversation is private to those two participants. The most common pattern for member-to-member messaging on community sites and marketplaces.
## Group conversations
Multi-participant DMs — three or more users in a single private thread, started from the new-conversation screen by picking multiple recipients. Moderators (creator + admins) can invite or remove participants over time. See [Group conversations](/docs/features/group-conversations/) for the full feature reference.
## Chat rooms
Persistent rooms with admin-set membership rules. Administrators create chat rooms from **WP Admin → Better Messages → Chat Rooms**, then embed them anywhere with the generated shortcode. Each room defines its own role-based access (allowed roles, guest access, optional join restrictions). Rooms can be configured to appear in user inboxes or to be embed-only.
See [Chat rooms](/docs/features/chat-rooms/) for details.
## Synced group chats
A special integration mode that mirrors user groups from third-party plugins into Better Messages threads. The Better Messages addon listens for join / leave events on the host plugin and keeps the thread participants in sync automatically.
Currently supported group sources:
- [BuddyPress Groups](https://buddypress.org/) — see [BuddyPress integration](/docs/integrations/buddypress/)
- [BuddyBoss Groups](https://www.buddyboss.com/) — see [BuddyBoss integration](/docs/integrations/buddyboss/)
- [PeepSo Groups](https://www.peepso.com/) — see [PeepSo integration](/docs/integrations/peepso/)
- [Ultimate Member Groups](https://ultimatemember.com/extensions/groups/) — see [Ultimate Member integration](/docs/integrations/ultimate-member/)
- [FluentCommunity Spaces](https://fluentcommunity.co/) — see [FluentCommunity integration](/docs/integrations/fluentcommunity/)
## Mass messaging
Not strictly a conversation type, but worth knowing about: **mass messaging** lets administrators send a broadcast as individual 1-on-1 DMs to many recipients at once — each recipient gets a private thread with the sender, not a shared group. Useful for site-wide announcements that still feel personal. See [Mass messaging](/docs/features/mass-messaging/).
## See also
- [User inbox](/docs/getting-started/user-inbox/) — where conversations of all types appear
- [Chat rooms](/docs/features/chat-rooms/)
- [Group conversations](/docs/features/group-conversations/)
- [Integrations catalogue](/docs/category/integrations/)
---
## Install Better Messages — WordPress Plugin Setup Guide
# Installation
:::info REQUIREMENTS
To install the plugin ensure that your website running:
- **WordPress 5.9 or newer**
- **PHP 7.4 or newer**
:::
## How to install
Installing Better Messages follows the standard WordPress plugin install flow — no special steps required.
### From WP Admin
1. Open **Plugins → Add New** in WP Admin
2. Search for **Better Messages**
3. Click **Install Now**, then **Activate**
4. Configure under **Better Messages → Settings**
### Manual upload
1. Download the plugin ZIP from the [WordPress.org plugin page](https://wordpress.org/plugins/bp-better-messages/)
2. Upload the ZIP via **Plugins → Add New → Upload Plugin**, or unzip into `/wp-content/plugins/bp-better-messages/`
3. Activate the plugin under **Plugins**
4. Configure under **Better Messages → Settings**
## Integration setup
If you run a community / marketplace / LMS plugin, follow its integration guide for the recommended setup:
* [BuddyPress](/docs/integrations/buddypress/)
* [BuddyBoss](/docs/integrations/buddyboss/)
* [PeepSo](/docs/integrations/peepso/)
* [Ultimate Member](/docs/integrations/ultimate-member/)
* [Full integrations catalogue](/docs/category/integrations/) — all 34+ supported plugins
## Activating the WebSocket version
After install, the free (AJAX) version is active by default. To unlock instant delivery, voice / video calls, AI bots, and the rest of the paid feature set, purchase a license on the [pricing page](/docs/pricing/) and enter it under **Better Messages → Account**.
---
## Messages Location & User Inbox — Better Messages WordPress Setup
# Messages Location
Every user has a personal inbox where every conversation they are part of is listed — DMs, group conversations, chat rooms, and synced group chats all show up here. The user can open any thread and reply directly from this page.
/`) are cohorts of students sharing access to one or more courses, managed by users with the **Group Leader** role. Better Messages mirrors that organisation by creating a dedicated chat for each LearnDash Group.
/`. With this toggle on, Better Messages adds a **Send Message** button to that profile, positioned right under the instructor's name.
/`) by default, or from the standard WordPress author archive.
| Attribute | Default | Notes |
|---|---|---|
| `user_id` | profile owner | Override the message recipient |
| `class` | LearnDash button classes | Override CSS classes |
| `text` | `Send Message` | Override the button label |
```text
[better_messages_learndash_instructor_button]
[better_messages_learndash_instructor_button user_id="42"]
```
## Frequently asked questions
### Will students from different courses end up in the same chat?
No — each LearnDash course has its own Course Group Chat. Students enrolled in multiple courses see one thread per course, surfaced together in the Courses widget.
### What happens when a student's enrollment is revoked?
LearnDash fires `learndash_update_course_access` on revoke; Better Messages removes the student from the Course Group Chat immediately. Previous messages stay readable in the thread history.
### Does it work with LearnDash Groups (cohort feature)?
Yes — each LearnDash Group gets its own paired chat, separate from the per-course chat. Group Leaders are auto-joined as instructors of the chat.
### Does the Send Message button require the LearnDash Instructor Role add-on?
Yes — the **Send Message Button on Instructor Profile** option is only available when the paid LearnDash Instructor Role add-on is active. Other LearnDash integrations (Message Instructor button, Course Group Chat) work without it.
### Will the AI Chat Bot work in a LearnDash course chat?
Yes — add an AI bot as a participant in the course chat. The bot answers when mentioned with `@botname`. Useful for handling FAQ-style student questions automatically.
## See also
- [LearnDash student messaging plugin](/blog/learndash-student-messaging/) — full feature write-up with screenshots
- [WordPress LMS chat plugin](/blog/wordpress-lms-chat-plugin/) — comparing LearnDash, LearnPress, Tutor LMS, MasterStudy LMS, FluentCommunity Courses
- [LearnPress integration](/docs/integrations/learnpress/) — for LearnPress sites
- [Tutor LMS integration](/docs/integrations/tutor-lms/) — for Tutor LMS sites
- [MasterStudy LMS integration](/docs/integrations/masterstudy-lms/) — for MasterStudy sites
- [Group conversations](/docs/features/group-conversations/) — underlying group chat feature
- [Mini widgets](/docs/features/mini-widgets/) — Courses widget configuration
- [AI Chat Bots](/docs/features/ai-chat-bots/) — adding bots to course threads
---
## Better Messages for LearnPress: Student & Instructor Messaging
The **LearnPress integration** for Better Messages adds a Message Instructor button on every course page, an auto-managed Course Group Chat tied to enrollment, a Send Message button on the LearnPress instructor profile, a Messages tab inside the LearnPress profile, and a Courses widget on the Mini Widgets bar. Works on both the free and WebSocket versions of Better Messages.
:::info REQUIREMENTS
To install the plugin ensure that your website running:
- **WordPress 5.9 or newer**
- **PHP 7.4 or newer**
:::
## Installation
### How to install LearnPress
**[Download LearnPress](https://www.wordplus.org/learnpress)** from the WordPress plugin directory and install it through the standard WordPress installation process.
### How to install Better Messages with LearnPress
1. Install Better Messages through the WordPress plugins screen, or upload the plugin files to `/wp-content/plugins/bp-better-messages`.
2. Activate the plugin through the **Plugins** screen.
3. Go to **Better Messages → Settings → Integrations → LMS** to enable the integrations you want.
/`) so visitors can reach the instructor directly from their profile.
/messages/`). The tab embeds the full Better Messages inbox so students can read and reply to conversations without leaving their profile.
/?page=better-messages`. The dashboard tab is force-enabled and locked while this option is selected — change the Messages Location away from Motors to unlock it again.
/`, alongside **MY LISTINGS / MY FAVORITES / PROFILE SETTINGS**. The tab loads the full Better Messages inbox inline so dealers can read and reply without leaving their dashboard.
/?view=instructor`) so visitors can reach the instructor directly from their profile.
/?view=student`) so other learners can reach the student from their public profile page.
"Audio Call"
user_id
The recipient — user who will receive the call
Post author of current WordPress post/page
url_only
Set to 1 to return only the URL (no button HTML)
0
class
Additional CSS classes for styling
None
## Examples
### Basic — call the post author
```
[better_messages_audio_call_button]
```
Renders a default button. Clicking starts an audio call with the current post's author.
### Custom label and explicit recipient
```
[better_messages_audio_call_button text="Call Support" user_id="42"]
```
Custom-labeled button that connects to user ID 42 (e.g., your support rep) regardless of post context.
### URL only for custom styling
```html
Call Now
```
Returns just the URL — wrap in your own anchor with custom styling.
### Themed class
```
[better_messages_audio_call_button text="Audio Call" class="btn-primary btn-lg"]
```
Adds extra CSS classes for design integration with your theme's button styles.
## Frequently asked questions
### Does the button work for guests?
Guests see the button but clicking redirects to login (or to guest-chat flow if enabled). Active calls require a session.
### What happens if the recipient is offline?
The recipient sees a missed-call system message in the conversation when they next open the thread. No queued ringing for offline users.
### Will this work on the free version?
No — voice calls require the WebSocket version. The shortcode renders, but clicking shows an upgrade notice.
### Can I gate which roles see the button?
Use a wrapping conditional in your theme, OR use **Settings → Calls** per-role restrictions to gate who can place calls globally.
## See also
- [Video call button shortcode](/docs/shortcodes/better_messages_video_call_button/) — same pattern for video
- [Mini chat button shortcode](/docs/shortcodes/better_messages_mini_chat_button/) — open mini chat
- [Audio calls feature](/docs/websocket/audio-calls/) — full documentation
- [Group audio chat](/docs/websocket/group-audio-chat/) — multi-party voice (up to 50)
---
## better_messages_live_chat_button Shortcode
# better_messages_live_chat_button
:::info
**[How to add shortcodes?](https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/)**
:::
**Universal Live Chat Button.** Drop it into any post, page, custom post type, page builder, or theme template — the shortcode resolves who the chat targets, what label it shows, and which thread to open *automatically*, based on the current page.
The same shortcode works for: post-author chat, marketplace vendor chat (user stored in postmeta), site-wide support inbox, AI bot launcher. No PHP required — configure it visually in the [Shortcode Builder](#shortcode-builder) or hand-write the attributes with magic tokens like `post_author` and `{author_name}`.
This shortcode supersedes [`better_messages_pm_button`](/docs/shortcodes/better_messages_pm_button/) and [`better_messages_mini_chat_button`](/docs/shortcodes/better_messages_mini_chat_button/).
... ` string | Inline SVG icon shown before the label. Sanitized at render time — scripts, event handlers, and `javascript:` URLs are stripped. |
| `type` | `link` (default) or `button` | Which HTML element to render. |
| `target` | e.g. `_blank` | HTML target attribute on the rendered link. |
| `alt` | any string | HTML `title` attribute on the rendered element. |
:::info
The `bm-lc-button-styled` class is enabled by default in the Shortcode Builder. The raw `[better_messages_live_chat_button]` shortcode (no class) renders an unstyled element — useful for sites that style the button themselves via CSS.
:::
## Placeholders
Tokens wrapped in curly braces are interpolated against the current post:
| Placeholder | Resolves to |
|---|---|
| `{post_id}` | Numeric ID of the current post. |
| `{post_title}` | Post title. |
| `{post_type}` | Post type slug. |
| `{author_id}` | Numeric ID of the post author. |
| `{author_name}` | Display name of the post author. |
Available in `text`, `subject`, and the custom-pattern form of `unique_tag`. When the shortcode runs outside of a post context (archives, sidebars, 404 pages), placeholders collapse to safe defaults — for example `text="auto"` falls back to `Live Chat` instead of producing `Chat with `.
## Thread information banner
When `object_id` is set, the chosen post becomes a banner inside the conversation — both participants see the post's title, thumbnail, and link at the top of the thread. The banner persists on every transport (REST, AJAX polling, WebSocket relays) and is written once when the thread is created (no overwrites).
Use it with `object_id="auto"` so the current post automatically becomes the context. Particularly useful for marketplace / directory / job board patterns where chats should clearly reference what they're about.
The banner is rendered with a built-in template by default. Sites that ship dedicated BM integrations (WooCommerce, WP Job Manager, Houzez) provide their own banner content via the `better_messages_rest_thread_item` filter and continue to win over the generic builder. For your own custom banner HTML, hook `better_messages_thread_info_banner_html`.
## Examples
### Post-author chat on every blog post
```
[better_messages_live_chat_button user_id="post_author" unique_tag="auto" object_id="auto" text="auto" class="bm-lc-button-styled"]
```
Drop this once into your single-post template (or use a content-injection plugin). Each post automatically gets a button that chats with its author, opens a per-post thread, and shows the post as a banner.
### Marketplace vendor button (user id stored in postmeta)
```
[better_messages_live_chat_button user_id="postmeta:_vendor_user_id" unique_tag="auto" object_id="auto" text="Chat with vendor" class="bm-lc-button-styled"]
```
Reads the vendor's WP user id from the `_vendor_user_id` postmeta key on the current listing. Works with any vendor / agent / owner postmeta field — change the key to match what your plugin or theme uses.
### Site-wide support inbox
```
[better_messages_live_chat_button user_id="1" unique_tag="support" text="Contact Support" class="bm-lc-button-styled"]
```
All visitors land in the same thread with admin user id 1. Add it to the site footer or a contact page.
### Pill-shaped orange button with custom inline styles
```
[better_messages_live_chat_button user_id="post_author" unique_tag="auto" object_id="auto" text="auto" class="bm-lc-button-styled" bg_color="#ff6b35" text_color="#ffffff" font_size="18px" padding="14px 24px" border_radius="999px"]
```
Inline style attributes override the `bm-lc-button-styled` defaults — no custom CSS required.
### Button with an inline SVG icon
```
[better_messages_live_chat_button user_id="post_author" unique_tag="auto" object_id="auto" text="auto" class="bm-lc-button-styled" icon='unique_tag to product_123 to create or open additional unique conversation between 2 members based on the tag.
None
class
Sets additional class to button html element.
Useful for additional CSS styling.
None
```
[better_messages_mini_chat_button text="Private Message" subject="New conversation subject" class="extra-class"]
```
## Frequently asked questions
### Why is this marked legacy?
The newer `[better_messages_live_chat_button]` shortcode handles all the same use cases plus: guest authorization flow, automatic decision between mini-chat and full-page based on settings, and AI bot targeting via negative user IDs. Use it for new implementations.
### Will this shortcode keep working?
Yes — backwards-compatible. Existing pages using `[better_messages_mini_chat_button]` continue to work indefinitely. No need to migrate immediately.
### What's `unique_tag` for?
Creates a separate conversation per tag, even between the same two users. E.g., `unique_tag="product_123"` opens (or creates) a thread specific to "product 123". Useful for marketplace product Q&A where buyer-vendor have a per-product context.
### Does this work for guests?
No — the legacy shortcode doesn't handle guest auth flow. Use [`better_messages_live_chat_button`](/docs/shortcodes/better_messages_live_chat_button/) for guest-compatible usage.
### Does it respect the Mini Chats setting?
Yes — the button only opens a mini chat if Mini Chats is enabled in plugin settings. Otherwise, the button does nothing.
## See also
- [better_messages_live_chat_button](/docs/shortcodes/better_messages_live_chat_button/) — recommended replacement
- [better_messages_pm_button](/docs/shortcodes/better_messages_pm_button/) — other legacy alternative
- [Mini chats feature](/docs/websocket/mini-chats/) — popup chat windows (WebSocket version)
- [Mini widgets](/docs/features/mini-widgets/) — broader widget overview
---
## better_messages_my_messages_url Shortcode
# better_messages_my_messages_url
:::info
**[How to add shortcodes?](https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/)**
:::
A **URL-only shortcode** that returns the path to the logged-in user's inbox. Doesn't render any UI — just the URL string. Designed for use cases where you need the inbox URL as a link target (menu items, buttons, custom dashboard widgets) without embedding the full messenger.
## When to use it
| Scenario | Pattern |
|---|---|
| WordPress menu link to Messages | Use this shortcode with the [Shortcode in Menus](https://www.wordplus.org/shortcode-in-menus) plugin |
| Custom dashboard "View Inbox" button | Wrap the URL in your own anchor tag |
| Account-page link list | Add as one item in a user's account-actions list |
| Author bio "Message me" link | URL-only with custom button styling |
## Usage
```
[better_messages_my_messages_url]
```
Returns the URL of the page where the messenger lives — typically `/messages/` or wherever **WP Admin → Better Messages → Settings → General → Messages Location** points.
## In a menu (via Shortcode in Menus)
1. Install [Shortcode in Menus](https://www.wordplus.org/shortcode-in-menus)
2. **Appearance → Menus** → Add a Custom Link
3. URL: `[better_messages_my_messages_url]`
4. Label: "Messages"
When rendered, the URL placeholder is replaced with the actual inbox URL.
## In a custom anchor
```html
View My Messages
```
The shortcode renders to the bare URL — wrap it in any element you want.
## Frequently asked questions
### What URL does this return for non-logged-in users?
An empty string. The shortcode only resolves a URL for authenticated users (logged-in WordPress users or authenticated guests). Wrap the shortcode with a login link in your template if you need to redirect anonymous visitors somewhere meaningful.
### Does this return a relative or absolute URL?
Absolute URL — full `https://yoursite.com/messages/` form. Useful for emails and external links.
### Can I include this in an email template?
Yes — though emails typically use a different anchor (each thread has its own deep-link URL). For "view all my messages" links in transactional emails, this is useful.
## See also
- [better_messages](/docs/shortcodes/better_messages/) — embed the full inbox UI
- [better_messages_unread_counter](/docs/shortcodes/better_messages_unread_counter/) — unread count for menus
- [Easy customization](/docs/features/easy-customization/) — configure where the inbox lives
---
## better_messages_pm_button Shortcode
# better_messages_pm_button
:::info
**[How to add shortcodes?](https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/)**
:::
:::info Legacy shortcode
Prefer [`better_messages_live_chat_button`](/docs/shortcodes/better_messages_live_chat_button/) for new implementations — it auto-decides between mini chat and full page based on plugin settings, and reliably handles guest visitors.
:::
**Private message button shortcode**
Shows private message button
Attribute
Whats it for
Default
text
Sets button text label
"Private Message"
user_id
Set User ID with whom conversation will be started
Post author of WordPress Post/Page
subject
Prefill subject at the new conversation screen
None
message
Prefill message at the new conversation screen
None
target
Set _self to open in same page
Set _blank to open in new browser tab
_self
fast_start
Set 0 to force the new-conversation screen (with subject / message prefills).
Default behaviour follows the global Fast Start setting under Better Messages → Settings → Messaging — when that setting is on, the button jumps straight into the existing thread and the subject / message attributes are ignored.
1 (follow global setting)
url_only
Set 1 to not render button, but display just URL
0
class
Sets additional class to button html element.
Useful for additional CSS styling.
None
[better_messages_pm_button text="Private Message" subject="Have a question to you" message="Lorem Ipsum is simply dummy text." target="_self" class="extra-class" fast_start="0" url_only="0"]
## Frequently asked questions
### Why is this marked legacy?
The newer `[better_messages_live_chat_button]` shortcode handles guest authorization, auto-decides between mini-chat and full-page, and supports AI bot targeting. Use it for new implementations.
### Will this shortcode keep working?
Yes — backwards-compatible. Existing pages using `[better_messages_pm_button]` continue to work indefinitely.
### What's `fast_start`?
With `fast_start="1"`, clicking the button opens the conversation screen directly, skipping the new-conversation form. The `subject` and `message` prefills are ignored in fast-start mode.
### Why might I still use this over the new shortcode?
`pm_button` has a `message` prefill attribute (the new shortcode doesn't, since it's geared toward universal use). If you specifically need to prefill the first message, this remains useful.
### Does this work for guests?
No — the legacy shortcode doesn't include the guest authorization flow. Use [`better_messages_live_chat_button`](/docs/shortcodes/better_messages_live_chat_button/) for guest-compatible usage.
## See also
- [better_messages_live_chat_button](/docs/shortcodes/better_messages_live_chat_button/) — recommended replacement
- [better_messages_mini_chat_button](/docs/shortcodes/better_messages_mini_chat_button/) — other legacy alternative
- [better_messages_user_conversation](/docs/shortcodes/better_messages_user_conversation/) — embed the conversation inline instead of as a button
---
## better_messages_single_conversation Shortcode
# better_messages_single_conversation
:::info
**[How to add shortcodes?](https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/)**
:::
:::info Compatibility
<>This { (props.type ? props.type : 'guide') } compatible with Better Messages {props.version} or higher
:::
Embed **one specific conversation thread** on any WordPress page using its thread ID. Unlike the main `[better_messages]` shortcode (which shows the user's full inbox), this shortcode locks the page to a single thread — useful for support ticket pages, announcement threads, or any context where you want users to interact with a specific conversation only.
## When to use it
| Use case | Why a single conversation shortcode |
|---|---|
| Support ticket page | Each ticket is one thread; embed that thread inline |
| Announcement thread | A specific "site announcements" thread shown on the homepage |
| Event-day Q&A thread | A pinned thread visible during a live event |
| Customer-vendor order page | The conversation tied to a specific order |
| Documentation page Q&A | A specific thread for question/answer about that doc |
## Attributes
| Attribute | What it does | Default |
|---|---|---|
| **`thread_id`** | The Better Messages thread ID to display | No default — required |
## Usage
```
[better_messages_single_conversation thread_id="55"]
```
Replace `55` with the actual thread ID. To find a thread's ID, view the conversation in WP Admin → Better Messages → Messages Viewer (when enabled) or via the REST API.
## Examples
### Site-wide announcement thread
```
[better_messages_single_conversation thread_id="1"]
```
Embed on the homepage to show every visitor the latest site-wide announcements thread.
### Per-order conversation (dynamic)
```php
// In a template file:
$thread_id = get_post_meta($order_id, '_bm_thread_id', true);
echo do_shortcode('[better_messages_single_conversation thread_id="' . $thread_id . '"]');
```
Embed the conversation tied to a specific WooCommerce order on the order detail page.
### Documentation Q&A thread
```
[better_messages_single_conversation thread_id="42"]
```
Drop into a documentation page to enable inline Q&A on that doc.
## Frequently asked questions
### Can users without access to the thread see it?
No — standard access rules apply. If the current user isn't a participant in the thread (and the thread isn't a public chat room they have access to), they see a permission error.
### Can I show a thread to guests?
Only if the thread is in a chat room with guest access enabled. Standard DMs require login.
### What happens if the thread is deleted?
The shortcode renders an empty state — "This conversation is no longer available." To handle gracefully, conditionally include the shortcode based on thread existence.
### Can I show multiple threads on the same page?
Yes — multiple `[better_messages_single_conversation]` shortcodes can appear on one page. Each renders independently.
### Does this work with the WebSocket version's real-time features?
Yes — embedded threads get real-time updates, typing indicators, presence, and all other WebSocket-version features.
## See also
- [better_messages](/docs/shortcodes/better_messages/) — full inbox layout
- [better_messages_user_conversation](/docs/shortcodes/better_messages_user_conversation/) — auto-create with a specific user
- [better_messages_live_chat_button](/docs/shortcodes/better_messages_live_chat_button/) — start a new conversation
- [Group conversations](/docs/features/group-conversations/) — multi-user threads
---
## better_messages_unread_counter Shortcode
# better_messages_unread_counter
:::info
**[How to add shortcodes?](https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/)**
:::
Display the **unread messages counter badge** anywhere on your WordPress site — header, menu item, custom dashboard widget, or sidebar. Updates in real-time (instantly on the WebSocket version, on poll on the free version). The badge respects the global unread counter mode (per-message vs per-conversation).
## When to use it
| Location | Why a counter badge |
|---|---|
| **Site header / menu** | Most common — let users see "Messages (3)" at a glance |
| Member dashboard | Compact summary of pending communications |
| Mobile floating button | Pair with the [floating chat button](/docs/features/enhanced-mobile/) for an icon + count |
| User profile dropdown | Personal-area "you have N unread messages" indicator |
| Sticky sidebar | Persistent visibility on long content pages |
## Attributes
| Attribute | What it does | Default |
|---|---|---|
| **`hide_when_no_messages`** | If `1`, the counter is hidden when there are zero unread messages | `0` (always show) |
| **`preserve_space`** | If `1` AND counter is hidden, the space is reserved invisibly — smoother animation when a new message arrives | `0` |
## Usage
### Always-visible counter
```
[better_messages_unread_counter]
```
Renders the counter regardless of unread state. Shows "0" when nothing is unread.
### Hide when zero
```
[better_messages_unread_counter hide_when_no_messages="1"]
```
Counter only appears when there are unread messages — cleaner UX for most sites.
### Hide with reserved space
```
[better_messages_unread_counter hide_when_no_messages="1" preserve_space="1"]
```
Best for menus: counter is invisible when zero but reserves the space, so new-message animations don't push other menu items around.
## Putting it in a menu
The recommended pattern for adding the counter to your WordPress menu:
1. Install the [Shortcode in Menus](https://www.wordplus.org/shortcode-in-menus) plugin
2. **Appearance → Menus** → Add a Custom Link
3. URL: `[better_messages_my_messages_url]` (links to the inbox)
4. Label: `Messages [better_messages_unread_counter hide_when_no_messages="1" preserve_space="1"]`
The result: a "Messages" menu item with a counter badge that appears when there are unread messages.
## Frequently asked questions
### Does the counter update in real-time?
On the WebSocket version, yes — instantly as new messages arrive. On the free version, the counter updates every few seconds (matching the polling interval).
### What does the counter count — messages or conversations?
Whichever you've configured in **Settings → Messaging → Unread Counter**. See [Unread filter](/docs/features/unread-filter/) for the counter mode options.
### Can I style the badge?
Yes — the counter renders with stable class names (`.better-messages-unread-counter`). Override via your theme's Additional CSS.
### Does the counter appear for non-logged-in users?
No — guests don't have a personal inbox, so the counter renders empty. For guest sites with guest chat, the counter reflects unread messages in their guest sessions.
### How can I hook into the counter value (for custom UI)?
Listen for the `bp-better-messages-update-unread` `CustomEvent` on `document`. The new count is in `event.detail.unread`:
```js
document.addEventListener('bp-better-messages-update-unread', (e) => {
console.log('Unread count:', e.detail.unread);
});
```
## See also
- [better_messages_my_messages_url](/docs/shortcodes/better_messages_my_messages_url/) — pair this with the counter for menu items
- [Unread filter](/docs/features/unread-filter/) — counter mode settings
- [Site notifications](/docs/features/site-notifications/) — related on-site notification surface
- [Enhanced mobile](/docs/features/enhanced-mobile/) — floating chat button (also has built-in counter)
---
## better_messages_user_conversation Shortcode
# better_messages_user_conversation
:::info
**[How to add shortcodes?](https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/)**
:::
:::info Compatibility
<>This { (props.type ? props.type : 'guide') } compatible with Better Messages {props.version} or higher
:::
Embed a **direct conversation between the current visitor and a specified user**. If they've never messaged before, the thread is created automatically. If a thread already exists, that thread is displayed. Perfect for author bio pages, vendor profiles, coach landing pages, and any context where a user should land directly in conversation with a specific person.
## When to use it
| Use case | Pattern |
|---|---|
| Author bio "Message me" page | Auto-pull author from post context, embed DM thread |
| Marketplace vendor storefront | "Message vendor" page with their dedicated thread |
| Coaching / consulting landing page | Client lands directly in conversation with the coach |
| Telemedicine practitioner profile | Patient gets direct chat with their assigned practitioner |
| Support staff individual page | Direct DM with a specific support rep |
## Attributes
| Attribute | What it does | Default |
|---|---|---|
| **`user_id`** | The user to start/show a conversation with | Author of the current WordPress post or page |
## Usage
```
[better_messages_user_conversation user_id="55"]
```
If `user_id` is omitted, the post/page author is used:
```
[better_messages_user_conversation]
```
## Examples
### Coaching page
```
[better_messages_user_conversation user_id="12"]
```
Embed on a coach's landing page (user ID 12 = the coach). Visitors land directly in a private conversation with the coach.
### Marketplace vendor profile
```php
// In a vendor profile template:
$vendor_id = get_vendor_id_from_context();
echo do_shortcode('[better_messages_user_conversation user_id="' . $vendor_id . '"]');
```
Each vendor profile gets a per-vendor DM thread auto-created for new visitors.
### Author bio (auto-detect)
```
[better_messages_user_conversation]
```
When placed on a post or page, no `user_id` needed — the post author becomes the recipient. Great for author bio boxes that consistently behave across all posts.
## Frequently asked questions
### What happens if the visitor isn't logged in?
The shortcode shows a login form first. After login, the user is taken directly to the conversation with the specified user.
### Does this create a new thread every time?
No — if a thread already exists between the two users, that thread is reused. New thread only when no prior conversation exists.
### Can guests use this shortcode?
Only with [guest chat enabled](/docs/features/guest-access/). Guests get a transient identity for the conversation.
### What if the specified user_id doesn't exist?
The shortcode shows a "user not found" notice. Always validate the user_id in dynamic shortcode usage.
### Is there a way to prepopulate a message?
Not in the default UI. To pre-post a message into the thread programmatically, call `Better_Messages()->functions->new_message( [ 'sender_id' => …, 'recipients' => …, 'content' => … ] )` before rendering, or use a JS filter on the input.
## See also
- [better_messages](/docs/shortcodes/better_messages/) — full inbox layout
- [better_messages_single_conversation](/docs/shortcodes/better_messages_single_conversation/) — embed a specific existing thread
- [better_messages_live_chat_button](/docs/shortcodes/better_messages_live_chat_button/) — button that starts a chat (lighter alternative)
- [better_messages_pm_button](/docs/shortcodes/better_messages_pm_button/) — legacy "private message" button
- [Group conversations](/docs/features/group-conversations/) — multi-user threads
---
## better_messages_video_call_button Shortcode
# better_messages_video_call_button
:::info
**[How to add shortcodes?](https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/)**
:::
:::info WebSocket Version Guide
<>This functionality available only with WebSocket Version
:::
Embed a **video call button** anywhere on your WordPress site that starts a one-on-one video call with a specified user. The shortcode works inside posts, pages, custom-built profile templates, page builders (Elementor / Bricks / Beaver), and any theme location that accepts shortcodes.
## When to use it
| Scenario | Where you'd place the shortcode |
|---|---|
| Coaching / consulting profile pages | On the coach's listing page so prospects can start a call directly |
| Marketplace vendor profiles | On the vendor's storefront for buyer-to-seller live demo calls |
| Telemedicine / appointment booking | On the practitioner's profile after a booking is confirmed |
| Custom member directory cards | In the per-member card template to expose a "Call" CTA |
| Author bio boxes | Below blog posts for direct-to-author calls |
## Attributes
Attribute
What it controls
Default
text
Button label text shown to the visitor
"Video Call"
user_id
The recipient — the user who will receive the call
Author of the current WordPress post or page
url_only
Set to 1 to return only the call URL (no button HTML). Useful for custom button styling.
0
target
HTML target attribute on the rendered anchor (e.g. _blank to open in a new tab)
None
class
Additional CSS class names on the button element for styling overrides
None
## Examples
### Basic — call the post author
```
[better_messages_video_call_button]
```
Renders a button with the default "Private Message" label. Clicking it starts a video call with the author of the current post or page. Best for blog author bio boxes and CPT detail pages.
### Custom label and explicit recipient
```
[better_messages_video_call_button text="Start Video Call" user_id="42"]
```
The button label reads "Start Video Call" and connects to the user with ID 42 regardless of the current post author. Useful when the button lives outside a post context (sidebar, custom page).
### URL only — for custom-styled button
```
Talk to support live
```
Returns just the URL string. Wrap it in your own anchor element and apply any custom styling. The URL handles all the call-launching logic — clicking it opens the live video call in the Better Messages widget.
### Themed class for design integration
```
[better_messages_video_call_button text="Video Call" class="btn-primary btn-lg"]
```
Adds extra CSS classes to the rendered button — pair with Bootstrap / Tailwind / your theme's own button styles for consistent design.
## Frequently asked questions
### Does the button work for users who aren't logged in?
Guests can see the button, but clicking it will redirect them to log in (or to your guest-chat flow, if guest access is enabled for video calls). The actual call requires both parties to have a session.
### What happens if the recipient is offline?
The recipient sees a missed-call system message in the conversation when they next open the thread. Better Messages doesn't queue ringing for offline users.
### Will this work with the free version?
No — video calls require the WebSocket version. The shortcode will still render the button, but clicking it shows a notice that the feature requires upgrading.
### Can I make the button appear only for specific user roles?
The shortcode doesn't have role gating built in. Use a wrapping conditional in your theme or a shortcode-permission plugin if you need that. Alternatively, use the per-role call restrictions in **Settings → Calls** to control who can place calls at the global level.
## See also
- [Audio call button shortcode](/docs/shortcodes/better_messages_audio_call_button/) — same pattern for voice-only calls
- [Mini chat button shortcode](/docs/shortcodes/better_messages_mini_chat_button/) — open the mini chat widget
- [Video calls feature](/docs/websocket/video-calls/) — full feature documentation
- [WordPress video call plugin](/blog/wordpress-video-call-plugin/) — feature overview blog post
---
## One-on-One HD Audio Calls in WordPress Chat
# HD Audio Calls
The WebSocket version enables **HD 1-on-1 audio calls** directly from any conversation. Built on WebRTC for peer-to-peer audio streaming when possible (with TURN relay fallback for restrictive networks), audio quality is high and latency is low — comparable to dedicated voice apps like Zoom or Discord.
:::info WebSocket version
Audio calls are a WebSocket-version feature. For multi-party voice, see [group audio chat](/docs/websocket/group-audio-chat/) (up to 50 participants).
:::
## What it adds
- 1-on-1 HD audio calls between any two participants
- WebRTC peer-to-peer streaming — the audio doesn't transit Better Messages servers
- Low latency, Opus codec for high quality at modest bandwidth (~30 kbps each direction)
- Initiate from any conversation with one click
- Works in all modern browsers (Chrome, Firefox, Edge, Safari, mobile equivalents)
- Built-in call UI with mute, hang up, and timer
## How it works
When a user clicks the **Call** button:
1. Signaling: the WebSocket relay carries SDP and ICE candidates between the two browsers
2. Peer-to-peer connection: the two browsers establish a direct WebRTC connection
3. Audio streaming: voice flows P2P between the participants
4. Fallback: if direct P2P fails (corporate firewall, symmetric NAT), a TURN relay forwards the encrypted audio
| Network scenario | What happens |
|---|---|
| Normal home/office network | Direct peer-to-peer — minimal latency |
| One participant behind strict firewall | TURN relay forwards encrypted audio |
| Both behind corporate proxies | TURN relay (slight added latency) |
All audio is **DTLS-SRTP encrypted** end-to-end — even when relayed through TURN, the audio bytes are encrypted between the participants.
## When 1-on-1 audio calls fit
| Use case | Pattern |
|---|---|
| Coaching session | Coach-client 1-on-1 call inside the existing chat thread |
| Customer support escalation | Voice call when chat alone is taking too long |
| Marketplace negotiation | Quick voice call to close a higher-value deal |
| Telemedicine consultation | Practitioner-patient 1-on-1 |
| Dating community | Audio call as a step before video |
## Requirements
- Website must use **HTTPS** (WebRTC requires secure context for microphone)
- Each participant needs a working microphone
- Modern browser with WebRTC support
- WebSocket-version license
## Frequently asked questions
### Are calls recorded?
No — calls are real-time and not recorded by Better Messages. To record, participants can use their own screen-recording or call-recording tools (with consent). The plugin doesn't include built-in recording.
### Can I configure per-role call permissions?
Yes — restrict who can place calls via **WP Admin → Better Messages → Settings → Calls**. Useful for paid-tier-only calls.
### What if the recipient is offline?
The caller sees a "user offline" notice. Better Messages doesn't queue ringing for offline users.
### Does audio quality degrade with poor networks?
WebRTC adapts to bandwidth — under poor conditions, the bitrate drops automatically. Even on cellular, conversations remain intelligible. For truly bad connections, the call may drop and need to be re-initiated.
### How do group audio calls differ?
[Group audio chat](/docs/websocket/group-audio-chat/) supports up to 50 participants and routes through a media server (SFU) rather than peer-to-peer. Different scaling model, similar end-user experience.
## See also
- [Video calls](/docs/websocket/video-calls/) — 1-on-1 video calls
- [Group audio chat](/docs/websocket/group-audio-chat/) — multi-party voice (up to 50)
- [Group video chat](/docs/websocket/group-video-chat/) — multi-party video
- [Screen sharing](/docs/websocket/screen-sharing/) — during any call
- [Voice messages](/docs/addons/voice-messages/) — async voice (different from live calls)
---
## Encrypt Browser Chat Cache (AES-256)
# Local Browser Encryption
Better Messages caches recent message data in the **browser's IndexedDB** for fast loading and offline access. The WebSocket version can encrypt that cache with **AES-256** so it's protected against access by other users sharing the device — important for kiosks, shared computers, or public access scenarios.
:::info WebSocket version
This is a WebSocket-version feature. The free version caches less data and doesn't expose this encryption setting.
:::
## What it adds
- AES-256 encryption of the local IndexedDB cache on each user's device
- Protects offline message storage from unauthorized device-sharing access
- Transparent to the user — no extra setup, no password prompts
- The encryption key is tied to the user's session — only the authenticated user can decrypt
- Important for kiosks, public-access PCs, family-shared computers, or office desktops with multiple users
## How it works
When local browser encryption is enabled:
1. On login, your server provides the user's browser with a per-session encryption key
2. Before writing to IndexedDB, the browser encrypts the data with AES-256
3. Reads from IndexedDB decrypt on-the-fly
4. On logout (or session expiration), the key is wiped — the cache becomes unreadable
| User action | What's protected |
|---|---|
| Logged in, browsing chat | Cache is encrypted in IndexedDB; transparent to the user |
| Logged out | Cache is now unreadable — keys are gone |
| Another user logs in on the same browser | They get their own key — can't read the previous user's cache |
| Power user inspects IndexedDB via DevTools | Sees encrypted ciphertext, not plaintext messages |
| Sophisticated attacker with full device access | Can extract encrypted blob but must defeat AES-256 to read content |
## When to enable
| Environment | Recommendation |
|---|---|
| Public library / internet cafe terminals | Enable — multiple anonymous users share the device |
| Kiosk-style installations | Enable — strong privacy default |
| Office computers with multiple shifts | Enable — privacy between shift workers |
| Healthcare environment | Enable + use [E2EE](/docs/websocket/e2e-encryption/) |
| Personal-device-only audience | Optional — adds CPU overhead for limited threat |
## How to enable
Enable **Browser Database Encryption** in **WP Admin → Better Messages → Settings → Messaging → Encryption**.
The setting takes effect on the user's next page load. Existing un-encrypted cache entries are migrated to encrypted on read.
## Frequently asked questions
### Does this slow down the chat?
The encryption / decryption happens transparently in WebAssembly or native CryptoAPI — overhead is small (sub-millisecond per operation). No perceptible difference.
### Can I export my cache as plaintext?
No — the cache is intentionally inaccessible outside the authenticated user's session. To export your messages, use [WordPress's Personal Data Export](/docs/features/privacy-gdpr/) — that pulls from the server, not the cache.
### What if I want even stronger protection?
Combine with [end-to-end encryption (E2EE)](/docs/websocket/e2e-encryption/) — that encrypts content end-to-end so even your WordPress server can't read it. Combine both for the strongest privacy stack.
### What happens if the user clears their browser data?
The encrypted cache is deleted. The user will need to re-load message history from the server on next visit. Their data on your server is unaffected.
### Does this protect against malware on the user's device?
Partially. Malware that runs in the same browser context as the chat could read the decrypted data while the user is logged in. AES-256 cache encryption protects against threats that access the disk directly (e.g., another user logging into the same OS account).
## See also
- [Private (AES-256 transit)](/docs/websocket/private/) — content encryption in transit
- [End-to-end encryption](/docs/websocket/e2e-encryption/) — true E2EE per-thread
- [Secure (WSS / TLS)](/docs/websocket/secure/) — connection-layer security
- [Your data is yours](/docs/websocket/your-data/) — data location overview
---
## How to Cancel a Better Messages WebSocket Subscription
# Can I cancel my subscription after subscribing?
Yes, you can cancel your WebSocket subscription at any time.
Your license stays valid for the period you've already paid for — instant message delivery, voice / video calls, web push, the native mobile apps, and the rest of the WebSocket-only features continue to work until that period ends. After it expires, the plugin reverts to AJAX (free) behavior. Your messages, threads, history, files, integration data, and AI chat bots stay intact.
No further charges are applied unless you resubscribe.
## How to cancel
1. Log in to your Freemius account at [https://users.freemius.com/](https://users.freemius.com/)
2. Go to **Licenses**
3. Find your Better Messages WebSocket subscription and click **Cancel subscription**
You can also reactivate any time from the same dashboard.
## See also
- [Refund policy](/docs/websocket/refund-policy/) — 7-day money-back guarantee terms
- [Reset license](/docs/websocket/reset-license/) — moving a license to a new domain
- [Pricing](/docs/pricing/) — current plans and billing options
---
## Cloud AI: Moderation, Translation, Voice Transcription
# Better Messages Cloud AI
Better Messages Cloud AI provides AI-powered features included with the WebSocket license at no additional cost. No third-party API keys or external accounts required.
## Features
### AI Content Moderation
Automatically review messages for harmful or unwanted content using AI.
- 23 content categories including extended categories (spam, scam, contact sharing, commercial promotion, and more)
- Custom moderation rules in plain text
- Conversation context awareness — detect patterns split across multiple messages
- Text and image moderation
- Two action modes: flag for review or hold until approved
For full details see [AI Content Moderation](/docs/features/ai-content-moderation/).
### AI Message Translation
Automatically translate incoming messages to each user's preferred language.
- Currently available for 1-to-1 conversations only
- 53 supported languages with automatic source language detection
- HTML formatting preserved in translations
- Users select their preferred language in the messaging settings panel
- Translation toggle to switch between translated and original text
For full details see [AI Message Translation](/docs/features/ai-message-translation/).
### Voice Message Transcription
Automatically transcribe voice messages to text using AI speech recognition.
- Supports 99+ languages with automatic language detection
- Transcription results cached and displayed alongside voice messages
- Users can view the transcription by clicking the transcribe button on any voice message
#### How it works
1. A user sends a voice message in a conversation
2. Any participant clicks the transcribe button on the voice message
3. The audio is sent to Better Messages Cloud for transcription
4. The transcribed text appears below the voice message for all participants
Transcription results are cached — once a voice message is transcribed, the text is stored and displayed instantly for all future views.
#### Language
By default, the language is automatically detected from the audio. If all users on your site speak the same language, you can set a specific language code (e.g. `en`, `ru`, `es`) in the settings for better accuracy and faster processing.
## How to enable
### Moderation
Navigate to **WP Admin** → **Better Messages** → **Settings** → **Moderation**.
1. Select **Better Messages Moderation AI** as the provider
2. Enable **AI Moderation**
3. Choose the **Flagged Message Action**
4. Select **Content Categories** to detect
### Translation
Navigate to **WP Admin** → **Better Messages** → **Settings** → **Translation**.
1. Enable **Message Translation**
2. Optionally restrict available languages in the **Available Languages** section
3. Users select their preferred language in the messaging settings panel inside the chat interface
### Transcription
Navigate to **WP Admin** → **Better Messages** → **Settings** → **Voice Messages**.
1. Select **Better Messages Transcription AI** as the provider
2. Enable **Transcription**
3. Optionally set a **Language** code or leave empty for auto-detection
:::note Requirements
- WebSocket license
- PHP 8.1 or higher
- [Voice Messages](/docs/addons/voice-messages/) add-on (for transcription)
:::
## Callback URL
Better Messages Cloud AI uses a callback URL to deliver results to your site. Some features (such as message translation) rely on this callback as the primary delivery method, so it must be reachable from the internet.
If your server is behind a firewall, WAF, or a security plugin (e.g. Wordfence, Sucuri, Cloudflare Access) that blocks incoming requests from external servers, Cloud AI features may be slow or fail entirely.
### Testing the callback
Each settings page that uses Cloud AI includes a **Test Callback URL** button. Click it to verify that the Better Messages Cloud server can reach your site's callback endpoint. If the test fails, you will see the exact URL that needs to be whitelisted.
### Whitelisting
If the test fails, whitelist the following REST API endpoint in your firewall or security plugin:
```
https://yoursite.com/wp-json/better-messages/v1/ai/task-result
```
Replace `yoursite.com` with your actual domain. This is a POST endpoint that receives task results from the Better Messages Cloud server.
## Reliability
Results are returned immediately when possible. If the response takes longer than expected, the cloud server delivers the result asynchronously via callback. In cases where the callback cannot reach your site (e.g. due to firewall restrictions), a background cron job retries periodically until the result is delivered. Processed results are cached on the cloud server for 30 minutes, making retries instant.
## Data Privacy
Voice message audio and message content are sent to Better Messages Cloud for processing over HTTPS. All processing runs on private Better Messages servers — no data is shared with third parties. No user data is stored — content is processed in real time and immediately discarded.
---
## End-to-End Encryption (E2EE) for WordPress Chat
# End-to-End Encryption
Better Messages supports end-to-end encryption (E2EE) for private conversations, ensuring that only the participants can read the messages. The server never has access to message content — all encryption and decryption happens directly in the users' browsers.
## Requirements
- **WebSocket version** — E2E encryption is only available with the WebSocket real-time mechanism (not available in AJAX mode)
- **HTTPS/SSL** — the site must have SSL enabled, since the Web Crypto API requires a secure context
- **Modern browser** — any browser with Web Crypto API support (all modern browsers including Chrome, Firefox, Safari, Edge)
## How it works
When end-to-end encryption is enabled, each user generates a personal encryption key pair. When a conversation is created, a unique conversation key is generated and securely shared with each participant. Messages are encrypted before leaving the sender's browser and can only be decrypted by the intended recipients.
The server stores only encrypted data — it relays messages between participants but cannot read their content. Even site administrators cannot access the plaintext of encrypted messages.
## Key capabilities
- Messages encrypted in the browser before transmission — server never sees plaintext
- AES-256-GCM encryption for message content and file attachments
- ECDH P-256 key exchange for secure key distribution between participants
- Password-protected key backup for multi-device access
- Key recovery if the user forgets their encryption password
- Automatic key distribution for new conversation participants
- Key rotation when participants are removed from a conversation
- Crypto operations offloaded to Web Workers for better performance
- Mobile app support (iOS and Android)
## Setting up encryption
### First-time setup
When a user first joins an encrypted conversation, they are prompted to create an encryption password. This password is used to protect their private key so it can be recovered on other devices or browsers.
1. User opens an encrypted conversation
2. A setup dialog appears asking them to create an encryption password
3. The system generates a personal key pair and securely backs up the private key (encrypted with the password) on the server
4. The user can now send and receive encrypted messages
### Multi-device access
When accessing encrypted conversations from a new device or browser:
1. The user is prompted to enter their encryption password
2. The encrypted private key backup is downloaded from the server
3. The private key is decrypted locally using the password
4. The user can now read and send encrypted messages on the new device
This works the same way on the mobile app — enter the encryption password to restore keys and access encrypted conversations.
### Password recovery
If a user forgets their encryption password:
1. Click "Forgot password?" in the key restore dialog
2. Confirm the intent to reset — this generates new encryption keys
3. Enter a new encryption password
4. Other participants will automatically re-wrap the conversation key for the user's new identity key when they come online
5. Once re-wrapped, the user regains access to the conversation and can read previous messages
## How encryption works
### Identity keys
Each user has a personal ECDH P-256 key pair:
- **Public key** — shared with other users so they can establish secure key exchanges
- **Private key** — never leaves the user's device in unencrypted form; backed up on the server encrypted with the user's password (PBKDF2 with 600,000 iterations)
### Conversation keys
Each encrypted conversation has its own AES-256 symmetric key:
- A random 256-bit key is generated when the conversation is created
- This key is wrapped (encrypted) individually for each participant using ECDH shared secrets
- Each participant unwraps the conversation key using their own private key
- The conversation key is used to encrypt and decrypt all messages in that conversation
### File attachments
File attachments in encrypted conversations are also encrypted:
- A unique encryption key is generated for each file
- The file is encrypted with AES-256-GCM before upload
- The file key is wrapped with the conversation key (not directly with participant keys)
- Each participant unwraps the file key using the conversation key, then decrypts the file
- Decrypted files are cached locally in the browser for performance
- File metadata (size, type) is visible to the server, but file content is encrypted
### Performance
- All cryptographic operations (encryption, decryption, key wrapping) are offloaded to a SharedWorker or Web Worker so they don't block the UI
- Conversation keys are cached in memory after first unwrap for fast encrypt/decrypt
## Group conversations
End-to-end encryption works with group conversations:
- All participants share the same conversation key
- When a new participant is added, they are marked as "pending" until they receive the wrapped conversation key
- Pending users see a notice that they need to set up encryption — they cannot send or read messages until setup is complete
- Other participants can continue messaging normally while some users are pending
- Key distribution happens automatically when both the pending user and a participant who holds the key are online
- When a participant is removed, their wrapped key is deleted and they lose access to future messages
## Restrictions
- Messages in encrypted conversations **cannot be forwarded** to other conversations
- Encrypted conversations **bypass the moderation queue** — the server cannot read ciphertext, so content moderation is not possible for E2E messages
- The server **rejects unencrypted messages** sent to encrypted conversations — all messages must be valid E2E ciphertext
- AI chat bots are always excluded from encrypted conversations
- When creating a new conversation with an AI bot as recipient, the E2E encryption toggle is automatically disabled
## Security properties
### What is encrypted end-to-end
- Message text content
- File attachment content
### What is NOT encrypted end-to-end
- Message metadata (sender, timestamp, read status)
- Conversation participant list
- User presence and typing indicators
- Conversation settings
- File metadata (size, type)
### Server limitations
- The server relays encrypted messages but cannot decrypt them
- The server stores encrypted private key backups but cannot access them without the user's password
- Site administrators can see conversation metadata but not message content
## Admin experience
- The moderation queue shows **"Encrypted message"** as a placeholder for E2E message content
- Admins can see conversation metadata (participants, timestamps, message count) but not the actual content
- File attachment metadata (count and size) is visible in the admin panel, but file content is encrypted
## Mobile app support
End-to-end encryption is fully supported on the iOS and Android mobile apps:
- Uses native cryptographic operations
- Keys are backed up and recoverable across devices using the same password-based recovery as the web version
- The same encryption password works on both web and mobile
## How to enable
All encryption settings are located in **WP Admin → Better Messages → Settings → Messaging → Encryption**.
- **Enable End-to-End Encryption** — main toggle to activate the E2E encryption feature. Requires HTTPS to be enabled on your site.
The following options become available once E2E encryption is enabled:
- **Enabled by default** — the encryption toggle will be pre-checked when users create new conversations. Users can still uncheck it to create unencrypted conversations.
- **Force for all conversations** — all new private conversations will be end-to-end encrypted. Users cannot disable encryption. This option requires "Enabled by default" to be checked.
- **Allow guest users** — allow guest chat users to participate in end-to-end encrypted conversations. AI chat bots are always excluded regardless of this setting.
---
## Better Messages End User License Agreement (EULA) — Freemius
# End User License Agreement
Effective as of Nov 29, 2017
To help you understand the [EULA (End User License Agreement)](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/#eula), we’ve prepared a bullet-point list that summarizes some of the main ideas (yes, including rights, obligations, liabilities, and all that legalese!) covered in there. IMPORTANT: The following bullet-point list is for convenience purposes only, in order to help you navigate (and hopefully, better understand) the [EULA](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/#eula). This bullet-point list is _not_ a substitute for, or even a part of, the [EULA](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/#eula), whose terms and conditions constitute a legally binding contract. It is your responsibility to fully read those terms and conditions.
General
-------
* The agreement is published at [https://freemius.com/plugin/1557/bp-better-messages/legal/eula/](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/)
* You, the customer (or the customer on whose behalf a service provider, such as an agency, is), must be of a legal age in your jurisdiction to form a binding contract, but in any event at least thirteen (13) years old to access or use the [Freemius service](https://freemius.com/).
* Freemius, Inc. is an [authorized reseller of “BP Better Messages”](https://freemius.com/terms/vendor/) and is the 'merchant of record' for your purchase.
* The agreement is between you and Freemius, Inc. on behalf of the Vendor behind “BP Better Messages” (the “_Vendor_”). You may not assign or transfer it without Freemius’ express prior written consent.
* The agreement contains various clauses to limit and exclude Freemius’ and Vendor’s liability, and it also contains indemnity protection for Freemius and the Vendor.
Support
-------
* While the EULA is between You and Freemius, Inc., all support and maintenance services for the product (such as providing bug fixes, updates, upgrades, troubleshooting, etc.), if any, are the sole responsibility of the Vendor.
* You can contact the Vendor’s support via [support@better-messages.com](mailto:support@better-messages.com). So if you're having trouble or have any questions, please contact [support@better-messages.com](mailto:support@better-messages.com) for assistance.
* Freemius, Inc. resells and distributes “BP Better Messages” and other plugins and themes "as is" and with no implied or statutory warranties, or guarantees that they will function exactly as you would like, or that they will be compatible with all third-party components and plugins.
* Support for this product is only available for those who have an active, paid license.
* Product updates are granted for as long as the your license remains active.
* Whilst the Vendor attempts to provide the best support possible, there's no guarantee that any particular support query can, or will, be answered to the extent, or within a timeframe, that the inquirer is completely satisfied.
Security & Software Updates
---------------------------
* Product security and feature updates are included for free as long as your license is active. Updates will be delivered automatically from the WordPress admin dashboard or you can manually download the latest version of the product from your dashboard: [https://users.freemius.com/login/](https://users.freemius.com/login/).
Subscriptions & Automatic Renewals
----------------------------------
* The product’s license is sold as automatically recurring subscriptions that renew each month or year (depends on the subscription's billing cycle) on the anniversary of the purchase date.
* All subscriptions automatically renew at the end of the monthly/annual license term unless You cancel the subscription prior to the automatic renewal date.
* We cannot grant refunds on renewal payments.
* For annual subscriptions, we will attempt to send you a renewal reminder email 30 days prior to your renewal date, and you may use this opportunity to cancel your subscription before the renewal payment is automatically processed. Such a reminder would only be a courtesy, and depends on your email client, potentially can end up at your spam box, so do not rely on that email - you alone are responsible for taking any action before a renewal takes effect. Just add yourself a calendar reminder :)
* If a subscription renewal fails, the system will attempt to process the payment 3 more times according to our [dunning mechanism schedule](https://freemius.com/help/documentation/selling-with-freemius/dunning-failed-payments/). After the 4th failed attempt, the subscription will be canceled.
* If you subscribe to the monthly or annual plans, and your license expires due to a failed renewal, subscription or license cancellation, the paid features & functionality of the product will be disabled.
* You can always access your account and cancel the subscription via [https://users.freemius.com/login/](https://users.freemius.com/login/)
Price Changes
-------------
* Prices of “BP Better Messages” are subject to change without prior notice or consent.
* As long as your subscription remains active and you don’t switch to another plan or license-level, your subscription renewals amount will not be affected by any price changes.
Free Trials
-----------
* If you subscribe for a trial with a payment method and cancel the trial before the 1st payment was processed, the paid features & functionality of the product will be disabled.
* If you subscribe for a trial without a payment method and the trial expires, the paid features & functionality of the product will be disabled.
* If you subscribe for a trial with a payment method, Freemius will attempt to send you an email reminder 2 days before the trial expiration, giving you enough time to cancel the trial. Such a reminder would only be a courtesy, and depends on your email client, potentially can end up at your spam box, so do not rely on that email - you alone are responsible for taking any action before a the trial expires. Just add yourself a calendar reminder :)
* If you subscribe for a trial without a payment method, Freemius will attempt to send you an email reminder 2 days before the trial expiration, giving you the option to purchase a plan. Same like with the trial with a payment method, such a reminder would only be a courtesy, and depends on your email client, potentially can end up at your spam box.
Refund Policy
-------------
* If, during the first 7 days following the Purchase date, You experience a defect that makes the Product's material functions unusable, and following Your cooperation with our support team we are unable to resolve it, then following Your request we will issue a full refund of the Purchase price. For clarity, any defect or lack of use arising from a conflict or incompatibility with a third party product, is not covered by this policy, and nor are missing Product features.
* There are a few very limited cases (as specified in the [EULA](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/#eula)) in which Freemius will determine eligibility for refunds. Otherwise, eligibility for refunds are determined and governed exclusively by the Vendor and [Vendor's refund policy (see below)](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/#refund_policy), and so your ability to get a refund therefor depends on Vendor's cooperation. In any case, no refunds are given beyond the scope of the [Vendor's refund policy](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/#refund_policy), and nor are there any refunds available on renewal payments.
END USER LICENSE AGREEMENT
--------------------------
### _Last Updated: July 22, 2021_
This End User License Agreement ("_Agreement_") constitutes a binding contract between you, the customer (or the customer on whose behalf a service provider, such as an agency, is) purchasing the Product (defined below) license ("_You_" and "_Your_") and Freemius, Inc. (“_Freemius_”, “_we_”, “_us_” and “_our_”). By placing Your order via the Checkout (defined below), or by otherwise accessing or using the Product, You acknowledge that You have read, understood, and agree to be bound by the following (the date of such occurrence being the "_Effective Date_"):
1. This Agreement; and
2. Other supplemental terms and policies referenced herein, which are stated to be incorporated into, and made a part of, this Agreement by reference.
If You do not agree with any of the terms and conditions of this Agreement, do not place Your order and do not otherwise access or use the Product. Under this Agreement, You are purchasing a license to the Product ("_Purchase_"). Under Your Purchase, You receive a license (more on your license rights in Section 2 _(License)_ below). Your Purchase can either be a recurring subscription (e.g. 'monthly' or 'annual') license or a one-time 'lifetime' license (in each case, a "_License_", and respectively a "_Subscription License_" and a "_Lifetime License_"). Freemius is a reseller of the License, and is the 'merchant of record' for the purpose of this transaction. But the vendor from whom You are ultimately receiving access to the Product (the "_Vendor_") is otherwise responsible for the provision of the Product and all related services, and You acknowledge that Freemius is not the provider or operator of the Product. Again, more on this below.
1. DEFINITIONS AND INTERPRETATION
------------------------------
This Agreement contains a range of capitalized terms, some of which are defined in this Section, and some of which are defined elsewhere. The Section headings in this Agreement are for convenience of reading only, so do not rely upon them for interpretation. As used in this Agreement “_You_” means either you personally or, if you are entering into this Agreement on behalf of an entity (for example, if you are subscribing using an entity’s email domain), such entity, and in such case you represent that you have the authority to bind such entity to this Agreement. “_Affiliate_” means with respect to Freemius, any person, organization or entity controlling, controlled by, or under common control with, Freemius, where “control” means the possession, directly or indirectly, of the power to direct or cause the direction of the management and policies of such person, organization or entity, whether through the ownership of voting securities or by contract or otherwise. "_Checkout_" means the online checkout form which You submit(ted) for Your Purchase. Your order is subject to our Acceptance (defined below), and once Accepted the order is hereby incorporated into, and made a part of this Agreement, by reference. “_Product_” means the software product or service (such as _WordPress_ plugin or theme, or “Serviceware” plugin, or plugins and/or themes bundle) specified in the Checkout. References herein to "Product" shall also include any of its related documentation, as well as any updates and upgrades provided by the Vendor. “_Site_” means the digital property or service (such as a website, browser extension, mobile app, _etc._) owned or operated by You or Your client for which You are using the Product. In the case of a "WordPress multi-site network", each "network sub-site" shall be deemed a Site for the purposes of your order and this Agreement. "_Trial_" means a limited-in-time use of the Product on a trial basis. "_Trial Period_" means the period of the Trial, as specified in the Checkout.
2. ORDERING, REFUND POLICY AND TRIALS
----------------------------------
Your submitted order is only an offer, and is subject to our acceptance of it ("_Acceptance_"). Acceptance only occurs at such time that we have done both of the following:
1. as applicable (depending on the type of Product), provided You with license key(s); and
2. unless the order is for an Trial, received full payment (as confirmed by us or our payment service provider) of the purchase price of your order through settlement of funds via your provided credit card or other payment method.
We may, without liability, reject Your order, or otherwise cancel Your order at any time and for any lawful reason prior to Acceptance (for example if we are unable to process or fulfill the order), and in such cases we will refund Your payment. Prior to Acceptance, an automatic e-mail acknowledgement of your order may be generated (but such acknowledgement does not constitute Acceptance of your order). FOLLOWING ACCEPTANCE, AN ORDER IS FINAL, NON-CANCELABLE, AND ORDER PAYMENTS ARE NON-REFUNDABLE, EXCEPT AS SPECIFIED IN THE FOLLOWING REFUND POLICY ("_Vendor Refund Policy_"), which is hereby incorporated into, and made a part of, this Agreement by reference: If, during the first 7 days following the Purchase date, You experience a defect that makes the Product's material functions unusable, and following Your cooperation with our support team we are unable to resolve it, then following Your request we will issue a full refund of the Purchase price. For clarity, any defect or lack of use arising from a conflict or incompatibility with a third party product, is not covered by this policy, and nor are missing Product features. Notwithstanding the above, if You are purchasing a bundled offering of more than one Product (a "_Bundled Offering_"), then the Purchase plan terms and refund policy that specifically govern that Bundled Offering as a whole (the "_Bundled Offering Terms_") shall apply instead of the above-mentioned Vendor Refund Policy, as well as to the extent of any other conflict or inconsistency with a provision of this Agreement. If You subscribed for a free Trial, Freemius may (but shall not be obligated to) send You an email two (2) or more days prior to the expiration of the Trial Period, giving You the opportunity to make a Purchase of the Product. If You subscribed for a Trial with a payment method (a "_Paid Trial_"), then:
1. Freemius may (but shall not be obligated to) send You an email reminder of the upcoming payment two (2) or more days prior to the expiration of the Trial Period. You acknowledge that such a reminder would only be a courtesy, and You alone are responsible for taking any action before a payment takes effect.
2. _In the case of 'monthly' or 'annual' Paid Trials:_ if (per the instructions in the reminder email) You fail to cancel the Trial prior to its expiration, the Trial shall convert to a paid Subscription License, and You will be charged the Fees (defined below) for the initial Purchase Term.
3. _In the case of a 'lifetime' Paid Trial:_ You are deemed to have purchased a Lifetime License, and, subject to the Vendor Refund Policy, You will not be charged the Fees until the expiration of the Trial Period.For the purposes of determining Refund eligibility under a Trial, the period stated in the applicable Vendor Refund Policy shall be deemed to begin on the first day of the Trial Period.
3. LICENSE AND RESTRICTIONS
------------------------
Subject to the terms and conditions of this Agreement, Freemius grants You the following License under Your Purchase. If a third party service provider (such as an agency) is entering into this Agreement on Your behalf for the purpose of operating the Product on Your behalf, the License (and any related services, such as support and maintenance) also extends to such service provider. The License is:
1. limited, non-exclusive, non-assignable, and non-sublicensable;
2. for the term of the Purchase plan (e.g. monthly, annual, lifetime, _etc._) specified in the Checkout, plus for whatever period thereafter the Product (in whole or in part) is still made available to You (the "_Purchase Term_");
3. to access, use, and as applicable install or receive, the Product solely on or in connection with Your Site(s) (subject to the authorized number of Sites); and
4. subject to whatever volume, location, feature, and other limitations or conditions (if any) are specified in the Checkout.
We recommend installing and testing the Product in a staging (or similar non-production) environment prior to installing it in the Site's production environment, and making necessary configurations, which should hopefully allow You to identify any code conflicts between the Product and other products or code of the Site, and therefore avoid disruption to Your Site. As a condition to the License, and unless You obtain the prior express written permission of the Vendor, You shall not do (or permit or encourage to be done) any of the following, in whole or in part: (a) copy, “frame” or “mirror” the Product, on any other server or wireless or Internet-based device; (b) sell, assign, transfer, lease, rent, sublicense, distribute, publicly perform, display or communicate, offer as part of a time-sharing, outsourcing or service bureau environment, or otherwise make available, the Product to any third party, or bundle or incorporate the Product into or with any other product or service; (c) modify, alter, adapt, arrange, or translate the Product; (d) decompile, disassemble, decrypt, reverse engineer, extract, or otherwise attempt to discover the source code or non-literal aspects (such as the underlying structure, sequence, organization, file formats, non-public APIs, ideas, or algorithms) of, the Product; (e) remove, alter, or conceal any copyright, trademark, or other proprietary rights notices displayed on or in the Product; (f) circumvent, disable or otherwise interfere with security-related or technical features or protocols of the Product; (g) make a derivative work of the Product, or use the Product to develop any service or product that is the same as (or substantially similar to) the Product; (h) store or transmit any robot, malware, Trojan horse, spyware, or similar malicious item intended (or that has the potential) to damage or disrupt the Product; (i) use the Product to infringe, misappropriate, or violate any third party's Intellectual Property Rights, or any applicable law (such as anti-spamming laws), or to otherwise engage in any fraudulent activity; (j) employ any hardware, software, device, or technique to pool connections or reduce the number of Sites, devices or users that directly access or use the Product (sometimes referred to as 'virtualisation', 'multiplexing' or 'pooling') in order to circumvent any restrictions on scope of the License; or (k) take any action that imposes or may impose (as determined in Freemius' reasonable discretion) an unreasonable or disproportionately large load on the servers, network, bandwidth, or other cloud infrastructure which operate or support the Product, or otherwise systematically abuse or disrupt the integrity of such servers, network, bandwidth, or infrastructure. The Product may include third party software components, as well as proprietary components (such as [Freemius' SDK](https://github.com/freemius/wordpress-sdk) component that is applied to the Product), that are subject to open source licenses and/or notices (“_Third Party Software_” and “_Third Party Software Terms_”, respectively). This Agreement is not intended, and shall not be construed, to derogate from any rights You may have under such Third Party Software Terms. Accordingly, to the extent that the Product (or any part thereof) is subject to any Third Party Software Terms or to any other licensing terms, and they conflict with the scope of the License granted to You or with any provision of this Agreement, such Third Party Software Terms or other licensing terms (as the case may be) shall prevail. Any undertakings, representations, warranties, guarantees, conditions, or other commitments made by Freemius in this Agreement concerning the Product (if any), are made by Freemius and not by any authors, licensors, or suppliers of, or contributors to, such Third Party Software. _As an example only: if the Product is subject to the GNU General Public License (GPL), then You may use the Product in accordance with the GPL, and may ignore any provision of this Agreement (such as a conflicting License restriction above or a conflicting ownership provision) which conflicts with the GPL._
4. PAYMENT AND PRICING
-------------------
1. Fees. If or once You have purchased a paid License (including, for example, if You failed to cancel a Paid Trial before its expiry), You agree to pay all fees stated in the Checkout ("_Fees_"), and in accordance with its payment terms. Following receipt of Your order, You authorize Freemius (either directly and/or through third parties) to request and collect payment (or otherwise charge, refund or take any other billing actions) from our payment provider or Your designated banking account, and to charge Your payment method, as well make any inquiries Freemius deems necessary to validate Your designated payment account or financial information, in order to ensure prompt payment (including for the purpose of receiving updated payment details from Your payment, credit card or banking account provider – such as, updated expiry date as may be provided to us by Your credit card company). In connection with Purchase renewals (if applicable), Freemius will attempt to automatically charge You the applicable renewal Fees. In the event of failure to collect the Fees owed by You, we may (but shall not be obligated to) retry to collect at a later time, and/or suspend or terminate Your Purchase, without further notice. Where the Fees are invoiced, each invoice shall be due and payable in full by the due date specified on the invoice.Freemius shall not be responsible or liable (such as for bank fees) in the event any charge causes a negative balance in Your bank or payment account.
2. Refunds. _Except where there has been a duplicate charge to Your payment method (in which case Freemius may, but is not obligated to, determine Refund eligibility:_ You acknowledge and agree that any refunds, cancellations, and returns (collectively, "_Refunds_") for the Product are subject to the [Vendor Refund Policy](https://freemius.com/plugin/1557/bp-better-messages/legal/eula/#refund_policy) only, and that, even though Freemius may assist or otherwise be involved in administering Refunds eligibility for Refunds is determined solely by Vendor (and not Freemius), and accordingly any Refund requests must be made directly to the Vendor. Failure by Vendor to respond to a Refund request or inquiry (for example, if Vendor ceases to do business) shall not give rise to or impose any obligation or liability on Freemius.
3. Price Changes; Renewal Discounts. _In respect of Subscription Licenses only:_ Provided that Your recurring subscription is active, has not changed, and has not been terminated or cancelled: (a) any changes (increases or decreases) to the Product pricing during the Purchase Term shall not affect Your Purchase plan; and (b) You will be entitled to any renewal discounts offered by the Vendor.
4. Changing Plans. When You change Your Purchase plan, You will be deemed to have made a new Purchase, and accordingly no renewal discount will be applicable for such change. You may, however, be entitled to pro-rated Fees for the new Purchase (as further described here: [https://freemius.com/help/documentation/selling-with-freemius/proration/](https://freemius.com/help/documentation/selling-with-freemius/proration/)).
5. General. Pricing for the Product is exclusive of all applicable sales, use, consumption, VAT, GST, and other taxes, duties or governmental charges, except for taxes based upon Freemius' net income. Unless expressly stated otherwise in the Checkout, all amounts payable under this Agreement:
1. are stated, and are to be paid, in US Dollars;
2. are payable in advance (accordingly to the applicable billing cycle); and
3. are non-refundable (subject to the Vendor Refund Policy), and are without any right of set-off or cancellation.
5. PRODUCT SUPPORT AND MAINTENANCE
-------------------------------
All support and maintenance services for the Product (such as providing bug fixes, updates, upgrades, troubleshooting, _etc._), if any, are the sole responsibility of the Vendor, and You agree: (a) to look to the Vendor alone for such support and maintenance; and (b) that Freemius has no obligation to provide any such (or similar) services under this Agreement. Nor does Freemius offer or give any Product warranty (see Section 8 _(Disclaimer of Warranties)_ for more information). Any Product support and maintenance services that are provided by the Vendor will (unless the Vendor agrees in writing with You otherwise) only be provided to You (or Your service provider, if applicable) and with respect to the applicable Site(s). Some updates and upgrades may be implemented by the Vendor automatically, and some may be implemented manually; but in either case, updates and upgrades to the Product will override any prior modifications You made to the Product. Moreover: (i) You will not be eligible for support and maintenance services in the event You modify the Product, nor following termination or cancellation of Your Purchase; and (ii) no undertaking is made by Vendor that it will support or maintain the Product (for example, if the Vendor ceases to do business or retires the Product), even if You have purchased a Lifetime License. Vendor's support contact is: [support@better-messages.com](mailto:support@better-messages.com) The only support Freemius shall be obligated to provide under this Agreement is first-tier aftersales support (which includes billing and order-related support), which will be provided to You only.
6. PRODUCT FEATURES
----------------
As with support and maintenance services, features of the Product are also the sole responsibility of the Vendor. This includes, but is not limited to, issues as to feature availability, operability, blocking, and de-activation. A new or modified feature may be accompanied by separate or additional terms and conditions. You agree: (a) to look to the Vendor alone for issues relating to features; and (b) that Freemius has no obligation to address issues relating to features. _Moreover, and in respect of Licenses that are configured by the Vendor as 'blocking' Licenses:_ following termination or cancellation of Your Purchase or Your Paid Trial, or expiration of Your free Trial without a payment method, some or all of the Product's 'paid' features may be disabled by the Vendor (and in the event Your Purchase plan is 'monthly', and depending on Your billing cycle, such 'paid' features are automatically disabled), and You acknowledge that this may have the effect of disabling or rendering unusable the entire Product itself.
7. OWNERSHIP
---------
1. Product. Freemius and/or its licensors (including without limitation the Vendor) exclusively own all Intellectual Property Rights (defined below) in and to the Product. Furthermore, Freemius and/or its licensors shall exclusively own (and are hereby assigned) all Intellectual Property Rights in and to any derivative works and/or improvements in or to the Product (regardless of inventorship or authorship); unless the Product is governed by Third Party Software Terms that permit You to make derivative works and/or improvements to the Product, in which case, as between You, Freemius and Vendor, You will exclusively own the Intellectual Property Rights in and to such derivative works and improvements. Except for the License, You are granted no other right or license in or to the Product, whether by implied license, estoppel, patent exhaustion, operation of law, or otherwise. Any rights not expressly granted herein are hereby reserved by Freemius and its licensors. You agree that Vendor shall be a third party beneficiary under this Agreement with the right to enforce provisions hereunder that relate to Vendor's Intellectual Property Rights.
2. Feedback. If You provide Freemius with any ideas, suggestions, or similar feedback about performance of the Product or for improving the Product (“_Feedback_”), You hereby grant to each of Freemius and all Freemius Affiliates a worldwide, assignable, non-exclusive, royalty-free, fully paid-up, sublicensable (through multiple tiers of sublicensees), irrevocable, and perpetual license, to access, use, reproduce, distribute, publish, broadcast, make available to the public, modify, adapt, edit, create derivative works of, publicly display, publically perform, and otherwise commercially exploit such Feedback, in any media format and through any media channels (now known or hereafter developed) (“_Feedback License_”). You hereby represent and warrant that: (A) the Feedback does not, and will not, infringe, misappropriate or violate any third party's Intellectual Property Rights, or any law; and (B) You have obtained, and will maintain during and after this Agreement, all licenses, permissions, consents, approvals, and authorizations required to grant the Feedback License. The Feedback License shall survive any termination of this Agreement.
3. Definition of IP Rights. “_Intellectual Property Rights_” means any and all rights, titles, and interests in and to inventions, works of authorship, databases, technology, designs, and other intellectual property, and includes without limitation patents, copyright and similar authorship rights, personal rights (such as moral rights, rights of privacy, and publicity rights), architectural, building and location (and similar geography-based) rights, mask work rights, trade secret and similar confidentiality rights, design rights, database rights, industrial property rights, trademark, trade name, trade dress and similar branding rights, as well as: (a) all applications, registrations, renewals, extensions, continuations, continuations-in-part, divisions or reissues of the foregoing rights; and (b) all goodwill associated with the foregoing rights.
8. TERM AND TERMINATION
--------------------
1. Purchase Term and Renewals. This Agreement commences on the Effective Date and shall, unless terminated in accordance herewith, continue in full force and effect for the duration of the Purchase Term. If the Purchase Term is 'monthly' or 'annual', it shall automatically renew for successive periods of equal length, unless you cancel the Purchase by canceling the subscription prior to such renewal in accordance with the below. If the Purchase Term is 'annual' (including multi-annual), Freemius may (but shall not be obligated to) provide You with a reminder of the upcoming renewal. You acknowledge that such a reminder would only be a courtesy, and You alone are responsible for taking any action before a renewal takes effect.
2. Cancellation by You. You may cancel Your Purchase at any time and for any reason, via the functionality offered. If You cancel the Purchase, the cancellation will take effect immediately (and will automatically stop any renewals) and the corresponding License will terminate at the end of the then-current Purchase Term. If you purchased a Lifetime License, the Purchase is not eligible for cancellation by You. For the avoidance of doubt, You will not be entitled to any refund in cases where You cancel Your Purchase. If You cancel a Trial, the Product's 'paid' features will be automatically disabled, unless the Product is designated as 'premium-only', in which case the entire Product will be disabled. If You object to any provision of this Agreement or any subsequent changes thereto, or become dissatisfied with the Product in any way, Your only recourse against Freemius is to cancel Your Trial or Purchase (as applicable) as aforementioned.
3. Termination by Freemius for Convenience. Freemius may, at any time, terminate Your Purchase (regardless of the Purchase Term) for convenience, by written notice to You (including via the functionality offered). In such cases, Freemius shall give You a pro-rated refund of any prepaid Fees, as follows: (a) in the case of a Lifetime License, depreciated on a three (3) year straight line basis from the date of installation of the Product; and (b) in the case of a Subscription License (such as 'monthly' or 'annual'), based on the remaining then-current Purchase Term.
4. Termination by Freemius for Breach. Freemius may terminate Your Purchase (regardless of the Purchase Term) in the event You breach any material provision of this Agreement (for example, if you breach the License) and fail to cure such breach, if curable, within thirty (30) days of receiving written notice from Freemius. For the avoidance of doubt, You will not be entitled to any refund in the event of such termination.
5. Effect of Purchase Termination. Upon termination or cancellation of Your Purchase: (a) the License automatically terminates, and You must immediately cease all access to and use of the Product except to the extent any features of the Product remain available to You; (b) You shall promptly pay any unpaid amounts that are outstanding as of such termination or cancellation. Termination and cancellation shall not affect any rights and obligations accrued as of the effective date thereof.
6. Survival. Any provision that is stated to survive, or that ought by its nature to survive, shall survive termination of this Agreement. The following shall also survive termination of this Agreement: Sections 7 (_Ownership_) through 14 (_Miscellaneous_) inclusive.
9. DISCLAIMER OF WARRANTIES
------------------------
THE PRODUCT, AS WELL AS ANY OTHER ITEMS OR SERVICES PROVIDED BY FREEMIUS, ARE PROVIDED AND MADE AVAILABLE TO YOU ON AN “AS IS” AND “AS AVAILABLE” BASIS, WITH ALL FAULTS, AND WITHOUT ANY REPRESENTATION, WARRANTY, GUARANTEE OR CONDITION OF ANY KIND WHATSOEVER, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY, QUIET POSSESSION, TITLE, QUALITY OF SERVICE, NON-INFRINGEMENT, OR THAT OTHERWISE ARISE FROM A COURSE OF PERFORMANCE OR DEALING, OR USAGE OF TRADE, ALL OF WHICH ARE HEREBY DISCLAIMED BY FREEMIUS AND ITS LICENSORS AND SUPPLIERS (INCLUDING WITHOUT LIMITATION THE VENDOR). IN ADDITION, NEITHER FREEMIUS NOR ITS LICENSORS OR SUPPLIERS (INCLUDING WITHOUT LIMITATION THE VENDOR) DOES NOT MAKE ANY REPRESENTATION, WARRANTY, GUARANTEE OR CONDITION: (A) REGARDING THE EFFECTIVENESS, USEFULNESS, RELIABILITY, AVAILABILITY, TIMELINESS, ACCURACY, OR COMPLETENESS OF THE PRODUCT; (B) THAT YOUR USE OF, OR RELIANCE UPON, THE PRODUCT WILL MEET ANY REQUIREMENTS OR EXPECTATIONS; (C) THAT THE PRODUCT WILL BE UNINTERRUPTED, SECURE, ERROR-FREE OR VIRUS-FREE, OR THAT DEFECTS WILL BE CORRECTED; OR (D) REGARDING THE SATISFACTION OF, OR COMPLIANCE WITH, ANY GOVERNMENT REGULATIONS OR STANDARDS.
10. LIMITATION OF LIABILITY
-----------------------
1. IN NO EVENT SHALL FREEMIUS, ANY FREEMIUS AFFILIATE, OR ANY OF OUR LICENSORS OR SUPPLIERS (INCLUDING WITHOUT LIMITATION THE VENDOR) BE LIABLE UNDER, OR OTHERWISE IN CONNECTION WITH, THIS AGREEMENT, FOR:
1. ANY CONSEQUENTIAL, INDIRECT, SPECIAL, INCIDENTAL, OR PUNITIVE DAMAGES;
2. ANY LOSS OF PROFITS, LOSS OF BUSINESS, LOSS OF REVENUE, OR LOSS OF ANTICIPATED SAVINGS;
3. ANY LOSS OF, OR DAMAGE TO, DATA, REPUTATION, OR GOODWILL; AND/OR
4. THE COST OF PROCURING ANY SUBSTITUTE GOODS OR SERVICES.
2. THE COMBINED AGGREGATE LIABILITY OF FREEMIUS AND ALL FREEMIUS AFFILIATES, AS WELL AS THE VENDOR, UNDER, OR OTHERWISE IN CONNECTION WITH, THIS AGREEMENT SHALL NOT EXCEED THE AMOUNTS ACTUALLY PAID BY YOU TO FREEMIUS UNDER THIS AGREEMENT FOR THE APPLICABLE PRODUCT THAT GAVE RISE TO LIABILITY.
3. THE FOREGOING EXCLUSIONS AND LIMITATIONS SHALL APPLY: (A) TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW; (B) EVEN IF FREEMIUS, A FREEMIUS AFFILIATE, OR THE VENDOR HAS BEEN ADVISED, OR SHOULD HAVE BEEN AWARE, OF THE POSSIBILITY OF LOSSES, DAMAGES, OR COSTS; (C) EVEN IF ANY REMEDY IN THIS AGREEMENT FAILS OF ITS ESSENTIAL PURPOSE; AND (D) REGARDLESS OF THE THEORY OR BASIS OF LIABILITY, INCLUDING WITHOUT LIMITATION BREACH OF WARRANTY, NEGLIGENCE, MISREPRESENTATION, STRICT LIABILITY, OR OTHER CONTRACT OR TORT LIABILITY.
11. INDEMNIFICATION
---------------
1. If any third party (including, but not limited to, a regulatory or governmental authority) brings any kind of demand, claim, suit, action or proceeding against Freemius, a Freemius Affiliate, the Vendor, and/or any of our or their respective directors, officers, employees, or representatives (each, an “_Indemnitee_”), and it is based upon or arises from:
1. Your use of the Product;
2. Your breach under any contract You may have with a Vendor; and/or
3. Your breach of any provision of this Agreement
(each of the foregoing, an “_Indemnity Claim_”) then, upon written request by Freemius (to be decided in our sole discretion), You agree to assume full control of the defense and settlement of the Indemnity Claim; _provided, however,_ that (c) Freemius reserves the right, at any time thereafter, to take over full or partial control of the defense and/or settlement of the Indemnity Claim, and in such cases You agree to reasonably cooperate with Freemius' defense activities at Your own cost and expense; and (d) You shall not settle any Indemnity Claim, or admit to any liability thereunder, without the express prior written consent of the Indemnitee(s).
2. In addition, and regardless of whether (or the extent to which) You controlled or participated in the defense and/or settlement of an Indemnity Claim, You agree to indemnify and hold harmless the Indemnitee(s) for and against: (e) any costs and expenses (including reasonable attorneys' fees) incurred by the Indemnitee(s) in the defense of the Indemnity Claim; and (f) any amounts awarded against, or imposed upon, the Indemnitee(s) under such Indemnity Claim, or otherwise paid in settlement of the Indemnity Claim (including without limitation any fines or penalties).
12. GOVERNING LAW
-------------
This Agreement (including without limitation its validity and formation) shall be governed by, and construed in accordance with, the laws of the State of New York, USA without regard to any conflicts of laws rules or principles. The United Nations Convention on Contracts for the International Sale of Goods and the Uniform Computer Information Transaction Act shall not apply to this Agreement and are hereby disclaimed.
13. DISPUTE RESOLUTION
------------------
__Please read this Section carefully.__
1. Mandatory, Bilateral Arbitration. YOU AND FREEMIUS AGREE THAT ANY DISPUTE, CONTROVERSY OR CLAIM ARISING UNDER, OR OTHERWISE IN CONNECTION WITH, THIS AGREEMENT (EACH, A “_Dispute_”) SHALL BE RESOLVED ONLY BY FINAL AND BINDING BILATERAL ARBITRATION, except that each party retains the right to bring an individual action in a small claims court and the right to seek injunctive or other equitable relief in a court of competent jurisdiction to prevent the actual or threatened infringement, misappropriation or violation of a party’s Intellectual Property Rights. This agreement to arbitrate is intended to be broadly interpreted.
1. ### _Arbitration Rules and Governing Law_
* Notwithstanding Your and Freemius’ agreement that New York law governs this Agreement and its validity, interpretation and application, You and Freemius hereby further agree that the Federal Arbitration Act, 9 U.S.C. § 1, et seq. (“_FAA_”) applies to this agreement to arbitrate, and governs all questions of whether a Dispute is subject to arbitration.
* Unless You and Freemius expressly agree otherwise in writing in respect of a Dispute, the arbitration shall be administered by Judicial Arbitration and Mediation Services, Inc. (“_JAMS_”), pursuant to JAMS Streamlined Arbitration Rules and Procedures (“_JAMS Streamlined Rules_”), as modified by this Agreement (that is, the terms of this Section 17 govern if they conflict with any of the JAMS Streamlined Rules), and consistent with the _JAMS Policy on Consumer Arbitrations Pursuant to Pre-Dispute Clauses Minimum Standards of Procedural Fairness_ (“_JAMS Consumer Fairness Standards_”). The arbitrator must honor the terms and conditions of this Agreement (including without limitation all liability exclusions and limitations), and can award damages and relief, including any attorneys’ fees authorized by law. YOU AGREE THAT, BY ENTERING INTO THIS AGREEMENT, YOU AND FREEMIUS ARE HEREBY EACH IRREVOCABLY WAIVING THE RIGHT TO A TRIAL BY JURY AND THE RIGHT TO PARTICIPATE IN A CLASS ACTION (OR OTHER CLASS-WIDE PROCEEDING).
* Notwithstanding JAMS Streamlined Rule 8(b), You and Freemius agree that any dispute as to the arbitrability of a Dispute brought by either You or Freemius shall be resolved by a court of competent jurisdiction.
2. ### _No Class Arbitrations_
THIS ARBITRATION AGREEMENT DOES NOT ALLOW CLASS ARBITRATIONS EVEN IF THE JAMS STREAMLINED RULES, (OR OTHER PROCEDURES OR RULES OF JAMS) WOULD. RATHER, YOU AND FREEMIUS ARE ONLY ENTITLED TO PURSUE ARBITRATION ON AN INDIVIDUAL BASIS. FURTHER, AND UNLESS YOU AND FREEMIUS EXPRESSLY AGREE OTHERWISE IN WRITING IN RESPECT OF A DISPUTE, THE ARBITRATOR MAY NOT CONSOLIDATE MORE THAN ONE INDIVIDUAL PARTY’S DISPUTE WITH ANY OTHER PARTY’S DISPUTE(S), AND MAY NOT OTHERWISE PRESIDE OVER ANY FORM OF A REPRESENTATIVE OR COLLECTIVE PROCEEDING.
3. ### _The Arbitrator's Decision_
* The arbitrator will be subject to this Agreement, and shall not make any decision or award that is in excess of, or contrary to, what this Agreement provides. The arbitrator will render an award in accordance with JAMS Streamlined Rules. The arbitrator’s decision will include the essential findings and conclusions upon which the arbitrator based the award. Judgment on the arbitration award may be entered in any court having jurisdiction thereof. In the event any litigation should arise between You and Freemius in any court of competent jurisdiction in a proceeding to vacate or enforce an arbitration award, YOU AND FREEMIUS HEREBY IRREVOCABLY WAIVE ALL RIGHTS TO A JURY TRIAL, instead electing that the proceeding be resolved by a judge. The arbitrator may award declaratory or injunctive relief only in favor of the plaintiff/claimant and only to the extent necessary to provide relief warranted by the claimant’s individual claim. If You prevail in arbitration You will be entitled to an award of attorneys' fees and expenses, to the extent provided under applicable Law. Freemius will not seek, and hereby waives all rights Freemius may have under applicable Law, to recover attorneys’ fees and expenses if Freemius prevails in arbitration, unless You assert a frivolous claim.
* The arbitrator’s decision and award is final and binding, with some exceptions under the FAA.
4. ### _Location and Fees_
* Unless You and Freemius expressly agree otherwise in writing, the arbitration will take place in-person at the following locations: (a) if You are a resident of a country in North America, Central America or South America, the arbitration will take place in New York City, New York, USA; or (b) if You are a resident of any other country in the world, the arbitration will take place in Tel Aviv-Jaffa, Israel. In the event JAMS indicates that it is unable to provide, or arrange for, an arbitrator in Israel, You agree that the arbitration will be held in New York City, New York, USA.
* If You initiate an arbitration for a Dispute, You will be required to pay $250 of the fee required to initiate the arbitration and Freemius will pay any remaining JAMS Case Management Fees and all professional fees for the arbitrator’s services; You will remain responsible for its respective costs relating to counsel, experts, witnesses, and travel to the arbitration.
* If Freemius initiates an arbitration for a Dispute, Freemius will pay all administrative fees and costs related to the arbitration, including all professional fees for the arbitrator’s services; You will remain responsible for its costs relating to counsel, experts, witnesses, and travel to the arbitration.
5. ### _Small Claims Court_
Notwithstanding the foregoing, either party may bring an individual action in a small claims court for Disputes within the scope of such court’s jurisdiction. This agreement to arbitrate does not preclude You from bringing issues to the attention of federal, state, or local agencies. Such agencies can, if the Law allows, seek relief against Freemius on Your behalf.
2. Opting Out of this Mandatory Arbitration. You can decline this agreement to arbitrate by contacting [legal@freemius.com](mailto:legal@freemius.com) within thirty (30) days of the Effective Date and stating that You decline this arbitration agreement. Furthermore, and notwithstanding the provisions regarding modification of the Agreement, if Freemius changes this _Dispute Resolution_ Section after the Effective Date (or the date You accepted any subsequent changes to this Agreement), You may reject any such change by providing Freemius written notice of such rejection to [legal@freemius.com](mailto:legal@freemius.com) within thirty (30) days of the date such change became effective, as per the terms of this Agreement. In order to be effective, the notice must include Your full name and clearly indicate its intent to reject the change(s) to this _Dispute Resolution_ Section. By rejecting such change(s), You are agreeing that it will arbitrate any Dispute between You and Freemius in accordance with the provisions of this _Dispute Resolution_ Section as of the Effective Date (or the date You accepted any subsequent changes to this Agreement), unless You declined this arbitration agreement in the manner described above.
3. Limitation on Claims. Regardless of any law to the contrary, any claim or cause of action arising out of, or related to, this Agreement must be filed within one (1) year after such claim or cause of action arose, or else You agree that such claim or cause of action will be barred forever.
4. Confidentiality of Disputes. All aspects of the arbitration proceeding, including but not limited to the decision and award of the arbitrator and compliance therewith, shall be strictly confidential. The parties agree to maintain its confidentiality, unless (and in such cases, only the extent) otherwise required by applicable law. This paragraph shall not prevent a party from submitting to a court of competent jurisdiction any information necessary to enforce an arbitration award, or to seek equitable relief.
14. MISCELLANEOUS
-------------
1. Entire Agreement. This Agreement represents the entire agreement between You and Freemius with respect to the subject matter hereof, and supersedes and replaces any and all prior and contemporaneous oral and/or written agreements, understandings and statements between You and Freemius with respect to such subject matter. You acknowledge and agree that in entering into this Agreement You have not relied on any statement or representation (whether negligently or innocently made) not expressly set out in this Agreement, such as statements and explanations in any FAQs, summaries or explanatory guides regarding this Agreement, or other marketing material on the Freemius or Vendor websites. To the extent of any conflict or inconsistency between these terms and conditions on the one hand, and the Checkout on the other hand, the former shall prevail. The language of this Agreement is expressly agreed to be the English language. By entering into the Agreement, You hereby irrevocably waive, to the maximum extent legally permitted, any law applicable to You requiring that the Agreement be localized to meet Your language (as well as any other localization requirements), or requiring an original (non-electronic) signature or delivery or retention of non-electronic records. We may be able (but are not obligated) to provide You with copies of this Agreement on written request; _however_, please be sure to print a copy of this Agreement for Your own records.
2. Assignment. Freemius may assign this Agreement (or any of its rights and/or obligations hereunder) without Your consent, and without notice or obligation to You. This Agreement is personal to You, and, except as permitted by this Agreement, You may not assign (or in any other way transfer) this Agreement (or any of its obligations or rights hereunder) without Freemius' express prior written consent. Any prohibited assignment shall be null and void.
3. Severability. If any provision of this Agreement is held by a court of competent jurisdiction to be illegal, invalid or unenforceable, then: (a) the remaining provisions of this Agreement shall remain in full force and effect; and (b) the Parties hereto agree that the court making such determination shall have the power to limit the provision, to delete specific words or phrases, or to replace the provision with a provision that is legal, valid and enforceable and that most closely approximates the original legal intent and economic impact of such provision, and this Agreement shall be enforceable as so modified in respect of such jurisdiction. In the event such court does not exercise the power granted to it as aforesaid, then such provision will be ineffective solely as to such jurisdiction (and only to the extent and for the duration of such illegality, invalidity or unenforceability), and will be substituted (in respect of such jurisdiction) with a valid, legal and enforceable provision that most closely approximates the original legal intent and economic impact of such provision.
4. Remedies. Except as may be expressly stated otherwise in this Agreement, no right or remedy conferred upon or reserved by any party under this Agreement is intended to be, or shall be deemed, exclusive of any other right or remedy under this Agreement, at law or in equity, but shall be cumulative of such other rights and remedies.
5. Waiver. No failure or delay on the part of any party in exercising any right or remedy under this Agreement shall operate as a waiver thereof, nor shall any single or partial exercise of any such right or remedy preclude any other or further exercise thereof or the exercise of any other right or remedy. Any waiver granted hereunder must be in writing (for waivers by You, emails will be acceptable; for waivers by Freemius, the writing must be duly signed by an authorized representative of Freemius), and shall be valid only in the specific instance in which given.
6. Relationship. The relationship of the parties is solely that of independent contractors. Nothing in this Agreement shall be deemed to create any employment, fiduciary, joint venture, agency or other relationship between the parties.
7. Notices. You agree that Freemius may send You notices by email and/or by regular mail. Except as stated otherwise in this Agreement or required by law applicable to You, You agree to send all notices to Freemius, to [support@freemius.com](mailto:support@freemius.com).
8. No Third Party Beneficiaries. Except as otherwise expressly provided in this Agreement (such as Freemius Affiliates, Freemius' licensors and suppliers (including without limitation the Vendor), and Indemnitees), there shall be no third-party beneficiaries of or under this Agreement.
9. U.S. Government Rights. The Product is “commercial computer software” and the documentation is “commercial computer software documentation”, pursuant to DFAR Section 227.7202 and FAR Section 12.212, as applicable. If You are an agency, department, employee or other entity of the United States Government, then Your access to and use of the Product shall be subject solely to the terms and conditions of this Agreement.
10. Export Compliance. You represent and warrant that: (a) You are not a resident of (and You will not use the Product in) a country that the U.S. government has embargoed for use of the Product, nor are You named on the U.S. Treasury Department’s list of Specially Designated Nationals or any other applicable trade sanctioning regulations of any jurisdiction; and (b) Your country of residence and/or incorporation (as applicable) is the same as the country specified in the contact and/or billing address provided to us. In the event You breach this Section (in whole or in part), or otherwise violate any Export Control Laws (defined below) in connection with the Product, You agrees to indemnify and hold harmless Freemius, all Freemius Affiliates, and the Vendor (including ours and their respective directors, officers, and employees) for any fines and/or penalties imposed upon Freemius, a Freemius Affiliate, and/or Vendor (or such individuals) as a result of such breach or violation. “_Export Control Laws_” means all applicable export and re-export control Laws applicable to You and/or Freemius, as well as the United States' Export Administration Regulations (EAR) maintained by the US Department of Commerce, trade and economic sanctions maintained by the US Treasury Department's Office of Foreign Assets Control, and the International Traffic in Arms Regulations (ITAR) maintained by the US Department of State.
11. Force Majeure. Freemius shall not be responsible for any failure to perform any obligation or provide any service hereunder because of any (a) act of God, (b) war, riot or civil commotion, (c) governmental acts or directives, strikes, work stoppage, or equipment or facilities shortages, and/or (d) other similar cause beyond Freemius' reasonable control. For the avoidance of doubt, any problems relating to the hosting of the Service shall not be deemed within Freemius' reasonable control.
---
## Group Voice Calls in WordPress Chat
# HD Group Audio Chat
The WebSocket version turns any conversation, group chat, or chat room into a **multi-party voice call** supporting up to 50 simultaneous participants. The feature uses WebRTC with a dedicated media server for efficient routing — call quality stays high even with dozens on the line, while bandwidth stays modest compared to video.
:::info WebSocket version
Group audio chat is a WebSocket-version feature. The free version does not include voice calling.
:::
## What it adds
- Up to **50 simultaneous voice participants** per call
- Works in private one-on-one conversations, group chats, and chat rooms
- Lower bandwidth than group video — typically 50–80 kbps per participant
- Media-server routing (SFU model) for stable quality at scale
- Remote mute/unmute control for the call host
- Per-role restrictions: control which user roles can place or join calls
- Optional **mini-chat call buttons** in members directories and on profile pages
- Bandwidth-friendly fallback for users on cellular / low-quality connections
## How it works
A user clicks the **Voice Call** button in a conversation. Better Messages signals the request through the WebSocket relay; the cloud server allocates a call room on the media server. All participants connect to the media server via WebRTC. Each participant uploads their own microphone stream once; the media server distributes streams to everyone else — this is dramatically more efficient than full mesh (where each participant uploads to every other participant individually).
| Topology | Network upload per participant |
|---|---|
| Full mesh (peer-to-peer) | (N−1) × stream — quadratic, breaks past 5–6 participants |
| Media server (SFU) | 1 × stream — flat, scales to 50+ |
The host (the user who started the call) can remotely mute disruptive participants. Participants can also self-mute, self-unmute, and leave anytime.
The call session is independent of the underlying conversation thread — when the call ends, the conversation remains exactly as it was, with a system message noting "Voice call ended" and duration.
## When to use group voice over group video
| Choose group voice when… | Choose group video when… |
|---|---|
| 10+ participants | Visual presence matters |
| Mobile/cellular users | High-bandwidth connections |
| Discussion / audio-first content | Demo, screen-share, face-to-face |
| Bandwidth-constrained users | Standard broadband |
| Privacy preference for audio only | Trust-building, sales / coaching |
## Requirements
- Site must be served over **HTTPS** (browser WebRTC requirement)
- Each participant needs a working microphone
- Modern browser with WebRTC support (Chrome, Firefox, Edge, Safari, mobile equivalents)
- WebSocket-version license active
## Configuration
Per-role restrictions and optional mini-chat call buttons apply to both audio and video group calls — see [Group Video Chat → Per-role restrictions](./group-video-chat.mdx#per-role-restrictions) for the shared admin controls.
## Frequently asked questions
### What is the maximum number of participants?
50 simultaneous voice participants. Sites that regularly need more can contact support to discuss the self-hosted plan, where the cap can be raised based on media-server capacity.
### Are group voice calls recorded?
No — calls are real-time only and not recorded by default. The plugin doesn't include built-in recording. Sites that need recording typically use a screen-recording layer at the participant level or browser-based recording extensions, subject to participant consent.
### Can guests (non-logged-in users) join a group voice call?
Yes — if guest chat is enabled on the chat room, guests can join voice calls placed in that room. They appear by their entered display name.
### What's the bandwidth requirement per participant?
About 50–80 kbps upload + 50–80 kbps download per active speaker. A 20-person call uses about 1.5 Mbps download on each device. The codec is Opus.
### Does the media server store anything?
No. The media server routes audio streams in memory only — no storage, no recording, no transcription on the audio path. Call metadata (start time, participants, duration) is logged for the host's call history.
## See also
- [Group video chat](/docs/websocket/group-video-chat/) — same scaling model with video
- [Audio calls](/docs/websocket/audio-calls/) — one-on-one voice calling
- [Video calls](/docs/websocket/video-calls/) — one-on-one video calling
- [WordPress video call plugin](/blog/wordpress-video-call-plugin/) — feature post covering the full call stack
- [WordPress group chat plugin](/blog/wordpress-group-chat-plugin/) — group chat overview
---
## Group Video Calls in WordPress Chat
# HD Group Video Chat
The WebSocket version enables **multi-party video calls** supporting up to 32 simultaneous participants. Works in any conversation, group chat, or chat room. Uses WebRTC with a media server (SFU) for efficient routing — call quality stays high even at scale.
:::info WebSocket version
Group video chat is a WebSocket-version feature. For voice-only multi-party (up to 50), see [group audio chat](/docs/websocket/group-audio-chat/).
:::
## How it works
Group video chat can be started in any conversation, group chat, or chat room. The feature uses WebRTC with a media server for efficient multi-party video routing. All participants can see and hear each other simultaneously, with adaptive video quality that adjusts based on network conditions and the number of participants. Screen sharing is also available during group video chats.
## Key capabilities
- Up to 32 simultaneous video participants
- Available in conversations, group chats, and chat rooms
- Adaptive video quality based on network conditions
- Screen sharing during group video calls
- Media server for efficient multi-party routing
- Remote mute/unmute of participant microphones by the call host
- WebRTC-based for low latency
- Per-role restrictions for who can start and who can join — see below
- Optional group call buttons in the mini chat header — see below
- Available to guest visitors and AI bot participants when they're members of the conversation
## Requirements
- Website must use **HTTPS**
- Users need a working webcam and microphone
- Modern browser with WebRTC support
This feature is automatically available with the WebSocket version.
## Per-role restrictions
Site administrators can block specific WordPress roles from starting and / or joining group calls. Open **WP Admin → Better Messages → Settings → Group Calls → Group Call Restrictions**.