Leyp til innihald
WordPress.org

Faroese

  • Themes
  • Plugins
  • News
  • About
  • Contact
  • Get WordPress
Get WordPress
WordPress.org

Plugin Directory

NXT Cloud Chat – CRM, Inbox & OTP Login

  • Submit a plugin
  • My favorites
  • Log in
  • Submit a plugin
  • My favorites
  • Log in

NXT Cloud Chat – CRM, Inbox & OTP Login

By NXTWEBSITE
Download
  • Details
  • Reviews
  • Installation
  • Development
Support

Description

NXT Cloud Chat connects WordPress directly to Meta’s official WhatsApp Cloud API. Manage conversations, CRM contacts, sales pipelines, team access, and OTP login from WordPress admin.

Built for stores, sales and support teams, membership sites, agencies, and developers that need a self-hosted WhatsApp CRM.

Free Plugin

  • Shared inbox with explicit ticket creation, private notes, filters, followers, assignments, SLA indicators, and agent-view receipts.
  • CRM contacts, groups, tags, lifecycle stages, follow-up tasks, ownership, duplicate detection, and activity history.
  • Sales pipelines, configurable stages, deals, line items, values, and stage history.
  • Access Teams with module permissions and record scopes.
  • WhatsApp OTP login for WordPress and WooCommerce My Account.
  • Message history, delivery status, webhooks, connection health, and secure media access.
  • Optional browser Web Push alerts with shared unread counts and previews off by default.
  • Stable PHP wrappers, hooks, and runtime capability discovery.

Pro Add-on

Pro adds approved templates, broadcasts, dynamic segments, WooCommerce notifications, abandoned cart recovery, visual workflows, logs, retries, analytics, and CSV exports.

Setup and Privacy

Connect your own Meta app and credentials. Configured messaging operations use Meta’s servers; CRM records remain in your WordPress database. Credentials are encrypted at rest when supported. Optional Web Push uses browser-vendor push services, as described below.

  • Step-by-step setup guide
  • Plugin website
  • Upgrade to NXT Cloud Chat Pro

External Services

This plugin connects to the official WhatsApp Business Platform / WhatsApp Cloud API provided by Meta Platforms, Inc. Using this plugin means data will be transmitted from your WordPress site to Meta’s servers as described below.

What It Is Used For

  • 1-to-1 WhatsApp messaging – send and receive WhatsApp messages between your business number and your contacts from the WordPress Chat Window.
  • WhatsApp OTP login – send one-time passwords to users’ WhatsApp numbers for passwordless WordPress or WooCommerce login.
  • Template messaging – sync approved WhatsApp message templates from your Meta Business account and send them for notifications, authentication, broadcasts, and automation (Pro).
  • Broadcast campaigns – send bulk WhatsApp campaigns to selected contacts using approved templates (Pro).
  • Webhook event handling – receive inbound messages, delivery status updates, read receipts, and message events from the WhatsApp Cloud API.
  • WooCommerce notifications – send order and customer communication messages via WhatsApp (Pro).
  • COD verification workflows – use WhatsApp login or automated WhatsApp confirmation messages to help verify COD orders and reduce fake orders or failed deliveries (Pro).
  • Abandoned cart recovery – send WhatsApp reminders for abandoned WooCommerce carts (Pro).
  • Workflow-triggered messages – send WhatsApp messages based on user login, WooCommerce events, CRM events, deal changes, conversation events, or custom triggers (Pro).
  • Connection diagnostics – verify your API credentials and send test template messages to confirm that your WhatsApp Cloud API setup is working correctly.

What Data Is Sent and When

  • During setup – your App ID, App Secret, Business / Messaging Account ID, Phone Number ID, and Access Token are stored in your WordPress database and used server-side to authenticate API calls and verify incoming webhook signatures (X-Hub-Signature-256). These values are not printed into public pages or client-side JavaScript.
  • When sending or receiving WhatsApp messages – the recipient phone number, message content, template name, template parameters, media attachments, and delivery metadata are sent to or received from the WhatsApp Cloud API.
  • During WhatsApp OTP login – the user’s phone number and OTP message template data are sent to the WhatsApp Cloud API.
  • During template sync – your Business / Messaging Account ID and Phone Number ID are used to fetch and synchronise approved templates from your Meta account.
  • During webhook delivery – Meta sends inbound messages, delivery receipts, read events, and status payloads to your WordPress webhook endpoint. These are validated server-side using your App Secret before being stored.

Service Provider

WhatsApp Business Platform / WhatsApp Cloud API by Meta Platforms, Inc.

  • Meta Privacy Policy
  • WhatsApp Privacy Policy
  • Meta Terms for WhatsApp Business
  • WhatsApp Business Solution Terms
  • WhatsApp Business Terms of Service
  • WhatsApp Business Messaging Policy
  • WhatsApp Messaging Guidelines
  • WhatsApp Cloud API Pricing

You are responsible for ensuring that your use of this plugin and the WhatsApp Cloud API complies with applicable laws, your privacy policy, Meta’s platform rules, and WhatsApp Business policies.

Optional Browser Push Services

Web Push is off until a signed-in inbox user explicitly enables this browser and grants browser permission. The plugin then sends encrypted notification payloads directly to the browser vendor’s push service: Google Firebase Cloud Messaging, Microsoft Windows Push Notification Services (Edge), Mozilla Autopush, or Apple Web Push. No separate paid push account is required.

The service receives a browser subscription endpoint, encrypted payload, expiry and delivery metadata, and the site’s public VAPID identity. Subscription endpoints and encryption secrets are encrypted in your WordPress database. Previews are off by default. When enabled, a notification can contain the contact name, shared unread count, and a short incoming-message preview. Otherwise it contains the plugin name and unread count. Your browser and operating system may display and retain notifications on lock screens.

Logging out revokes that WordPress session’s notification enrollment; other sessions remain independent. Push already accepted by a vendor cannot be recalled. Notifications do not grant access to WordPress: opening one requires normal login, tenant, and chat permissions. Browser/OS restrictions and server cron can delay or prevent display; push-service acceptance is not proof of delivery or reading.

  • Google Privacy Policy
  • Microsoft Privacy Statement
  • Mozilla Privacy Notice
  • Apple Privacy Policy

