WHMCS.Community

Give your support, billing and technical team a real-time chat inside the WHMCS admin area. Staff Chat adds a floating widget to every admin page, so your team can talk, share files, mention each other and search past conversations without leaving WHMCS or paying for a separate chat tool. It works with ordinary AJAX polling, so there is no daemon, no extra port and no Socket.IO server to install or maintain. Every message travels through WHMCS itself, so nothing needs to be set up on your server beyond the module folder. If your admin area loads, Staff Chat works. The widget sits in the corner of every admin page and can be collapsed into a small launcher with an unread badge, so it stays out of the way until you need it. Your team can chat in a shared Group Chat, open private one-to-one conversations, react to messages, send images and files, and be notified when a colleague mentions them. Built for staff privacy and control Chat conversations often include client details, so Staff Chat is built to keep them protected. Chat history and attachments are encrypted at rest using the WHMCS encryption helpers, and attachments are downloaded only through an authenticated endpoint, never from a public URL. All chat actions are protected against cross-site request forgery. Full Administrators can review everything from a dedicated Chat History page, search across every room, and export results to CSV. A separate activity log records important actions with the admin, IP address and browser, and it never stores the text of a chat message. Owned License ($45.00) - https://www.hardsoftcode.com/cart/link/staff-chat-for-whmcs/owned Source Code License ($320.00) - https://www.hardsoftcode.com/cart/link/staff-chat-for-whmcs/source Why you need it Staff stop switching between WHMCS and an outside chat app. Conversations stay on your own server instead of a third-party service. Chat history and attachments are encrypted at rest. Full Administrators can review, search and export everything. Read-only roles, ghost mode and rate limiting let you control who can say what. Features Chat and rooms Shared Group Chat room for every approved admin Optional private 1:1 rooms between two admins Floating widget on every admin page, with expanded and collapsed launcher modes Online admin list with presence dots and per-room unread badges Configurable polling interval from 1 to 60 seconds Message timestamps and an unread count in the browser title Configurable message length and number of messages loaded per request Automatic retention and a per-room message cap Messages and interactions @mentions with autocomplete, highlighted names and a title marker when you are mentioned Emoji picker with the common chat emojis Reactions with live counts: 👍 ❤️ 😂 🎉 😮 😢 Typing indicator showing which admin is typing Edit your own messages within a configurable time window Delete messages with a confirmation dialog (Full Administrator only) Clickable links that open in a new tab Optional notification sound with a per-admin mute Files, images and links Image and file attachments, one per message Allowed types: JPG, PNG, GIF, WebP, PDF, TXT and ZIP Configurable maximum file size, with a hard ceiling of 50 MB Configurable total attachment storage quota Inline image previews and a full-size lightbox Authenticated downloads, with no public attachment URLs Attachments encrypted at rest Text-only link previews with SSRF protection History, search and export Encrypted chat history that survives page refreshes and admin logins Chat History page with a room selector, sorting, paging and filtering Global search across rooms, admins, message text and attachment names Reaction counts shown next to messages in history and search results Attachment previews and downloads in history and search results CSV export of chat history and of the activity log Retention applied when messages are written, when pages are viewed and by the daily cron Dashboard analytics 30-day message volume line chart Time-of-day chart showing your peak communication hours Group Chat versus private room distribution Top mentioned admins, ranked Attachment count, encrypted storage used and a breakdown by file type KPI cards for 30-day volume, active admins, attachments and peak hour Activity log Records widget connects, room switches, settings changes, message edits and deletions, cleared history, cleared log and denied access attempts Filters by action, admin and date range IP address and browser details, with IP logging switchable Session grouping, CSV export and retention pruning Full Administrator clear action Message content is never written to the log Access and safety Full Administrator-only module pages Read-only roles that can view and react but cannot send Ghost mode: selected admins are hidden from presence and their names are masked Per-admin message rate limiting Blocked words filter and optional link blocking CSRF protection, AJAX-only endpoints and POST-only chat actions Notifications Configurable default sound, volume and sound-on setting Desktop notifications through a service worker Chrome and operating-system permission diagnostics Built-in test notification button Admin area only. Staff Chat has no client-area pages and no client templates, and it works with WHMCS 8.x and 9.x. Changelog Version 2.0.0 Added: Group Chat and private 1:1 rooms Added: AJAX polling with a configurable interval Added: Mentions with autocomplete and highlighting Added: Emoji picker, reactions and typing indicator Added: Message edit window and Full Administrator message deletion with a SweetAlert2 confirmation Added: Encrypted image and file attachments with inline images and a lightbox Added: Text-only link previews with SSRF protections Added: Chat History with room selector, DataTables, attachment previews and CSV export Added: Global search across rooms, admins, message text and attachment names Added: Reaction counts in Chat History and CSV output Added: Activity Log with retention, filters, CSV export, session grouping and a clear action Added: Read-only roles, ghost mode, rate limit, blocked words and link rules Added: Desktop notifications with a service worker and Chrome/OS diagnostics Added: Dashboard analytics with 30-day message volume, time-of-day activity, room distribution, top mentioned admins and attachment storage breakdowns Added: Configurable aggregate attachment quota Updated: Module pages are now Full Administrator-only Updated: Chat history and attachments are now encrypted at rest Updated: Attachments are served only through an authenticated download endpoint, and legacy plaintext files are migrated Improved: Encrypted analytics cache that invalidates automatically, with a Full Administrator-only, CSRF-protected refresh endpoint Improved: Per-admin rate limiting shared across sessions Improved: Anti-framing headers and activity-log integrity events for encrypted data failures  

