Priestdev Customer Chat

Descrição

Priestdev Customer Chat connects your WordPress website to the BoxlyHQ customer communication platform so you can manage live chat, support conversations, and customer messaging from a single SaaS dashboard.

This plugin is designed for businesses that want a branded, robust chat experience without the complexity of maintaining their own messaging backend. Once connected, the Priestdev Customer Chat widget can be activated on your site and managed from your BoxlyHQ workspace.

Features

• Connect a WordPress site to the BoxlyHQ SaaS platform.
• Load the Priestdev Customer Chat live chat widget on the front end.
• Provide a shortcode-based chat experience when needed.
• Sync WordPress user context with the BoxlyHQ system.
• Manage widget and support settings from the BoxlyHQ dashboard.
• Review chat sessions from the WordPress admin interface.

External Services

This plugin connects to BoxlyHQ’s online services to provide the Priestdev Customer Chat widget, customer communication, support conversations, connection management, and related integration features. The plugin does not provide an independent messaging backend; the relevant features require communication with BoxlyHQ’s service.

BoxlyHQ online service

Service: BoxlyHQ API and online services at https://api.boxlyhq.com.

What it does: BoxlyHQ’s service provides site connection and authentication workflows, widget configuration, customer and visitor communication, conversation synchronization, chat-session management, notifications, and related support functionality.

Why the plugin connects: The plugin communicates with BoxlyHQ so a site owner can connect the WordPress site to a BoxlyHQ workspace, load and configure the Priestdev Customer Chat widget, create or retrieve support conversations, and send and receive messages through the BoxlyHQ dashboard.

Information that may be transmitted: Depending on the feature enabled and used, the plugin may transmit the WordPress site’s URL, BoxlyHQ connection and workspace information, WordPress user details for an authenticated user such as user ID, username, name, email address, and avatar URL, widget configuration, visitor or customer-provided information, conversation content, message metadata, product or order context, chat-session identifiers, and file or media metadata when supported by the connected BoxlyHQ service.

When transmission occurs: Communication occurs when an administrator connects, verifies, refreshes, or disconnects the site; when the widget is loaded or its settings are retrieved; when a visitor or customer opens or uses the chat; when a user authenticates through the integration; when a product or order support session is created; and when messages or conversation status updates are sent or received. Some widget connection checks may occur periodically while the connected widget is active.

The plugin communicates with this service only when the integration is configured or when a visitor, customer, administrator, or authorised WordPress user uses the relevant Priestdev Customer Chat feature. Information is used to provide the requested functionality and is handled according to the BoxlyHQ Privacy Policy and Terms of Service.

Privacy Policy: https://boxlyhq.com/privacy-policy
Terms of Service: https://boxlyhq.com/terms

Priestdev Customer Chat widget and real-time messaging

The plugin may load the Priestdev Customer Chat widget script from BoxlyHQ’s online service when the site is connected. This script is used to display and operate the front-end chat experience. It may transmit the information described in the BoxlyHQ online service section when the widget loads, retrieves its configuration, creates a conversation, or sends and receives chat messages.

Real-time chat uses the BoxlyHQ service’s real-time messaging connection. The plugin includes its Socket.IO client library locally in the plugin package; it is not loaded from a third-party CDN. The locally bundled library connects to BoxlyHQ only when the chat widget or shortcode chat is active and real-time communication is required. The connection may transmit authentication, conversation, visitor presence, message, and conversation-room data needed to deliver the chat experience.

WordPress and WooCommerce context

The plugin uses WordPress’s local REST API for browser-to-plugin requests and may send relevant context to BoxlyHQ when a connected feature requires it. When product or order chat is used, the plugin may transmit the relevant product or order identifier and limited context needed to create a support conversation. The plugin does not automatically transmit all WordPress or WooCommerce data; transmission depends on the feature used and the information required by the configured BoxlyHQ workflow.

Files, media, and avatars

Where the connected BoxlyHQ feature supports attachments, avatars, or other media, related file or media metadata and the content selected by the user may be transmitted to BoxlyHQ’s online services for communication and display. The plugin may also provide the avatar URL associated with an authenticated WordPress user when that user is synchronised with BoxlyHQ. These transfers occur only when the related account, chat, or media feature is used.

Payment, email, analytics, and telemetry

The WordPress plugin does not directly connect to a payment processor, email delivery provider, analytics service, advertising network, or telemetry service. Subscription billing and transactional email may be features of the separate BoxlyHQ platform, but this plugin does not independently call those providers. The plugin also does not load an external analytics or advertising script.

External assets and dependencies

The plugin’s chat CSS, chat application, administration scripts, and Socket.IO client are packaged with the plugin. The connected Priestdev Customer Chat widget script is loaded from BoxlyHQ’s online service when the integration requires it. No third-party CDN-hosted JavaScript dependency is required by the packaged chat application.