Features

Dashboard

  • Connection Health, Messaging Health, and Calling Health status cards.
  • Live status indicators for WhatsApp Cloud API credentials and webhook configuration.
  • Setup help links and support badge for guided onboarding.
  • CRM, SLA, lifecycle, tag, deal, automation, broadcast, and abandoned cart reporting (Pro).
  • Secure selected-range CSV exports with permission checks (Pro).

Deals – Sales Pipelines and Deal Tracking

  • Create pipelines with custom stages, colours, ordering, and required stage reasons.
  • Manage deals with owners, priorities, values, expected close dates, and line items.
  • Track stage-transition history and review deal activity in the contact timeline.
  • Duplicate, archive, or delete deals using guarded confirmation flows.
  • Use stable pipeline, deal, lifecycle, and line-item wrappers for integrations.

Chat Window – WhatsApp Inbox

A shared WhatsApp inbox for sales, support, and customer communication.

  • Browse, filter, and reply to WhatsApp conversations from WordPress.
  • Manage multiple tickets per contact with subject, category, persistent issue descriptions, status, priority, followers, and shared handoff notes.
  • Keep private notes visible only to their author while they retain record access. The latest own note is prefilled without duplicating unchanged text.
  • Combine multi-select assignment, status, and priority filters, including Following and Overdue. Selected criteria match the same accessible ticket.
  • Filter the chat list by latest-message source with Broadcast, Workflow, System, and Integration icons, plus an Unread-only control. Source icons start enabled; green shows that source and gray hides it. Chats with unread incoming messages remain eligible regardless of source selection, subject to access and ticket filters.
  • Save a ticket without sending a message. Save & Send requires message content, an open reply window, and the required permissions, with a disabled-button tooltip explaining unmet requirements.
  • Open a ticket from its number in chat activity history and see a compact header count excluding closed and unassigned tickets.
  • Assign tickets to users, teams, or queues with manual or automated routing.
  • Use saved inbox views: All, Mine, Team Queue, Unassigned, Overdue, and Recently Resolved.
  • Track SLA targets for first response and resolution.
  • Store message history with timestamps, delivery status, reply context, reactions, and secure media access.
  • Display server-side redacted previews for protected workflow template parameters sent with Pro 1.2.0. Hidden values stay hidden for all Chat Window users, including administrators.

Contacts – CRM Contact Management

  • Store phone number, country, name, custom fields, subscription status, and unsubscribe reasons.
  • Track lifecycle stages such as new lead, active prospect, customer, or closed customer.
  • Create follow-up tasks, assign owners, and use saved contact views.
  • Detect and merge duplicate contacts with guarded confirmation flows.
  • Review contact profiles and CRM activity timelines from Contacts or Chat Window.
  • Use stable contact upsert wrappers for safe integrations.

Groups

  • Create groups such as Leads, Members, VIP Customers, COD Customers, or Repeat Buyers.
  • Assign contacts manually or in bulk.
  • Use groups for broadcast targeting and workflow logic.
  • Verified-group protections help prevent accidental modification of important groups.

Tags

  • Create colour-coded CRM tags with descriptions.
  • Assign tags manually, in bulk, during import, or through compatible integrations.
  • Filter contacts by any, all, or none of selected tags.
  • Preserve tag names in exports and use stable tag wrappers for integrations.

Templates (Pro)

  • Create and manage templates directly from WordPress, and sync with Meta.
  • Browse templates by category such as marketing, utility, and authentication.
  • Use image headers, CTA buttons, quick replies, coupon codes, and dynamic placeholders.
  • Send individual template messages from Chat Window or Contacts.
  • Use templates in broadcasts, workflows, WooCommerce notifications, and abandoned cart recovery.

Send Broadcasts (Pro)

  • Build campaigns for selected groups or Dynamic Segments.
  • Use CTA buttons and approved template content.
  • Personalise messages with placeholders and target subscribed contacts.
  • Schedule campaigns or send immediately, then track delivery and read status.

Abandoned Carts (Pro)

Recover WooCommerce carts with WhatsApp reminders.

  • Track stale WooCommerce carts in a dedicated Abandoned Carts screen.
  • Review cart value, time abandoned, recovery status, and customer context.
  • Send WhatsApp recovery messages through workflows.
  • Configure stale-cart thresholds, retention periods, and cleanup schedules.

COD Order Verification

NXT Cloud Chat can help WooCommerce stores verify COD customers and reduce avoidable returns.

  • Use WhatsApp OTP login so customers verify their WhatsApp number before account access or checkout flows.
  • Sync verified WordPress users into CRM Contacts.
  • Use the Pro Contact is Verified workflow condition to check the current authentication state directly.
  • Branch by Cash on Delivery or Non-COD Payment and update the order to a registered WooCommerce status.
  • Add follow-up tasks for unconfirmed or high-risk COD orders.
  • Help reduce fake orders, unreachable customers, failed delivery attempts, and return-to-origin losses.

Segments (Pro)

  • Create tenant-scoped Dynamic Segments with a live rule builder.
  • Segment by subscription status, tags, groups, lifecycle stages, ownership, conversation state, tasks, and dates.
  • Add WooCommerce filters such as order value, order count, products, categories, coupons, refunds, statuses, and abandoned carts.
  • Preview audience size before sending.

Workflows (Pro)

Automate WhatsApp messaging and CRM actions without coding.

  • Trigger workflows from incoming messages, user logins, WooCommerce orders, abandoned carts, conversation changes, deal changes, contact lifecycle changes, tasks, or compatible plugin events.
  • Add conditions for tags, groups, lifecycle stages, ownership, segments, tasks, conversation state, SLA status, deal stage, order value, and cart context.
  • Send approved WhatsApp template messages.
  • Update contacts, tags, assignments, lifecycle stages, follow-up tasks, deals, line items, conversations, priorities, notes, and escalations.

Workflow Runs (Pro)

Monitor every automation execution.

  • View workflow logs with trigger event, contact, status, and timestamps.
  • Drill into individual runs to see step-by-step execution.
  • Track execution separately from message acceptance, delivery, read receipts, and failures.
  • Filter runs by tenant, workflow, execution, delivery, and creation date, including custom date ranges.
  • Review execution errors, message failure reasons, scheduled delays, and paginated run history.