Hello WHMCS Community, We’re introducing Weeby Studio — a complete WHMCS theme with a visual website builder, custom client area, and matching orderform and checkout, created by Hostk. The idea is simple: give hosting businesses a consistent brand experience and practical control over their website. Your pages, product presentation, customer workspace, and checkout share one design, with a dedicated Studio inside WHMCS to make it your own. Your hosting website. Your brand. Your Studio. Meet the Visual Studio Update your website from a focused visual workspace inside the WHMCS administration area. Edit visually: change website text, images, links, buttons, and supported styling. Build your pages: create or duplicate public pages, add content blocks, and arrange editable sections. Find every detail: navigate page structure through Pages and Layers. Manage your assets: upload images and replace editable visuals. Preview across devices: review desktop, tablet, and mobile layouts. Control shared elements: customize website navigation, headers, footers, and brand settings. Manage on-page SEO: edit browser titles, search descriptions, and image alternative text. Publish when ready: save an unpublished draft, review your changes, then publish. Keep a recovery path: export editable project backups and revisit saved published versions. Everyday content changes can be made in the visual editor, while native WHMCS forms, live prices, permissions, and transactions retain their original behavior. One design, from first visit to checkout Weeby Studio includes three connected parts of your customer experience: 1. Your public website A responsive hosting website with service landing pages, product presentations, comparison sections, and shared navigation. 2. Your client area A branded customer workspace for services, domains, invoices, support tickets, account information, and everyday account tasks. 3. Your orderform A matching product selection, configuration, cart, and checkout experience using native WHMCS ordering. The result is a consistent visual identity as customers move between your website, their account, and their next purchase. 23 starting pages. Room for your own ideas. The included public collection contains 23 pages, including 14 service landing pages, a homepage, service directory, and policy pages. Hosting & compute: Web Hosting, Cloud Hosting, Reseller Hosting, VPS Hosting, Dedicated Servers, and Game Servers. Business & security: Domains, Professional Email, SSL Certificates, and VPN. Expert services: Web Design, Backup & Recovery, Website Migration, and Managed Services. Customize the included content or create additional public pages through the Studio. 12 color palettes + your own brand colors Start with the original Weeby blue, navy, and white identity, choose one of 12 coordinated palettes, or create a custom palette. Set your brand accents, buttons, navigation, headings, text, backgrounds, surfaces, and borders. Customize your logo, typography, content width, and button corners from the shared design controls. Supported bundled visuals and the default favicon follow the selected palette. Your uploaded photos, custom logo, and custom favicon keep their original artwork. Product presentation connected to WHMCS Your real catalog stays central to the website. Connect website plan slots to specific WHMCS products or product groups. Display product names, descriptions, prices, and available billing cycles from WHMCS. Use the currencies and pricing configured in your installation. Customize supported CPU, RAM, storage, transfer, and other resource display labels. Presentation labels remain separate from the actual service specifications and allowances defined in WHMCS. A client area that feels part of your brand The custom client area brings key customer tasks into a coordinated layout: Dashboard with service overview and account updates. Sidebar navigation and account shortcuts. Product and service management screens. Domain listings and supported management actions. Invoices, billing information, and payment-related account views. Support tickets, Knowledgebase, and announcements. Login, registration, password recovery, and account details. Available actions follow the customer’s permissions and your enabled WHMCS functionality. Checkout with the details customers need The matching orderform supports product configuration, available billing cycles, domain choices, configurable options, add-ons, and guest or existing-customer checkout. Its itemized order summary presents the information supplied by WHMCS, including products, domains, selected options, billing periods, and recurring charges where available. Native discounts, taxes, credits, and totals remain authoritative. Multilingual content. RTL & LTR layouts. Translate public website content, navigation, and supported theme labels through the Studio, with a reading direction for each language. Prepare English LTR and Arabic RTL presentations, while native account and checkout fields use your installed WHMCS language packs. Language and currency controls follow your WHMCS configuration. Installation & documentation The package includes the website theme, matching orderform, Studio administration addon, and English and Arabic HTML documentation. Installation guidance covers activation, branding, products, languages, publishing, updates, and recovery. Editable project backups, saved published versions, and factory design recovery tools help you manage future changes. Weeby Studio requires an existing, licensed, self-hosted WHMCS installation. Confirm compatibility with your WHMCS release before purchasing. Hosting, WHMCS licensing, payment gateways, registrars, and provisioning services are configured separately. Explore Weeby Studio Live website demo https://hostk.com/weeby-demo/ Live Client Area demo https://hostk.com/weeby-demo/clientarea.php Email Address: test@hostk.com Password: test Special Price: $49.99 USD — reduced from $120 USD One-time purchase. Website-bound activation for one installation. Get Weeby Studio https://hostk.com/weeby/ We’d love to hear your feedback on the visual Studio, the customer workspace, and the ordering experience. Questions are welcome in this thread. Weeby Studio by Hostk Your website. Your client area. Your checkout. One connected brand.    

