Communication + Support — Built Into WordPress

WordPress Customer Messaging Platform

Threaded conversations, a full support ticket system, and a front-end customer inbox — all inside your WordPress dashboard. No third-party chat tool required.

4 Database Tables Purpose-built for performancenThreaded Context | Conversations tied to any objectn8 Participant Roles | Customer to admin — all coverednZero Third-Party APIs | Your data stays on your server

Stop Duct-Taping Your Customer Communication

Most small businesses piece together a support inbox, a chat tool, and a help desk — none of which talk to each other, and none of which live where your business actually runs. Messaging Hub brings threaded customer conversations and a structured support ticket system directly into WordPress, so your team and your customers communicate in one place.

Everything You Need to Run Customer Communication

Six core capabilities built into a single WordPress module.

Threaded Messaging

Context-Bound Conversations

Every thread is tied to a specific record — an order, a project, a property, or any custom object. Replies stay organized by context, not by inbox chaos.nSupport Tickets

Full Ticket Lifecycle

A Support Ticket System That Already Knows Your Data

Most help desk tools are disconnected from your actual business records. Messaging Hub threads are bound to context — meaning a ticket about Order #4821 actually knows it is about Order #4821. Your team sees the full picture without copying and pasting information between tabs.

Ticket System Capabilities

  • Auto-incrementing ticket numbers for easy referencenFour status levels: open, pending, waiting for customer, closednThree priority tiers: low, normal, high, urgentnAssign tickets to any team member with due date trackingnTicket statistics dashboard: total, open, unassigned, overdue, and your open countnQuick actions: Assign to me, Mark waiting, Close ticket, Reopen

Participant and Role System

  • Eight built-in participant roles: customer, tech, office, admin, staff, manager, and morenAdd participants by email address, WordPress username, or user IDnNew email addresses auto-provision a WordPress user accountnPer-participant read state tracked in real timenProfile-based thread filtering for multi-account and multi-property setupsnExtensible role and permission system via WordPress filters

The Front-End Inbox Your Customers Will Actually Use

Drop the [luperiq_messaging_hub_inbox] shortcode on any page and your customers get a polished inbox — thread list with subject lines, context labels, unread badges, last message previews, and timestamps. No custom theme required. No separate portal to build.

Front-End and Authentication Shortcodes

Three shortcodes cover the full customer-facing experience.

[luperiq_messaging_hub_inbox]

Renders a paginated thread list for the logged-in customer. Configure limit, page title, and whether to show a new ticket form.n

[luperiq_login_form]

Designed for Teams That Work in WordPress

Messaging Hub does not replace your website with a help desk SaaS. It extends WordPress into a customer communication platform — keeping your data on your server, your staff in familiar territory, and your customers in a branded experience you control.

Who Uses Messaging Hub

  • Service businesses managing job-site communication with clients and field techniciansnAgencies running client portals where customers check project status and ask questionsnE-commerce stores handling order questions and post-purchase support without leaving WordPressnProperty managers linking conversations to specific units or lease recordsnAny team that needs structured internal and external communication tied to real business records

What You Stop Paying For

  • Separate help desk SaaS subscriptions with per-agent pricingnThird-party customer chat widgets that load external scriptsnCustom portal development just to show customers their conversation historynManual thread tracking in shared email inboxesnCopying customer context between your CRM and your support tool

Related Email Modules

Email SMTP Delivery

Reliable delivery with retry logic and full logging.

Explore the full feature set and integration details.

View Module

Frequently Asked Questions

Does Messaging Hub send email notifications to customers?

No. Messaging Hub is a visual communication system. Unread counts appear in the WordPress admin toolbar, in the front-end sticky bar, and as inbox badges. If you want outbound email notifications, pair it with the LuperIQ Email Automations module.nCan customers use the inbox without an admin account? | Yes. Customers log in through the front-end login form (or any WordPress login). The inbox shortcode shows only the threads they participate in. They never see wp-admin or other customers' conversations.nHow are threads linked to orders or other records? | Threads are bound to a context_type and context_id pair — for example, type=order and id=4821. Other LuperIQ modules provide context hooks, and the system exposes 25+ WordPress filters so developers can tie threads to any custom object.nWhat happens if I add a participant email that is not a WordPress user? | Messaging Hub automatically creates a WordPress user account for that email address and adds them to the thread. This makes it easy to onboard customers into your portal without a separate registration step.nCan I use this for internal team communication only? | Yes. Threads do not have to be customer-facing. You can create internal threads between staff roles without exposing them in the front-end inbox. The participant role system handles the distinction.nIs there a limit on the number of threads or messages? | No hard limits are imposed by the module. Thread and message data lives in four dedicated database tables (lq_threads, lq_thread_participants, lq_messages, lq_tickets) on your own WordPress database, so capacity is determined by your hosting environment.

Ready to replace your help desk?

Messaging Hub is included in LuperIQ. See the plan that fits your business.

View Pricing