History

Keep a complete record of WhatsApp messages.

  • Review inbound and outbound messages.
  • Filter by contact, direction, date range, or status.
  • View delivery status, read receipts, timestamps, template names, and contact details.
  • Use history for reporting, debugging, compliance review, and customer context.

Authentication – WhatsApp OTP Login

Offer passwordless login using WhatsApp OTP.

  • Shortcode: [nxtcc_login_whatsapp]
  • Users choose their country, enter their phone number, receive an OTP via WhatsApp, and verify.
  • Verified users are linked to their WhatsApp number for future login.
  • Optional WhatsApp login buttons for the WordPress login page and WooCommerce My Account page.
  • Optional force-migration page for moving existing users to WhatsApp login.
  • Verified WordPress users can be synced into CRM Contacts.
  • Admin controls for OTP length, cooldown, countries, button text, colours, corner style, and branding.

Settings – WhatsApp Cloud API Configuration

Configure WhatsApp Cloud API securely from WordPress.

  • Save App ID, App Secret, Access Token, Phone Number ID, Business / Messaging Account ID, and display phone number.
  • Run connection diagnostics and test template sends.
  • Generate Verify Token and copy Callback URL for Meta webhook setup.
  • Verify webhook signatures with App Secret-based X-Hub-Signature-256 validation.
  • Manage cleanup, retention, uninstall data removal, Team Access permissions, and record scopes.

Team Access and Permissions

Give users the right level of access for their role.

  • Create tenant Access Teams for WordPress users.
  • Set view-only or manage permission per module.
  • Control access for Dashboard, Deals, Chat Window, Contacts, Groups, Tags, Templates, Broadcasts, Abandoned Carts, Segments, Workflows, History, Authentication, and Settings.
  • Set record scopes such as assigned records, team queue, or all records.
  • Apply CRM access-policy enforcement across inbox, contacts, imports, exports, media downloads, and forwarding.

User-Friendly and Developer-Friendly

NXT Cloud Chat is designed for everyday WordPress users, business teams, agencies, and developers.

For users and teams:

  • Clean WordPress admin screens.
  • Guided setup links and support badge.
  • Contact, group, tag, deal, inbox, CRM, sales pipeline, and OTP login tools in one place.
  • Team access controls without custom coding.
  • Useful for support, sales, ecommerce, COD order verification, and customer follow-up.

For developers and agencies:

  • Free plugin and Pro add-on are separate and extensible.
  • Database schema, DAO helpers, filters, actions, runtime discovery, and stable wrappers for compatible integrations.
  • Shared integration contracts for compatible extensions.

Screenshots

Chat Window – Shared WhatsApp inbox with tickets, assignees, inbox filters, SLA indicators, contact profile, and full message history.
Chat Window – Shared WhatsApp inbox with tickets, assignees, inbox filters, SLA indicators, contact profile, and full message history.
Deals – Sales pipeline board with custom stages, deal cards, expected close dates, stage reasons, stage-transition history, and deal modals.
Deals – Sales pipeline board with custom stages, deal cards, expected close dates, stage reasons, stage-transition history, and deal modals.
Dashboard – WhatsApp connection health, messaging and calling status cards, CRM workload summary, and setup help links.
Dashboard – WhatsApp connection health, messaging and calling status cards, CRM workload summary, and setup help links.
Contacts – CRM contacts list with lifecycle stages, tags, ownership, follow-up tasks, saved views, duplicate detection, and bulk actions.
Contacts – CRM contacts list with lifecycle stages, tags, ownership, follow-up tasks, saved views, duplicate detection, and bulk actions.
Groups – Contact group management for leads, members, customers, COD buyers, and custom audiences.
Groups – Contact group management for leads, members, customers, COD buyers, and custom audiences.
Tags – CRM tag management with colours, descriptions, bulk assignment, contact filtering, and export support.
Tags – CRM tag management with colours, descriptions, bulk assignment, contact filtering, and export support.
Templates – WhatsApp template list with sync, category badges, CTA buttons, image headers, and per-contact send actions (Pro).
Templates – WhatsApp template list with sync, category badges, CTA buttons, image headers, and per-contact send actions (Pro).
Send Broadcasts – Bulk WhatsApp campaign builder for approved template messages and segmented audiences (Pro).
Send Broadcasts – Bulk WhatsApp campaign builder for approved template messages and segmented audiences (Pro).
Abandoned Carts – WooCommerce abandoned cart recovery table with cart value, time abandoned, and recovery status (Pro).
Abandoned Carts – WooCommerce abandoned cart recovery table with cart value, time abandoned, and recovery status (Pro).
Segments – Dynamic segment builder with rule conditions, live membership preview, and WooCommerce filters (Pro).
Segments – Dynamic segment builder with rule conditions, live membership preview, and WooCommerce filters (Pro).
Workflows – Visual WhatsApp automation builder with CRM, deal, conversation, login, WooCommerce, and abandoned cart triggers (Pro).
Workflows – Visual WhatsApp automation builder with CRM, deal, conversation, login, WooCommerce, and abandoned cart triggers (Pro).
Workflow Runs - Separate execution and message delivery dashboards, date filters, paginated runs, and step diagnostics (Pro).
Workflow Runs – Separate execution and message delivery dashboards, date filters, paginated runs, and step diagnostics (Pro).
History – WhatsApp message history with delivery status, read receipts, timestamps, template names, and contact details.
History – WhatsApp message history with delivery status, read receipts, timestamps, template names, and contact details.
Authentication – WhatsApp OTP login settings with OTP length, cooldown, allowed countries, force-migration URL, and login button appearance.
Authentication – WhatsApp OTP login settings with OTP length, cooldown, allowed countries, force-migration URL, and login button appearance.
WhatsApp login widget – WhatsApp login widget embedded on a WordPress page.
WhatsApp login widget – WhatsApp login widget embedded on a WordPress page.
WhatsApp login buttons – WhatsApp login buttons for the default WordPress login page and WooCommerce My Account login page.
WhatsApp login buttons – WhatsApp login buttons for the default WordPress login page and WooCommerce My Account login page.
Settings – WhatsApp Cloud API credentials, connection diagnostics, webhook URL, verify token, team access, retention tools, and support badge preferences.
Settings – WhatsApp Cloud API credentials, connection diagnostics, webhook URL, verify token, team access, retention tools, and support badge preferences.