Hello WHMCS Community, We’re introducing Weeby Studio — a complete WHMCS theme with a visual website builder, custom client area, and matching orderform and checkout, created by Hostk. The idea is simple: give hosting businesses a consistent brand experience and practical control over their website. Your pages, product presentation, customer workspace, and checkout share one design, with a dedicated Studio inside WHMCS to make it your own. Your hosting website. Your brand. Your Studio. Meet the Visual Studio Update your website from a focused visual workspace inside the WHMCS administration area. Edit visually: change website text, images, links, buttons, and supported styling. Build your pages: create or duplicate public pages, add content blocks, and arrange editable sections. Find every detail: navigate page structure through Pages and Layers. Manage your assets: upload images and replace editable visuals. Preview across devices: review desktop, tablet, and mobile layouts. Control shared elements: customize website navigation, headers, footers, and brand settings. Manage on-page SEO: edit browser titles, search descriptions, and image alternative text. Publish when ready: save an unpublished draft, review your changes, then publish. Keep a recovery path: export editable project backups and revisit saved published versions. Everyday content changes can be made in the visual editor, while native WHMCS forms, live prices, permissions, and transactions retain their original behavior. One design, from first visit to checkout Weeby Studio includes three connected parts of your customer experience: 1. Your public website A responsive hosting website with service landing pages, product presentations, comparison sections, and shared navigation. 2. Your client area A branded customer workspace for services, domains, invoices, support tickets, account information, and everyday account tasks. 3. Your orderform A matching product selection, configuration, cart, and checkout experience using native WHMCS ordering. The result is a consistent visual identity as customers move between your website, their account, and their next purchase. 23 starting pages. Room for your own ideas. The included public collection contains 23 pages, including 14 service landing pages, a homepage, service directory, and policy pages. Hosting & compute: Web Hosting, Cloud Hosting, Reseller Hosting, VPS Hosting, Dedicated Servers, and Game Servers. Business & security: Domains, Professional Email, SSL Certificates, and VPN. Expert services: Web Design, Backup & Recovery, Website Migration, and Managed Services. Customize the included content or create additional public pages through the Studio. 12 color palettes + your own brand colors Start with the original Weeby blue, navy, and white identity, choose one of 12 coordinated palettes, or create a custom palette. Set your brand accents, buttons, navigation, headings, text, backgrounds, surfaces, and borders. Customize your logo, typography, content width, and button corners from the shared design controls. Supported bundled visuals and the default favicon follow the selected palette. Your uploaded photos, custom logo, and custom favicon keep their original artwork. Product presentation connected to WHMCS Your real catalog stays central to the website. Connect website plan slots to specific WHMCS products or product groups. Display product names, descriptions, prices, and available billing cycles from WHMCS. Use the currencies and pricing configured in your installation. Customize supported CPU, RAM, storage, transfer, and other resource display labels. Presentation labels remain separate from the actual service specifications and allowances defined in WHMCS. A client area that feels part of your brand The custom client area brings key customer tasks into a coordinated layout: Dashboard with service overview and account updates. Sidebar navigation and account shortcuts. Product and service management screens. Domain listings and supported management actions. Invoices, billing information, and payment-related account views. Support tickets, Knowledgebase, and announcements. Login, registration, password recovery, and account details. Available actions follow the customer’s permissions and your enabled WHMCS functionality. Checkout with the details customers need The matching orderform supports product configuration, available billing cycles, domain choices, configurable options, add-ons, and guest or existing-customer checkout. Its itemized order summary presents the information supplied by WHMCS, including products, domains, selected options, billing periods, and recurring charges where available. Native discounts, taxes, credits, and totals remain authoritative. Multilingual content. RTL & LTR layouts. Translate public website content, navigation, and supported theme labels through the Studio, with a reading direction for each language. Prepare English LTR and Arabic RTL presentations, while native account and checkout fields use your installed WHMCS language packs. Language and currency controls follow your WHMCS configuration. Installation & documentation The package includes the website theme, matching orderform, Studio administration addon, and English and Arabic HTML documentation. Installation guidance covers activation, branding, products, languages, publishing, updates, and recovery. Editable project backups, saved published versions, and factory design recovery tools help you manage future changes. Weeby Studio requires an existing, licensed, self-hosted WHMCS installation. Confirm compatibility with your WHMCS release before purchasing. Hosting, WHMCS licensing, payment gateways, registrars, and provisioning services are configured separately. Explore Weeby Studio Live website demo https://hostk.com/weeby-demo/ Live Client Area demo https://hostk.com/weeby-demo/clientarea.php Email Address: test@hostk.com Password: test Special Price: $49.99 USD — reduced from $120 USD One-time purchase. Website-bound activation for one installation. Get Weeby Studio https://hostk.com/weeby/ We’d love to hear your feedback on the visual Studio, the customer workspace, and the ordering experience. Questions are welcome in this thread. Weeby Studio by Hostk Your website. Your client area. Your checkout. One connected brand.    

