內容簡介
ChatJox 是一款自我託管的即時聊天與客戶支援外掛，讓網站訪客透過響應式聊天小工具開始對話，網站管理員則可在 WordPress 控制台中管理訊息。此外掛不需註冊帳號或付費，所有聊天訊息均儲存在網站上。
【主要功能】
• 響應式即時聊天，支援桌面與行動裝置
• 控制台內的操作員收件箱
• 自訂工作時間與自動回覆
• 可上傳檔案，並設定大小與副檔名限制
• 客戶滿意度評分與報告統計
外掛標籤
開發者團隊
② 後台搜尋「ChatJox – چت آنلاین و پشتیبانی」→ 直接安裝（推薦）
原文外掛簡介
ChatJox is a self-hosted live chat and customer support plugin for WordPress. It lets site visitors start conversations from a responsive chat widget while site administrators manage messages from an operator inbox inside the WordPress dashboard.
Chat messages are stored on the WordPress site. ChatJox does not require a ChatJox account, license key, paid activation, trial period, or external ChatJox service.
Live chat and operator inbox
Responsive live chat for desktop, Android and iOS.
Operator inbox inside the WordPress dashboard.
Search, open, close, archive and delete conversations.
Clickable URLs inside messages.
File uploads with configurable size and extension limits.
Optional visitor name, email and mobile-number collection before a conversation starts.
Local contact archive for unique email addresses and mobile numbers.
Working hours and automated replies
Scheduled working hours with configurable working days, start and end times, and overnight shifts.
Manual always-online and always-offline modes.
Keyword-based automated replies with per-rule enable/disable controls.
Configurable quick replies for visitors.
RTL, Persian and mobile support
RTL-first interface suitable for Persian websites.
Responsive desktop and mobile layouts.
Full-screen mobile mode.
iOS Visual Viewport and Safe Area handling.
Persian-oriented typography choices for Vazirmatn, Estedad and Shabnam when those fonts are available locally or supplied by the active site or theme.
No mandatory external font CDN.
Appearance and floating contact menu
Custom desktop and mobile chat dimensions.
Detailed colors for header, messages, composer, launcher, badge, quick replies and action menu.
Configurable typography, bubble radius, input radius and shadows.
Launcher position, desktop/mobile size, shape, animation, label mode, colors, preset icon, emoji or uploaded image.
Optional floating contact menu for live chat, phone, WhatsApp, Telegram, Rubika and custom links.
Icon, compact and card menu layouts.
Per-channel title, description, color and ordering.
Optional prefilled WhatsApp text.
Optional advanced support modules
Version 0.0.5 adds an opt-in advanced support center. Every module has its own ON/OFF switch and is disabled by default on existing installations so the established 0.0.4 behavior is preserved until an administrator enables a module.
Multi-operator inbox using selected WordPress users, with per-operator reply and assignment permissions.
Operator presence with automatic Online/Offline detection plus manual Online, Away and Offline modes.
Departments and visitor department selection, plus operator/department assignment and transfer controls.
Browser/Desktop notifications with sound and an unread badge, using the browser Notification API without an external notification service.
Faster adaptive real-time polling with reconnect/backoff behavior; no external WebSocket service is required.
Optional typing indicators and Delivered/Seen message states.
Customer context with current/start/referrer pages, device information, last activity and related conversation history.
Timed consultations with start, extend, stop and expiry status.
Operator audit logging for supported actions.
Read-only compatibility center for WordPress/PHP/HTTPS/REST/Upload/WP-Cron checks.
Version 0.0.7 modules
Version 0.0.7 adds five further opt-in modules. Every one of them is switched OFF after an upgrade, so an existing site behaves exactly as it did on 0.0.6 until an administrator turns a module on. While a module is off, none of its assets, polling, queries or admin screens are loaded.
Customer satisfaction rating (CSAT): after an operator closes a conversation the widget can ask for a 1-5 star rating and an optional comment. One rating per conversation, shown in the operator panel and in reports.
Reports and statistics: a dedicated screen with conversation, response, resolution and satisfaction KPIs, a per-day table and a sortable operator table. Statistics are calculated only when that screen is opened and are never queried from the chat widget or the inbox poll.
Conversation transcript: a responsive HTML copy of a conversation can be emailed to the visitor with wp_mail(), with a configurable per-conversation send limit. Conversation tokens, log data and IP addresses are never included.
Block list and anti-spam: a persistent block list plus message flood, repeated message, link flood, session flood, file flood, honeypot and minimum form time checks, layered on top of the existing rate limiting. Sensitive identifiers are stored as an irreversible hash. Permanent blocks are only ever created manually.
Duplicate conversation merge: related conversations of the same customer are suggested from an exact email, an exact mobile number or a WordPress user id, never from an IP address. Merging is non-destructive: the secondary conversation and all of its data are kept, an old visitor token keeps working and resolves to the canonical conversation.
Each module’s own options live on the Advanced Features screen next to its switch, so no extra settings menu is added.
Optional Telegram replies
Telegram integration is disabled by default. When explicitly enabled and configured by the site administrator, ChatJox can send visitor messages and uploaded-file links to a Telegram bot and receive administrator replies from Telegram.
Text and file metadata can be delivered as one Telegram notification where supported by the current workflow.
Performance and cleanup
Lazy loading where applicable.
Adaptive polling and hidden-tab suspension by default; when Browser Notifications are enabled, the operator inbox uses a low-frequency background check so permitted notifications can still appear while the tab remains open.
Selective cleanup for chats, files and logs.
No artificial feature gating, usage quotas or license checks.
External services
ChatJox works without any external ChatJox service. It contacts an external service only when the site administrator explicitly enables and configures the Telegram integration.
Telegram Bot API
When Telegram integration is enabled, ChatJox communicates with the Telegram Bot API at api.telegram.org to register a webhook, validate the configured bot, deliver visitor messages and uploaded-file links to the connected administrator chat, and receive administrator replies.
Data that may be sent to Telegram when this optional integration is enabled includes the visitor display name, conversation ID, message text, uploaded-file URL and file name, plus the administrator bot/chat identifiers required for message delivery. The plugin does not enable this connection by default.
Telegram Terms of Service: https://telegram.org/tos
Telegram Privacy Policy: https://telegram.org/privacy
Telegram Bot API documentation: https://core.telegram.org/bots/api
The optional WhatsApp, Telegram and Rubika contact buttons are ordinary administrator-configured links. ChatJox does not call those services merely by displaying the buttons; a visitor chooses whether to open a configured link.
Privacy
ChatJox can store chat messages, uploaded files, visitor IP addresses and browser user-agent strings on the WordPress site. Depending on administrator settings, it can also collect visitor names, email addresses and mobile numbers.
When email or mobile collection is enabled, unique email addresses and mobile numbers are additionally retained in a separate ChatJox contact-archive table in the local WordPress database. Normal chat cleanup does not remove this archive. If the administrator disables the plugin’s keep-data option before uninstalling ChatJox, the archive table is removed together with the other ChatJox tables.
ChatJox also adds suggested privacy-policy text to WordPress Privacy settings so site owners can adapt it to their site and jurisdiction. Version 0.0.5 integrates ChatJox conversation data with the WordPress personal-data Export and Erase tools for email-based requests.
If Telegram integration is enabled, see the External services section above for information about data sent to Telegram.