Installation

Requires PHP 8.2 or later for both Free and Pro. Back up and test your site’s PHP upgrade before installing. If an already-active installation is downgraded, the plugin pauses its features and shows administrators upgrade guidance without deleting data.

  1. Install NXT Cloud Chat from Plugins → Add New, or upload it to /wp-content/plugins/, then activate it.
  2. Open NXT Cloud Chat → Settings.
  3. Enter the App ID, App Secret, Access Token, Phone Number ID, Business / Messaging Account ID, and optional display number.
  4. Save and run the connection diagnostic.

WhatsApp Webhook Setup

  1. Enable incoming messages in the Settings webhook section.
  2. Copy its Callback URL and Verify Token.
  3. In Meta WhatsApp → Configuration, add both values and subscribe to messages.
  4. Complete verification. Keep the matching App Secret saved for X-Hub-Signature-256 validation.

WhatsApp Login Setup

  1. Configure OTP and country options under NXT Cloud Chat → Authentication.
  2. Publish a page containing [nxtcc_login_whatsapp].
  3. Optionally enable login-page/My Account buttons and an existing-user migration URL.

FAQ

How do browser notifications work?

Open the bell beside Chats, enable this browser, and approve its notification permission. Choose Assigned to me and my team or All accessible chats; both honor current record permissions, regardless of inbox filters. Enable previews only when names and messages are safe to show on the device’s lock screen. The count is the shared inbox unread count, not a personal counter. The existing plugin logo is used; no avatar generation or contact-photo requests are added.

Web Push needs HTTPS, a supported browser, server cURL, mbstring and OpenSSL P-256 support, and working WordPress cron. Configure server cron to run due events at least once per minute for predictable processing. Missing push extensions disable notifications only. Supported iPhone/iPad configurations require a compatible Home Screen web app; this feature does not install a site-wide PWA. Settings -> Tools contains server diagnostics, a test is available in the bell panel, and no polling fallback is used.

Which browsers have been tested for notifications?

Real notification display has been confirmed in Chrome, Microsoft Edge, Firefox, and Android Chrome. Safari on macOS and iPhone/iPad Home Screen web apps remain unverified for this release. Browser profiles have independent subscriptions. Browser background settings do not guarantee delivery while that profile is fully closed; operating-system notification, battery, and Focus settings can delay or suppress display. Push-service acceptance does not confirm display on the device.

Why do old messages not generate notifications?

Alerts expire after five minutes to avoid replaying an old notification backlog. Messages received before browser enrollment are not replayed. Read messages, expired alerts, and records outside the current user’s access or chosen audience are skipped. Message history remains available in the inbox; alert expiry does not delete chats.

How do I clean up Web Push activity?

Use Settings -> Tools -> How Long To Keep Data -> Web Push activity. Retention defaults to 1 day and supports 1-30 days. Preview Cleanup is read-only; Clean Up Now applies the saved cleanup rules. Eligible completed notification records and expired disabled enrollments are removed while active enrollments, pending deliveries, recent deduplication records, and push keys are preserved. Automatic cleanup uses the existing master switch and schedule. Clean Everything also includes other cleanup targets, such as message activity; it is not a Web Push-only action.

Do notifications stop after logout?

Yes, sends stop for the matching WordPress login session, while other signed-in browsers remain independent. Session expiry, remote session destruction, loss of permissions, and plugin deactivation also stop new sends. A new login must explicitly enable notifications again. Already submitted notifications may still arrive or remain visible; clearing cookies without a server-side logout cannot immediately revoke an existing server session. Standard WordPress server-side session storage is required.

Is NXT Cloud Chat an official WhatsApp Cloud API plugin for WordPress?

NXT Cloud Chat connects WordPress with the official WhatsApp Business Platform / WhatsApp Cloud API provided by Meta.

Do I need a Meta developer account?

Yes. You need a Meta developer account and a WhatsApp Cloud API app to get your App ID, App Secret, Business / Messaging Account ID, Phone Number ID, and Access Token. The documentation explains the setup process.

Do I need to pay NXT Cloud Chat per WhatsApp message?

No. NXT Cloud Chat does not charge per message. WhatsApp Cloud API conversation or messaging charges, if applicable, are charged by Meta according to Meta’s pricing policy.

Is my data stored on a third-party SaaS server?

No. Your plugin data, contacts, messages, CRM records, deals, tags, groups, settings, and activity history are stored inside your own WordPress database. WhatsApp messages are still sent through Meta’s official WhatsApp Cloud API because that is required to deliver WhatsApp messages.

Can I use NXT Cloud Chat for small, medium, and large businesses?

Yes. NXT Cloud Chat is suitable for small businesses, growing teams, medium businesses, agencies, and larger organisations that want a WordPress-native WhatsApp CRM, shared inbox, team access, and automation system.

Can WhatsApp verification help reduce returns or RTO?

Yes, it can help reduce avoidable returns and return-to-origin risk by verifying the customer’s WhatsApp number, improving customer reachability, and enabling COD confirmation messages. Results depend on your store process, shipping workflow, and customer communication policy.

Can I use only WhatsApp OTP login without using the CRM inbox?

Yes. You can configure WhatsApp Cloud API credentials, create a login page with [nxtcc_login_whatsapp], and use WhatsApp OTP login without actively using the inbox, deals, or CRM modules.

Does the plugin support WooCommerce My Account login?

Yes. You can enable a WhatsApp login button on the WooCommerce My Account login page from the Authentication settings screen.

Can customers log in without a password?

Yes. Customers can log in using a WhatsApp one-time password. After verification, their WordPress user account is linked to their WhatsApp number.

Can I manage WhatsApp messages from WordPress admin?

Yes. The Chat Window works as a WordPress admin WhatsApp inbox where you can view conversations, reply to messages, manage tickets, assign conversations, view contact profiles, and check message history.