Hi, I'll take the unanswered question. First, the stock behaviour.   In stock WHMCS, when a client clicks Accept on a quote, the quote is only marked Accepted. No invoice is created. Converting to an invoice is a separate admin step (Convert to Invoice on the quote). That matches what you're seeing from the normal WHMCS pages.   So if the hash-link route creates an invoice, something other than stock behaviour is doing it. There are three likely sources: - Kian's script itself - another hook in your hooks folder - an addon module. For example, ModulesGarden's Quotes Automation can auto-create invoices on accept, so check whether you have anything like it installed.   How to find what's creating it 1. Open the activity log and look at the entries around the time you tested an accept. You should see the quote being accepted and then the invoice being created, and the order and timing tell you a lot. 2. Search the script and your hooks folder for the following. Searching all of them also catches any hook that creates an invoice directly:    - `AcceptQuote`    - `ConvertQuote`    - `CreateInvoice`    - `localAPI`    - invoice inserts 3. Check Addon Modules for anything quote-related. 4. On a staging copy, rename the script or hook file, repeat the accept, and see if the invoice still appears. Test this on staging, not live.   If the script calls the local API to accept the quote, check what that call does in your WHMCS version. It may not behave exactly like the client-area button.   To stop it Remove or comment out the invoice-creation part in the script and leave only the accept step. If it's a module, look for an "auto create invoice on accept" setting. Then convert from admin when you're ready.   AcceptQuote hook caveats - It receives `quoteid` and `invoiceid`, but `invoiceid` is only there if applicable. In the stock flow it will be empty, so don't assume it's populated. - It runs after the accept has happened. It can notify or react, but it can't veto the accept. If you need a gate, do it before the accept call. - If you create an invoice from inside the hook, check the quote doesn't already have one first. Otherwise a double click, or a module and a hook both firing, gives you duplicate invoices.   Since the hash link is unauthenticated, make sure the hash is long, random and ideally expiring. Also log the IP and time of each accept.   The original script is old, so test it on your current version before relying on it.