Does NXT Cloud Chat include a CRM?

Yes. It includes CRM contacts, lifecycle stages, tags, groups, contact ownership, follow-up tasks, duplicate detection, contact profile, activity timeline, deals, pipelines, and team access controls.

Can I track sales pipelines and deals in the free plugin?

Yes. Sales pipelines, deal stages, deal management, line items, deal values, stage-transition history, and CRM activity history are included in the free plugin. Some advanced reporting and external line-item sources may require Pro or compatible integrations.

Can I send bulk WhatsApp messages?

Yes, with Pro broadcasts using approved WhatsApp templates. You must follow Meta’s WhatsApp Business policies and only message contacts where you have proper permission or opt-in.

Can I use WhatsApp templates with buttons and placeholders?

Yes. Pro supports approved WhatsApp templates with dynamic placeholders, CTA buttons, quick replies, image headers, and coupon codes where supported by Meta template rules.

Does NXT Cloud Chat support team members?

Yes. Team Access lets you assign module permissions, action levels, record scopes, and assignment eligibility for different WordPress users.

Can I assign chats and contacts to team members?

Yes. Contacts and conversation tickets can be assigned manually or through routing systems such as round-robin and least-busy assignment.

Does the plugin support SLA tracking?

Yes. Conversation tickets can track priority-based first-response and resolution SLA targets, and overdue tickets can be filtered in the inbox.

Can developers extend NXT Cloud Chat?

Yes. The plugin includes hooks, filters, DAO helpers, runtime wrappers, integration contracts, and extension points for developers and compatible add-ons.

Will my WhatsApp access token be exposed to visitors?

No. API credentials are used server-side and are not printed into public JavaScript or public pages.

Does the plugin verify webhook signatures?

Yes. Incoming webhook payloads can be verified using App Secret-based X-Hub-Signature-256 validation.

Can sensitive template variables be hidden from agents?

Yes. With Pro 1.2.0, Send Template parameters can be hidden from every Chat Window user without changing the customer’s message. License-key tokens are protected automatically. This applies to new sends only, not older history or sensitive text received from customers. Workflow configuration and direct database access are outside this privacy boundary.

What do the chat-list source icons filter?

Broadcast, Workflow, System, and Integration icons filter chats by their latest message source. Green shows a source; gray hides it. All sources start enabled, and Unread-only starts off. Choices are remembered in this browser per user and tenant. These controls filter the list only; they do not delete messages or close the selected chat.

Why can a chat remain visible when its source is hidden?

Chats with unread incoming messages remain eligible so customer replies are not missed. Incoming, manual, and unknown-source chats are not hidden by the automated-source icons. Search, ticket filters, and access permissions still apply; Unread-only narrows results to chats with unread incoming messages.

Where are WhatsApp messages stored?

Inbound and outbound WhatsApp messages, statuses, reactions, reply context, and related history are stored in custom database tables inside your WordPress installation.

What happens when I uninstall the plugin?

If you enable Delete all data on uninstall before uninstalling, the plugin removes its custom database tables, options, transients, scheduled events, and upload directories. This action is irreversible, so use it carefully.

Where can I upgrade to Pro?

You can upgrade from the plugin website: Upgrade to NXT Cloud Chat Pro.

Where can I find documentation?

The full documentation is available at NXT Cloud Chat User Guide.

Reviews

Very useful and simple

vincentlin mai 30, 2026
real time whatsapp..

Nice

chilakammagroups mai 18, 2026
Working

Great plugin, truly unlimited

RuthClaire mai 16, 2026
I connected multiple client websites and all those websites are logged in with a single WhatsApp account. Everything works perfectly and it’s very useful for agencies.

Great plugin for whatsapp login

rakeshrathode mai 15, 2026
Very simple, now my website users can login with WhatsApp otp.

Great support and huge cost savings

srinivasraoannam mai 14, 2026
I initially didn’t know how to configure the WhatsApp Cloud API, but the support team helped me with the setup process. I switched from Wati to NXT Cloud Chat and now I’m saving a lot of money. Very happy with this plugin.
Read all 5 reviews

Contributors & Developers

“NXT Cloud Chat – CRM, Inbox & OTP Login” is open source software. The following people have contributed to this plugin.

Contributors
  • NXTWEBSITE

Translate “NXT Cloud Chat – CRM, Inbox & OTP Login” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.2.6

  • Retry Web Push jobs after temporary database read failures instead of treating unknown results as missing messages, recipients, enrollments, or unread counts.
  • Preserve fan-out progress during retries while retaining existing session, tenant, record-access, retry, and alert-expiry checks. No notification is sent while required database reads fail.
  • Keep the Web Push cron schedule available during early bootstrap without loading translations before init; translate its display label during normal initialized requests.
  • Improve Web Push cleanup query construction and Plugin Check compatibility without changing cleanup eligibility, retention settings, or tenant boundaries.
  • Shorten the parsed readme Description and correct Installation subheadings while preserving external-service and privacy disclosures.

1.2.5

  • Added optional session-bound Web Push alerts for new incoming customer messages, independent of Pro and inbox display filters.
  • Added a compact notification bell with per-browser enrollment, assigned/team or all-accessible audiences, shared unread counts, optional short previews, and the plugin logo. Previews are off by default.
  • Added encrypted subscriptions and VAPID keys, strict Google, Microsoft Edge, Mozilla, and Apple push-service endpoint validation, and permission-checked notification links without a site-wide service worker or polling fallback.
  • Added bounded queue processing, retries, per-chat grouping, duplicate suppression, and a five-minute alert lifetime. Newer messages can alert again without replaying older events; explicit tests have distinct notification identities.
  • Revoked matching enrollments on logout and checked session, tenant, audience, and record access before sending. Status reads explain login or connection changes without silently re-enrolling the browser.
  • Added administrator diagnostics for retained test and incoming-message results, queue state, and current-session eligibility. Database failures report unknown results instead of misleading zero counts, without exposing message content or subscription secrets.
  • Integrated Web Push activity with existing retention, read-only preview, manual cleanup, scheduled cleanup, and run summaries. Retention defaults to 1 day and supports 1-30 days without changing existing cleanup settings.
  • Preserved active enrollments, pending deliveries, push keys, tenant boundaries, and recent deduplication evidence during cleanup. Partial database failures retain actual deletion totals and report unknown remaining counts safely.
  • Handled notification permission errors in the preference panel and added a safe new-window fallback when a notification click finds a closed chat tab. Reloads check only the plugin’s owned worker for updates.
  • Raised the whole Free plugin minimum to PHP 8.2, with legacy-readable bootstrap guidance and preservation of existing data on unsupported PHP. Pro 1.2.1 adopts the same PHP requirement; Pro is not required for Web Push.

1.2.4

  • Updated the locally bundled Font Awesome Free library to 7.3.1, including matching webfonts and license notices. Versioned stylesheet and font URLs refresh cached assets without using an external CDN.
  • Updated workflow source icons in the inbox filters and message sender indicators to use the matching project-diagram symbol.

1.2.3

  • Added compact Broadcast, Workflow, System, and Integration source icons below the chat-list ticket filters. All sources start enabled, and each icon can independently hide chats whose latest message has that source.
  • Added an Unread-only filter and protected chats with unread incoming messages from source hiding, while retaining ticket, search, and access-scope restrictions. Incoming, manual, and unknown-source chats remain eligible when Unread-only is off.
  • Applied source and unread filtering in the server query against the actual latest message, with request-local cache separation and invalidation. Message history and the selected chat remain unchanged.
  • Remembered filter choices in browser storage per user and tenant, with safe defaults when storage is unavailable or corrupt, and prevented stale polling responses from replacing newer selections.
  • Simplified filtered-cache invalidation, reused identical Unread-only cache results, removed redundant focus styling and unused response metadata, and kept saved source preferences inactive when their controls are absent.
  • Kept the new filter icons borderless and background-free, removed the icon-row gap, and reduced the inbox header padding to 8px 16px. Existing messages, schema, and Pro 1.2.0 compatibility are unchanged.

1.2.2

  • Added server-side redacted previews for protected workflow template parameters. Masked values and license keys are hidden from every Chat Window user, including administrators, and are not exposed through message history, replies, forwarding, or exports.
  • Added shared Unicode-aware template parameter validation and safe field-length errors for compatible Pro sends.
  • Added runtime capability discovery for template privacy and parameter validation. Use Pro 1.2.0 for workflow masking and order license-key tokens.
  • Privacy applies to newly sent messages only. Existing history and sensitive text received from customers are not retroactively redacted. Workflow configuration and direct database access are outside the Chat Window privacy boundary.

1.2.1

  • Renamed the account identifier label to Business / Messaging Account ID across connection settings, validation messages, team access, and dashboard checks. Saved identifiers and API fields are unchanged.
  • Added inline and server-side digit-only validation for account and phone-number IDs without numeric conversion or silently removing invalid characters.
  • Improved connection diagnostics with readable missing-field errors, Meta error codes and subcodes, and explicit failures for invalid JSON responses.
  • Prevented overlapping webhook-token generation requests and stale token responses after account changes, preserved the current webhook setting during completion, and displayed server failure details and translated Meta error labels.
  • Removed an unused private Team Access helper and redundant connection dependency includes while preserving public integrations and tenant-scoped behavior.

1.2.0

  • Prevented late or out-of-order WhatsApp receipts from downgrading confirmed Delivered or Read status; late acceptance no longer erases a recorded failure.
  • Preserved the earliest valid receipt timestamps and cleared stale failure text when delivery or reading is confirmed.
  • Added bounded compare-and-swap retries so concurrent receipt updates preserve status and audit evidence.
  • Return HTTP 503 with Retry-After when webhook database reads or writes fail, instead of acknowledging unpersisted events. Redelivered batches retain inbound-message deduplication.
  • Serialized inbound deduplication and contact writes with a per-phone database advisory lock, preventing overlapping callbacks from creating duplicate messages or automation events. Busy or unavailable locks request redelivery without changing existing records.
  • Notify status listeners only after a successful history update and include the resolved history outcome alongside the incoming receipt status.
  • Recommended alongside Pro 1.1.8 for separate workflow execution and message delivery reporting.

1.1.9

  • Recorded new ticket creation as a distinct New ticket created activity instead of a ticket status change, in chat and ticket timelines.
  • Create/Get Ticket now reuses only active tickets and creates a new ticket when all previous tickets are resolved or closed. Incoming messages no longer reopen completed tickets; explicit reopening and snoozed-ticket wake-up remain available.
  • Added unique incoming-message agent views and a paginated Viewed by list, including your own first view, entirely in Free.
  • Counted only messages visibly observed in the focused chat; polling, offscreen messages, and hidden tabs do not create views. Shared inbox unread flags now update only for observed messages.
  • Retried failed unread updates without duplicating agent views or changing first-view times, and respected WordPress’s disabled-avatar setting in the viewer list.
  • Added a dedicated tenant-scoped message-view table and read-only integration wrappers. Existing WhatsApp read timestamps and historical read flags are preserved without backfilling agent identities.
  • Stopped automatic ticket creation when messages arrive, messages are sent, or chats and media are opened. Existing tickets and their activity are preserved.
  • Added a clear No tickets selector state; New Ticket opens the existing panel form for explicit creation.
  • Kept authorized ticket-free chats visible in the default inbox while ticket-specific filters match existing tickets only.
  • Added compact sender avatars for other agents and source icons for workflow, broadcast, system, and integration messages, with name/source tooltips.
  • Preserved ticket and contact assignment access rules for chat, activity, and media requests without creating tickets during authorization.
  • Removed unused private helpers, cache constants, and obsolete inbox assignment metadata; consolidated duplicate ticket nonce checks in the shared authorization guard without changing public integration wrappers.
  • Recommended alongside Pro 1.1.7 for explicit workflow ticket handling and the ticket.message template-variable fix.