Hi Semih, going direct to the Cloud API instead of through a middleman is the right call. Here are my answers from the hosting ops side.   1) Sending WhatsApp today and what annoys me I haven't found anything clean. The usual options are hook scripts, email-to-message gateways, or a third-party layer in the middle. The pain points I'd want solved are: - Template approval. Anything that goes outside the 24-hour customer-service window has to be a pre-approved template, so the module needs to handle template names, languages and variables properly. - Category. Meta treats UTILITY (invoice due, payment received, service suspended) differently from MARKETING, and the pricing differs. Meta can also recategorise a template you submitted as UTILITY. Ready-made templates should be worded so they're clearly transactional, with no upsell text, or they'll end up in the wrong bucket. - Delivery status. "API accepted it" doesn't mean the customer got it. I'd want the webhook statuses (sent, delivered, read, failed) stored against the client or invoice, with the failure reason visible. Otherwise you find out at suspension time that the reminder never arrived. - Phone numbers. WHMCS phone formats are a mess, so E.164 normalisation and a sensible country-code fallback matter more than people expect. - Opt-in. Per-client consent should be recorded, so the module can skip clients who haven't opted in.   2) Events that matter For clients: - invoice created - payment reminders and overdue notices - payment received - failed card payment - service suspended or unsuspended - domain expiry - ticket reply   For staff: - new order - fraud-flagged order - high-priority ticket - failed module commands or provisioning errors   I'd keep credentials and passwords out of WhatsApp entirely.   A question on architecture: as I understand it, WHMCS notification rules are mainly aimed at staff-side channels. How are you handling client-facing messages, with per-client recipients and opt-in? A proper Notification Provider is much better than email-pipeline hacks, because you get event rules, no parsing of rendered emails, and a cleaner failure path. I'd just like to understand how it covers the client side.   3) One-time vs subscription I prefer one-time. Hosters get tired of recurring fees on small modules. Meta's API will keep changing, though, so a one-time price with an optional paid update and support period seems fair to me.   I'd happily try an early build if you're offering one.

@charlotteclark good question, and I can answer part of it from the docs. The developer reference for the EmailPreLog hook, which runs just before an email is written to the log, lists the recipient, cc and bcc as separate values of the entry. So the CC and BCC addresses are recorded with the message, not only the primary recipient. The docs don't say how the Email Message Log screen lays that out, so I can't promise the exact wording of the CC line you'll see.   The quickest way to settle it is a test. Make a custom General email template with one CC address filled in, send it through SendEmail to a dummy client, then open that message from the client's Emails tab and from Configuration, System Logs, Email Message Log. And check the headers of the copy that lands in the CC mailbox, since that is what proves the CC was actually applied.   You're right about the opt-in scopes for contacts, by the way. The docs say a contact receives copies of General messages only if they have the General notification option on, product messages only with the Product option, and domain messages only with the Domain option. So the contact's preference has to match the type of message you send.   On the database edit idea, I'd avoid it. Rewriting the template's CC field before each send is racy, as the suggestion itself admits, and it changes the template for every other email using it. For addresses that vary per client, contacts with the right preferences do the job without touching template rows.