1.1.8

  • Added compact multi-select Assignment, Status, and Priority inbox filters, including Following, with permission-aware matching on the same ticket.
  • Fixed overdue ticket matching to exclude resolved and closed tickets and protected filter results from stale requests.
  • Added compact status and priority counts, followed-ticket highlighting, ticket links in chat activities, and a header ticket count that excludes closed and unassigned tickets.
  • Reordered the ticket panel and added a persistent Issue field, required for new panel-created tickets while keeping existing tickets compatible.
  • Changed internal notes to author-only Private Notes across activity readers and timelines. Existing notes without an identifiable author are hidden; handoff notes remain shared with authorized handlers.
  • Prefilled each ticket’s latest own private note and prevented unchanged note text from being appended again.
  • Added ticket text limits and editing counters, with matching server validation, Unicode-safe note storage, and preservation of unchanged older text.
  • Limits: Issue and Private Note 5,000 characters; Handoff Note 2,000; Reason 191; customer Message 4,096. Pro 1.1.6 adds matching workflow validation.
  • Kept new workflow-generated team notes visible to authorized ticket handlers without exposing personal private notes or older unattributed notes.
  • Allowed new tickets to be saved without a customer message. Save & Send now checks required fields, permissions, message content, and reply-window expiry, with a hover/focus tooltip and duplicate-submit protection.
  • Corrected UTC reply-window checks and preserved saved tickets when direct message delivery fails.
  • Fixed actor lookup for WordPress user rows so manual activities show the recorded user’s name, automated actions show their source, and missing actors are not guessed.

1.1.7

  • Fixed bold, italic, strikethrough, and inline code formatting in chat messages and media captions using the shared safe text renderer.
  • Added formatting to chat-list previews while preserving the 40-character visible-text limit and Unicode characters.
  • Improved chat script cache refresh so updated rendering loads without waiting for a plugin version change.
  • Removed duplicate formatting helpers and unreachable message-rendering code.

1.1.6

  • Tested compatibility with WordPress 7.1.2.
  • Clarified COD workflow guidance for authentication verification, payment methods, and WooCommerce order statuses.
  • Removed legacy authentication policy files; settings continue to use the existing shared authentication handler.

1.1.5

  • Added a Support settings tab with a tenant-owner toggle for showing or hiding the admin support badge.
  • Improved the Chat Window empty state when the connection is invalid, including a direct settings link.
  • Added public authentication verification wrappers for integrations that need to require NXT Cloud Chat verification before protected actions.

1.1.4

  • Added multiple conversation tickets per contact with an explicitly selected current ticket.
  • Added tenant-managed ticket categories with safe archive behavior for referenced categories.
  • Redesigned the Chat Window ticket panel for ticket switching and in-panel ticket creation.
  • Added unified ticket saving for details, SLA dates, assignment, handoff notes, and internal notes.
  • Made the ticket panel the single Chat Window assignment surface and require a member or Access Team for manual ticket saves.
  • Linked inbound, direct session, and workflow template messages to their ticket context.
  • Added {{ticket.message}} for immutable customer-message use in Ticket Created and Ticket Details Changed workflows.
  • Added public multi-ticket and ticket-category wrappers for external integrations.

1.1.3

  • Added normalized inbound button, list, and Flow response rendering in the Chat Window.
  • Added sent-template message previews in chat without requiring the Pro plugin at display time.
  • Added optional verified-login enforcement for Cash on Delivery checkout orders.
  • Hardened public template and interactive-message payload parsing with bounded JSON and scalar-only parameter handling.
  • Removed an unused duplicate authentication policy controller.

1.1.2

  • Added an NXT Floating Chat add-on card to the Upgrade page alongside NXT Cloud Chat Pro.
  • Added install, activate, and activated states for the NXT Floating Chat card.
  • Updated the NXT Floating Chat card to use the dedicated add-on logo.

1.1.1

  • Added credential-free public wrappers for listing configured tenant profiles and resolving an exact tenant profile.
  • Added nxtcc_get_primary_display_phone_number() for safely reading the primary connection’s digits-only display phone number.
  • Published runtime capability discovery for the new connection-profile readers.
  • Fixed connection-profile and credential caches remaining stale after connection settings were updated.

1.1.0

  • Added a secure Pro Dashboard aggregate CRM and automation CSV export powered by the shared Free-owned analytics contract.
  • Added personal tenant-scoped saved Contact views with a compact selector, default views, secure allowlisted filters, and stable integration wrappers.
  • Added a Free-owned aggregate CRM analytics contract for contact health, current workload, tasks, response and resolution time, SLA compliance, lifecycle and tag distributions, and currency-safe deal reporting.
  • Redesigned Deals with route-backed Pipelines and Deals views, compact scrollable management modals, live external-source line-item search, integer quantities, deal deletion, stage preview/reordering, duplication, and guarded archive/delete behavior.
  • Added configurable per-stage reason requirements and authoritative deal stage-transition history.
  • Added manual and calculated deal values plus extensible line items with Manual, WooCommerce, Houzez, and external provider support.
  • Added a bounded Free-owned line-item provider contract with stable discovery, search, resolve, pipeline lifecycle, and management wrappers.
  • Added Free-owned sales pipelines, stages, manual deal management, contact and line-item links, ownership, expected close dates, stage reasons, and deal activity history.
  • Added stable tenant-scoped pipeline/deal wrappers, hooks, capabilities, and CRM deal access-policy checks for Pro and external integrations.
  • Added a shared allowlisted, tenant-scoped contact query runtime for secure dynamic segment and external integration use.
  • Added a locked Segments Pro menu entry and documented the shared contact-query and Pro segment integration contracts.
  • Added a bounded contact-query provider contract so Pro and compatible external plugins can register validated, indexed segment properties.
  • Added tenant-scoped CRM lifecycle stages, follow-up tasks, strong duplicate suggestions, and guarded contact merging.
  • Added stable lifecycle, task, duplicate-reader, and contact-merge runtime wrappers for Pro and external integrations.
  • Expanded the shared Contact Profile with lifecycle controls, follow-up tasks, and confirmed duplicate merging.
  • Added tenant-scoped contact tags with a dedicated Tags screen, contact filters, manual and bulk assignment, import defaults, and export support.
  • Added stable Free runtime wrappers, capabilities, and hooks for secure external contact-tag integrations.
  • Added tenant-scoped contact and chat ownership assignments with manual Contacts and Inbox controls, filtering, bulk updates, and audit history.
  • Added stable assignment wrappers and capability discovery for compatible add-ons and external plugin integrations.
  • Added concurrency-safe round-robin contact assignment with tenant-role pools, stable route keys, and existing-owner protection.
  • Added a tenant-scoped CRM activity timeline foundation with bounded readers, secure writers, automatic contact audit entries, and retention cleanup controls.
  • Added a tenant-safe read-only Contact Profile available from Contacts and the Chat Window, including contact details, ownership, message context, and permission-checked CRM activity history.
  • Added tenant-editable Access Teams with view-only/manage action levels, assigned/team/all record scopes, and assignment eligibility.
  • Added centralized CRM access-policy enforcement across Contacts, Inbox, bulk actions, imports, exports, forwarding, and secure media access.
  • Added stable CRM access-policy wrappers and Access Teams discovery for Pro modules and external plugin integrations.
  • Added independent conversation ticket management with saved Inbox views, status, priority, subject, category, snoozing, followers, internal notes, and required-note handoffs.
  • Added tenant-scoped conversation, assignment-history, and watcher tables with bulk Inbox loading and permanent-contact cleanup.
  • Added stable conversation ticket wrappers, activity readers, access checks, and lifecycle hooks.
  • Added a stable conversation auto-assignment wrapper with tenant-safe round-robin and least-busy routing through existing assignment pools.
  • Added a bounded tenant-scoped SLA candidate reader for efficient Pro deadline catch-up scheduling.
  • Added priority-based first-response and resolution SLA targets with WordPress-timezone due dates, overdue Inbox filtering, and a developer customization filter.
  • Fixed Deals stage-history timestamps and release-facing admin timestamp fallbacks to display in the WordPress site timezone.
  • Confirmed the uninstall cleanup catalog covers all Free and Pro 1.1.0 database tables.

1.0.9

  • Redesigned the Free dashboard with compact Pro-style cards for Connection, Messaging and Calling Health Status, and setup help links.
  • Added dashboard setup-help links from the existing support badge helper.
  • Improved the Messaging and Calling Health Status UI by hiding internal Meta node IDs while preserving the backend health payload.
  • Cleaned unused dashboard response fields and UI code after the dashboard redesign.

1.0.8

  • Added a shared contact upsert runtime wrapper for compatible integrations and add-ons.
  • Added the contact integration writer capability to the Free runtime contract.
  • Added Pro feature menu entries with compact Pro badges that open the existing upgrade page when Pro is not installed or the Pro license is inactive.
  • Updated Free plugin documentation for Pro abandoned cart recovery, workflow subscription-status checks, and Pro upgrade entry points.

1.0.7

  • Added a shared runtime wrapper so compatible add-ons can update contact subscription status safely.
  • Routed contact bulk subscribe and unsubscribe actions through the shared tenant-scoped subscription runtime.

1.0.6

  • Officially tested and validated compatibility with WordPress 7.0.

1.0.5

  • Added a floating Support Portal badge across eligible NXT Cloud Chat admin pages in Free and Pro contexts.
  • Improved the support badge UX with expandable and icon-only collapsed states.

1.0.4

  • Improved WordPress 6.7+ compatibility by refining translation-loading timing and cleanup catalog text handling.
  • Cleaned up i18n and PCP-related warnings in the Free plugin codebase for a more release-ready build.
  • Updated the dashboard upgrade call-to-action to point directly to the NXT Cloud Chat product page.

1.0.3

  • Added Team Access management for tenant-owner controlled staff permissions inside the plugin.
  • Redesigned the Connection settings tab with a more compact branded layout while keeping the existing functionality intact.
  • Added cleanup and retention controls for operational data from the plugin.
  • Refined Contacts, Groups, History, and Chat Window behavior, including verified-group protections and improved live chat handling.
  • Removed development-only debug traces from Contacts admin scripts for a cleaner production build.

1.0.2

  • Added the stable runtime compatibility contract and bridge wrappers used by the Pro workflow engine.
  • Added additive inbound-message, message-status, and authentication lifecycle hooks for internal integrations.
  • Improved release compatibility for the Pro add-on workflow runtime.

1.0.1

  • Added WhatsApp login button support for the default WordPress login page and WooCommerce login page.
  • Added customizable login button appearance controls.
  • Improved dedicated login page and login widget behavior.
  • Refined readme content and listing metadata.

1.0.0

  • Initial public release of NXT Cloud Chat.
  • Core WhatsApp Cloud API integration.
  • Chat Window, Contacts, Groups, Message History, and Dashboard.
  • Webhook handling with verify-token helper.
  • WhatsApp-based login/authentication widget for WordPress users.

Meta

  • Version 1.2.6
  • Last updated 3 dagar ago
  • Active installations 30+
  • WordPress version 6.4 or higher
  • Tested up to 7.1.3
  • PHP version 8.2 or higher
  • Language
    English (US)
  • Tags
    crmloginwhatsappwhatsapp businesswoocommerce
  • Advanced View

Ratings

5 out of 5 stars.
  • 5 5-star reviews 5 stars 5
  • 0 4-star reviews 4 stars 0
  • 0 3-star reviews 3 stars 0
  • 0 2-star reviews 2 stars 0
  • 0 1-star reviews 1 star 0

Your review

See all reviews

Contributors

  • NXTWEBSITE

Support

Got something to say? Need help?

View support forum

  • About
  • News
  • Hosting
  • Privacy
  • Showcase
  • Themes
  • Plugins
  • Patterns
  • Learn
  • Support
  • Developers
  • WordPress.tv ↗
  • Get Involved
  • Events
  • Donate ↗
  • Swag ↗
  • WordPress.com ↗
  • Matt ↗
  • bbPress ↗
  • BuddyPress ↗
WordPress.org

Faroese

The WordPress® trademark is the intellectual property of the WordPress Foundation.

  • Visit our X (formerly Twitter) account
  • Visit our Bluesky account
  • Visit our Mastodon account
  • Visit our Threads account
  • Visit our Facebook page
  • Visit our Instagram account
  • Visit our LinkedIn account
  • Visit our TikTok account
  • Visit our YouTube channel
  • Visit our Tumblr account
Code is Poetry.