@Rukka, RadWebHosting is right, and here's how I'd go about it. That error means a class WHMCS expects in its vendor directory isn't there. The usual causes are an incomplete upgrade, or files removed or damaged after the fact.   1. Back up your WHMCS files and database first. 2. Note the exact WHMCS version you're running. It needs to be the same version, not newer or older. 3. Download the Full Release Files for that version from the WHMCS download site, or from your reseller if that's where you license it. 4. Upload the zip to your WHMCS root and extract it, overwriting the existing files. This puts back any missing vendor classes, including PhpImap\Mailbox. 5. Check that the owner and permissions on vendor/ match the rest of your install, so PHP can read it.   Then send a test email or open a ticket to confirm mail is flowing again.   If the error comes back soon after re-uploading, ask your host whether a security tool such as Imunify360, CageFS or an antivirus is quarantining or removing those files. If so, they'll need to whitelist your WHMCS directory.   Only once the vendor files are restored, and only if POP/IMAP ticket import still fails, would I look at the PHP IMAP extension. A missing extension gives a different error (Call to undefined function imap_errors()). It's a separate problem from this Class not found one.   Let us know how it goes.

The backend middle layer is what would decide this for me too, more than the builder choice. In a Cheyenne-side setup I'd keep tickets in WHMCS as the source of truth and have the app poll or use webhooks for replies rather than trying to cache thread state locally, since stale conversations are the silent failure you're worried about. Attachment upload through a middle layer also needs size and timeout handling tested, not just the happy path. I came across AI App Builders vs Traditional Development https://aibuildercompare.com/blog/ai-app-builders-vs-traditional-development while reading around this and it pushed me toward keeping the custom API thin. Has anyone actually run ticket threading that way under load?

Ticket attachments are my sticking point too. I'm helping a small Portland host move client accounts to a mobile view, and the reply mentions trying the full ticket flow on a phone, which I take seriously because a screenshot upload is where a no-code builder can quietly fail. Before picking between FlutterFlow and Rork I came across this comparison: FlutterFlow vs Rork (2026): Which Should You Pick? https://aibuildercompare.com/compare/flutterflow-vs-rork. My uncertainty is the backend middle layer; I can handle the OIDC login, but keeping ticket threads current without silent failures worries me. Anyone running this in production?

@jmginer this is expected behaviour in v9, not a broken cancel flow. From v9, published invoices are immutable. When a client requests cancellation, WHMCS no longer deletes the renewal line from an already-issued invoice. What it does instead: 1. If the unpaid invoice only contained that cancelled service, the system cancels the whole invoice (and creates a credit note for it). 2. If the invoice also has other items, the system leaves the invoice in place and creates a credit note for just the cancelled service line. The original line stays on the invoice for the audit trail; the credit note offsets the balance.   So the line "not being removed" is the new model. The balance due should drop by the credited amount once the credit note exists. Check the invoice view for a linked credit note, and Clients > Cancellation Requests / the service's Pending Cancel status to confirm the request registered.   Also worth confirming: 1. Immediate vs End of Current Billing Cycle on the request (EOBP won't terminate until the cycle ends; the invoice handling above still applies to unpaid renewals). 2. Automation Settings > Cancellation Requests if you expect automatic terminate on the due date. 3. Exact version (9.0.x vs 9.1.x), in case you're looking at a Draft invoice (Draft lines can still be deleted) versus a published Unpaid one.   If there is no credit note and the full amount is still due after a cancel request on a published unpaid invoice, say which version you're on and whether that invoice had other items on it.