Description
Revamp your customer service with this powerful tool that combines contact forms, support tickets, chat, and a comprehensive CRM system to enhance interaction and efficiency. Manage conversations front and back end, attach multimedia files, webcam recordings and customize contact forms for specific needs. A floating icon and reporting buttons on content facilitate communication, making it ideal for any business aiming to improve responsiveness and customer satisfaction.
Benefits
- Unified Communication Platform: Integrates contact forms, support, chat, CRM into a single, efficient workflow.
- Enhanced Multimedia Support: Users can send messages with webcam, screen, and microphone recordings, enhancing interactive support.
- Customizable Contact Forms: Tailor contact forms with custom fields to collect specific information needed for various departments.
- Advanced Conversation Management: Manage and monitor conversations from both frontend and backend, improving service responsiveness.
- Email Confirmation for Security: Protects against spam by requiring email confirmation from visitors before starting conversations.
- Multilanguage Support: Offers real-time translation of messages with DeepL integration, catering to a global audience.
- Monetization Options: Integrates with the MicroPayments Plugin for paid support options, allowing for flexible revenue models.
- Comprehensive Reporting Tools: Easily report and manage content directly from posts with configurable buttons, enhancing content control.
Features
- Support pages in website frontend for starting/accessing conversations
- Members can open a conversation directly, while visitors have to confirm their email first
- Admins can see and access open Conversations from backend
- Report Content button for any post types (configurable)
- Contact Owner button for any post types (configurable)
- Contact Creator in BuddyPress/BuddyBoss profile for configurable roles
- My Conversations page to website frontend, to access own tickets by logged in users
- Custom support departments for website / report content / contact content owner / contact user
- Floating support buttons (contact, new messages) on all pages (can be disabled)
- Message counter in backend (site support) and frontend (for creators)
- Send webcam/screen/microphone recordings and file uploads in conversations
- Store new conversation attachments outside the web root and retrieve them with conversation access proof; administrators can inventory, migrate, and remove attachments
- Protected software/resource downloads catalog with optional plan-based access control
- Secure download gateway with short-lived signed links (no direct file URL exposure in frontend)
- API endpoint for updater/client plugins to list authorized downloads by contact credentials
- Custom contact forms with custom fields (text, dropdown, toggle) and data saved per contact
- Custom form per department enables custom fields per conversation (ticket)
- Invite by email to fill a form, contact a department or join a new conversation
- Can messages, add to later messages for quick replies
- Integrates with MicroPayments Plugin for paid support (per conversation, message)
- Account creation: search CRM contacts by name or email and generate a token using the selected contact ID.
- Customer account sections: Accounts, Organization and conditional Billing, with private subscription/payment summaries, a Stripe portal login and configurable titled plan links.
- Administrator Billing & Delivery: separate Stripe Sandbox/Test/Live connections, read-only payment review, product-to-plan mappings, reviewed manual provisioning, delivery drafts and manual account actions.
- Structured properties editor for accounts, account plans and organization plans, with configurable fields and download access keys from the catalog.
- Registration forms: register accounts in an external MySQL database, in example for VideoWhisper WebRTC server
- Multilanguage conversations with DeepL integration for translating messages on request
- Support Wiki pages with Markdown rendering for headings, lists, tables, images, code blocks, quotes, dividers, links, Fomantic UI-compatible classes when Fomantic is available, and a lightweight stylesheet loaded only on pages that render Support Wiki/Markdown content
- Integration hooks for VideoWhisper Site Manager / Site Manager Pro, enabling AI tools to read conversations, send CRM messages with native notifications, retrieve CRM stats, include external account counts when configured, and identify contact lead activity from conversation/message/account counts
More features to come …
External services
- Stripe: only after an administrator explicitly connects a mode, read-only requests to https://api.stripe.com retrieve the configured account’s billing objects using its restricted key and object/customer IDs; when a signed-in customer opens Billing, their confirmed CRM contact email is sent for exact customer lookup. Signed webhooks refresh minimal billing snapshots. Needed customer names/emails, product labels, invoice/payment relationships, amounts, currencies and subscription/transaction IDs/statuses are retained locally for administrator review; card details and full webhook payloads are not retained. No registration, payment creation, refund, cancellation or automatic suspension occurs. Service: https://stripe.com/ ; Terms: https://stripe.com/legal/ssa ; Privacy: https://stripe.com/privacy .
- DeepL: when a site administrator supplies an API key and enables translations, authenticated translation requests send message text and source/target languages to https://api.deepl.com or https://api-free.deepl.com. Updating the supported-language list sends the API credential. Service: https://www.deepl.com/ ; Terms: https://www.deepl.com/en/pro-license ; Privacy: https://www.deepl.com/en/privacy .
- Email: normal notifications use WordPress wp_mail and the site’s configured transport. If the administrator selects Postmark or Brevo and supplies credentials, notification/test requests send sender/recipient addresses, subject, message and configured headers to https://api.postmarkapp.com/email or https://api.brevo.com/v3/smtp/email. Postmark terms/privacy: https://postmarkapp.com/terms-of-service and https://postmarkapp.com/privacy-policy . Brevo terms/privacy: https://www.brevo.com/legal/termsofuse/ and https://www.brevo.com/legal/privacypolicy/ . No test email is sent automatically.
- Google reCAPTCHA: only when enabled with site/secret keys, covered forms load https://www.google.com/recaptcha/api.js and submit the response token (and visitor IP when supplied) to https://www.google.com/recaptcha/api/siteverify for spam checks. Service: https://cloud.google.com/security/products/recaptcha ; Terms: https://cloud.google.com/terms ; Privacy information: https://cloud.google.com/terms/cloud-privacy-notice . Site owners must configure any required visitor consent.
- Analytics: configured event names are sent to an existing window.gtag/dataLayer integration when present, including form/conversation event metadata. The plugin does not create a Google Analytics account. Site owners control analytics loading and consent. Google Analytics terms: https://marketingplatform.google.com/about/analytics/terms/us/ ; Privacy: https://policies.google.com/privacy .
- Optional streaming/account providers: only when their database/API/server settings are supplied, the plugin exchanges account, organization, plan, authentication, schedule, stream and usage information with those configured destinations. These may be self-hosted. Provider URLs, terms and privacy policies are determined by the administrator’s selected provider. VideoWhisper’s server project: https://github.com/videowhisper/videowhisper-webrtc . VideoWhisper service terms/privacy: https://www.videowhisper.com/view.php?p=Terms+of+Use and https://www.videowhisper.com/view.php?p=Privacy+Policy .
Geolocation now uses local server GeoIP data only. The former automatic third-party IP lookup is removed. Trusted reverse proxies can be declared with the vws_support_trusted_proxy_ips filter; otherwise rate limits use the validated connecting IP address.
Application source
The corresponding source for the included Support React application is in source/support/, with its dependency lock and BUILD.txt instructions. The WordPress plugin runs the bundled compiled assets without Node.js. The source export excludes deployment settings and private credentials.
Bundled libraries
Fomantic UI 2.9.4 (MIT), https://github.com/fomantic/Fomantic-UI , and Chart.js 4.4.0 (MIT), https://github.com/chartjs/Chart.js , are served locally. Their license notices are included in semantic/LICENSE.md and static/vendor/chartjs/LICENSE.md. The legacy CDN setting no longer offloads these libraries.
License
This plugin is released under a GPL license.
Billing freshness and organization contacts
Billing opens with New orders. Visiting a connected Billing screen or completing connection setup starts a read-only recent invoice/payment refresh when the previous check is older than the configured interval (90 minutes by default). Configure the interval or refresh manually under Sync & security. Native authenticated background requests process bounded pages while the screen is open; the billing worker continues queued work. This reads Stripe and updates the local billing cache, without provisioning, suspending, charging or changing subscriptions. Use full synchronization for historical records and catalog/customer/payment-link changes, and signed webhooks for changes to older records.
The Organization tab lists names and contact addresses for the current contact and other members assigned to the same organization, in pages of 25. Directory access requires a confirmed CRM contact linked to the signed-in WordPress user. Organization identity is derived on the server; URL parameters cannot select another organization. Contact PINs, metadata and account credentials are excluded.
Trial lifecycle (opt-in)
Native Trial lifecycle administration prepares additive storage, previews existing accounts and configures explicit trial plans. Defaults are 60 initial days, two 30-day customer renewals, 30 inactive days and a warning five days before the next deadline. A separate reviewed campaign defaults to 90 inactive days and at most 10 pauses per UTC day. Preparing/upgrading does not activate restrictions or enroll existing accounts. Unknown activity/domain history requires review.
My Accounts provides eligible renewals with a configurable reason/message form and a support conversation, upgrade/contact links and owner pause/resume controls. A separate email-code session supports trial management without WordPress/billing login or account-credential disclosure. Renewals, domain claims, quotas and notification receipts use durable transaction/replay fences. Paid upgrades and independent suspension reasons are preserved. Organization incentive grants are native, manual and separately reviewed; expiry resolves to their configured base plan, independently of streaming accounts.
Domain proof uses public HTTPS with pinned public DNS, no redirects/proxies, and a fresh HMAC challenge to the configured site. The streaming server and clients must be installed/tested separately before an administrator enables enrollment. Service cache changes can take up to five minutes; WordPress cron determines notification timing. Already negotiated P2P media cannot be certified stopped by disconnecting signaling. Trial-only pages must be excluded from third-party page caches.
The current template includes the new trial UI and emails. No bundled CRM locales are provided. Existing customer data/history is retained; expired one-use access codes are cleaned in bounded batches. No automatic subscription cancellation, paid-plan suspension or cPanel change is performed.
FAQ
How does system prevent bulk submissions from “visitor” bots?
A visitor needs to register a contact and confirm email to create a new ticket.
How are tickets secured ?
Each contact (email) has a code to access ticket.
How are conversation attachments stored?
New attachments and recordings require writable storage outside the web document root. The default is a vw-support-attachments/site-{blog-id} directory beside the WordPress home directory; a site administrator can configure another private local path through the vwls_attachment_storage_directory filter. Attachment types and size limits are in Application settings. Ticket Admin can count, migrate and remove attachments for selected tickets. Migration verifies a private backup and retains originals for review when it detects shared or unsupported references. Existing files remain public until migrated and verified public copies are removed. Backups are retained separately and are not included in attachment counts.
How are downloads secured ?
Downloads are served through a protected gateway endpoint. Public items are allowed when the download access key is empty; protected items require matching organization plan properties and valid contact authentication.
Can Support Wiki pages render Markdown?
Yes. Support Wiki pages can render agentic Markdown content automatically, and the [videowhisper_support_markdown] / [vws_markdown] shortcodes can render Markdown in regular content. The renderer supports headings, paragraphs, ordered and unordered lists, pipe tables, block images, fenced code blocks, blockquotes, dividers, inline code, bold, italic, absolute links, and relative wiki links. Rendered output includes Fomantic UI-compatible classes such as ui table, ui list, ui header, ui message, ui image, and ui breadcrumb where appropriate, plus a lightweight stylesheet for breadcrumbs, tables, lists, quotes/citations, code blocks, and figures on pages that need it.
How does this integrate with VideoWhisper Site Manager?
When VideoWhisper Site Manager is active, site admins can enable read-only AI access for users to retrieve their own CRM conversations. VideoWhisper Site Manager Pro can additionally enable message writes, admin CRM stats, contact retrieval, and new conversation creation. This plugin exposes integration hooks so Site Manager Pro can use the current CRM notification templates, cooldown settings, contact activity summaries, and external account database counts without exposing database passwords.
Site Manager’s dynamic agent guide documents CRM tools when this plugin and the relevant Site Manager settings are active. User tools include crm_list_my_conversations and crm_get_my_conversation_messages; Pro can add crm_send_my_conversation_message, crm_admin_get_stats, crm_admin_list_conversations, crm_admin_get_conversation_messages, crm_admin_send_conversation_message, crm_admin_list_contacts, and crm_admin_open_conversation.
How do I connect Stripe for billing review?
Open Support CRM > Billing & Delivery > Stripe connection. The native setup guide links to Stripe and walks through the selected environment, read permissions, API key, webhook and verification. Keep CRM changes disabled for read-only acceptance testing. Use an isolated CRM accounts database before enabling fixture mutations.
- Sandbox (recommended for a new demo): open the Stripe Dashboard, choose the account picker > Switch to sandbox, then create or open a dedicated general sandbox. Keep it selected while opening API keys and Webhooks. Choose Sandbox in this CRM. Stripe sandbox instructions.
- Test Mode (existing integrations): select the business account’s Test Mode environment in Stripe and Test Mode here. Its credentials and webhook are separate from a general sandbox, although both key prefixes are rk_test_.
- Live (real billing): select the intended live business account in Stripe and Live here. Use its separate rk_live_ key and live webhook signing secret. Environment buttons do not apply CRM changes or switch the customer-facing Billing environment.
In Stripe API keys, choose Create restricted key, start with no permissions and name the key for this CRM. Set Read for account identity, Customers, Products, Prices, Subscriptions, Invoices/Invoice Payments, PaymentIntents, Charges and Disputes; leave other permissions at None. Do not grant Write or connected-account permissions. Create the key, complete any verification and copy its full value into the native form. Publishable pk_ and unrestricted sk_ keys are refused. Store the key securely because Stripe may reveal it only once. Restricted-key instructions.
In Workbench > Webhooks, create an event destination for Your account, select Snapshot and API version 2025-06-30.basil, then select the events shown by the CRM. Choose Webhook endpoint and paste the selected CRM environment’s displayed endpoint URL. Save, open the endpoint and reveal its Signing secret. Copy that whsec_ value into the form; it is separate from the API key. Keep WooCommerce endpoints intact and use this dedicated endpoint’s secret, rather than a CLI listener secret or another environment’s secret. Stripe webhook instructions.
Verify and save with CRM changes disabled. Both credentials are required initially; blank fields preserve existing values. Saving verifies account identity, not webhook delivery or every resource permission. Start full read-only synchronization under Sync & security, check Sync & security and send a test delivery from the Stripe endpoint. Environment buttons save the current administrator’s selection for the Billing menu; customer-facing billing keeps its separate setting. Health reports completed stages, object counts and dates. Zero is a valid empty result. If automatic WP-Cron is disabled, arrange a server scheduler or use Process next sync page until Complete and Process pending billing updates now for queued webhook work. API connection, completed sync, signed webhook receipt and event processing are separate checks. For denied reads, inspect the failed GET request in Stripe Workbench and add only its missing Read permission. WP-Cron needs site traffic or a real host cron. Stripe test payment methods.
To switch to Live, create a new live restricted key with the tested read permissions and a separate live Snapshot endpoint/secret. Save in the CRM Live environment with changes disabled, confirm the account ID, synchronize and review real transactions. Review live Price-to-plan mappings and buyer links separately; test records, grants and mappings are not copied. When ready for customers, select Live under Customer billing and configure the live public portal login and plan-page links. Stripe live-mode keys.
A hosted account-connection flow requires a registered Stripe App or Connect integration. New standard Connect platforms cannot request read-only OAuth; this release uses the explicit restricted-key path for one business account. A registered restricted-key Stripe App can be evaluated for future installation assistance. Stripe Apps, Connect OAuth requirements.
Credentials are encrypted with PHP Sodium and a key derived from this site’s WordPress authentication salts. Protect both configuration and database backups. Hosts can supply VWS_STRIPE_CREDENTIALS[blog_id][mode] with key/webhook values in wp-config.php, then verify the connection in the native interface. Changing salts requires reconnecting encrypted credentials. Sandbox and Test Mode use separate records even though both use test keys. Live mode requires its own live restricted key, webhook secret, mappings and reviewed change permission. Selecting Live never copies test grants or performs a CRM action.
An email match only suggests a contact; administrators must confirm the buyer/contact association and exact account ownership. Map each Stripe Price ID to account/organization plans and one of the three editable delivery templates. Preview and confirm each delivery. First-stage provisioning supports paid initial or manual, single-unit priced invoice lines with successful PaymentIntent/charge evidence. Quantities, prorations, trials/zero totals, credits/out-of-band settlements, standalone Checkout orders without invoices and nonstandard payments require separate manual handling. Renewals are reviewed as payment evidence and never create another account automatically. Templates omit credentials; a separate action creates a private representative draft, with sending handled in the Support application.
Payment issues separate invoices, payments, subscriptions, buyer links and account-action forms into subtabs. Lists show 10 newest matching records per page, with name/email/item/Stripe-ID search. Run a new full read-only sync after upgrading to populate customer/product labels, exact invoice-payment links and the local search index. Email matches suggest CRM contacts and never confirm ownership or deliver access automatically. Payment issues show delays and cancellations for administrator review. There is no automatic suspension, cancellation, refund or WHM call. Manual suspension and plan changes require a reason and an expiring preview; changed evidence invalidates it. cPanel work is performed separately and recorded in the hosting checklist. Unverified accounts uses administrator-selected paid plans and recorded evidence; missing linkage or incomplete history is not proof of nonpayment. Existing manual and non-Stripe evidence can be recorded explicitly. Interrupted external/database commits remain held for reconciliation instead of blindly repeating provisioning. Billing records are retained when the plugin is disabled or removed. The signed-in customer Billing tab exposes only a minimal summary for that user’s single confirmed CRM email contact. Customer PIN and AI tools do not gain billing readers.
What appears in the My Accounts Billing tab?
The accounts shortcode provides Accounts and Organization sections, and shows Billing only when the customer-facing connection is configured and enabled. Administrators choose the single customer-facing Live, Sandbox or Test environment under Billing & Delivery > Customer billing. Browser parameters cannot select another contact, email, customer ID or environment. A single confirmed email contact must be linked to the signed-in WordPress user. Exact Stripe email matches are reviewed without granting CRM access; an existing administrator-confirmed buyer link can resolve a case-only email difference. Ambiguous or conflicting identities require support review.
Customer summaries include subscription status, latest invoice/paid and period dates, cancellation scheduling and recent charged/failed/pending/refunded/disputed payments. Reads are bounded, use a five-minute private cache and create no CRM access changes. Account and Organization tabs execute their selected section independently; viewing Organization no longer creates an organization or migrates account links automatically. Existing explicit owned organization-name edits remain available.
Configure a public Stripe customer portal login URL per environment. The portal authenticates customers by email and controls available plan changes, cancellation and invoices; no portal-session API writes are needed. Private single-customer session links are refused. Custom Stripe billing domains are supported with the same HTTPS public /p/login/ URL form. Add up to 20 plan-page links, each with a title and HTTPS URL, using one Title | URL line per page. Portal and plan links remain available if the Stripe read API is temporarily unavailable. No portal or plan destination is guessed from an email address.
Why must statistics users have a linked WordPress user ID?
A signed-in WordPress user is identified by their WordPress numeric user ID. Their CRM contact must have that same value in its uid field; the streaming account’s Contact ID then points to that contact. Matching an email alone does not establish this ownership. Review the CRM contact’s linked WordPress user and account Contact ID before allowing statistics access; do not replace the account Contact ID with a WordPress user ID.
Translation status
The English translation template is maintained. No translated locale catalogs are bundled with this release. Site-specific translations must be updated for new billing, payment, access and consent wording before use.
Screenshots
Changelog
1.16.2
- Fix Ticket Admin pagination so page numbers and the selected issue filter remain in the URL query.
- Show contact confirmation beside each participant; confirmed representatives alone do not qualify a pending conversation for activation.
1.16.1
- Publishes opt-in account lifecycle, billing review, structured plan properties and private conversation drafts. Installation and storage preparation leave restrictions and billing mutations disabled.
- Rechecks revoked account/site credentials, requires transactional one-use email-code storage, rejects invalid pause controls and removes browser SQL/debug confirmation disclosures.
- Includes corresponding Support application source and build instructions.
1.16.0
- Adds opt-in Developer trial, domain verification/quota, renewal portal and notification review; administrators control activation separately.
- Adds manually reviewed organization incentives and limited optional plugin-connection sessions.
- Prevents linking an unassigned legacy account by a domain string alone; sends account notifications only after a successful database insert.
1.15.0
- Activate all eligible Pending/Pending Answered conversations after verified contact confirmation; add native Ticket Admin diagnostics and selected repair for older mismatches.
- Open Billing on New orders and refresh stale recent invoices/payments automatically, with a configurable 90-minute default and bounded background progress.
- List the authenticated contact and other contacts from the same organization, with safe fields and pagination.
- Preserve billing service-change controls, message history, access codes and existing tool approvals.
1.14.1
- Recover one private billing delivery draft across interrupted job-receipt writes and retries by different administrators. No notification is sent while saving or recovering the draft.
1.14.0
- Add durable private administrator conversation drafts with editing, revision checks, explicit sending and notification receipts in the native CRM and Support application.
- Show mapping amounts and intervals; search by product or CRM plan name.
- Add versioned billing review, plan, mapping, delivery-template and private draft extension contracts.
1.13.11
- Identify the selected Stripe price by product, per-unit amount and billing interval; display named CRM plan links in paginated Mappings.
1.13.10
- Separate Price to Plans, Mappings and Prices into on-demand subtabs, with searchable 10-row catalog pagination and retained selected-price save routing.
1.13.9
- Show products, mapped CRM plans, quantity-based recurring rates, billing intervals, estimated payment dates and exact contact account counts in the first Active Subscriptions subtab.
1.13.8
- Add Active Subscriptions review with existing CRM contact matches, search and ten-row pagination, ordered by the latest dated nonzero paid invoice for each subscription.
- Match invoice, subscription, customer and billing environment exactly; subscriptions without a dated paid invoice sort last.
1.13.7
- Separate invoice, payment, subscription, buyer-association and manual account review into subtabs. Search synchronized names, emails, purchased items and provider IDs with 10 newest records per page.
- Synchronize minimal customer/product descriptions and exact invoice-payment relationships for useful review links and CRM contact suggestions; keep access changes manual and independently authorized.
1.13.6
- Add optional native Server sync controls, generic committed account/plan notifications and service providers selected by old/new plan properties.
- Reuse detected relay registration for targeted authenticated invalidation; queue bounded delivery with retries while retaining customer permissions and existing streaming registration behavior.
1.13.5
- Display common-currency invoice, payment and refund amounts consistently in currency units; label unfamiliar currency amounts as minor units.
- Reject malformed amount/currency display inputs without changing stored billing amounts or payment evidence.
1.13.4
- Remember each administrator’s selected billing environment and open a connected environment when no preference exists.
- Show connection/read-only state, readable sync stages/counts/timestamps, cron delays and separate webhook-delivery verification.
- Keep sync errors on Health, replace unconnected-environment errors with setup guidance and make CRM write permission an advanced setting.
1.13.3
- Identify publishable/unrestricted API keys and incorrect webhook signing secrets with specific setup errors; keep rejected connections on the setup page.
- Show required credential prefixes, clarify Test Mode labels and accept surrounding copy/paste whitespace without relaxing restricted-key or environment checks.
1.13.2
- Guide administrators through separate Sandbox, Test Mode and Live Stripe setup with official Dashboard/documentation links, restricted read permissions and webhook signing-secret instructions.
- Add an explicit test-to-live checklist and distinguish admin environment selection from customer-facing billing configuration.
1.13.1
- Organize customer accounts into Accounts, Organization and conditional Billing sections.
- Add owned, read-only subscription/payment summaries, configured public Stripe portal login links and multiple titled plan-page links.
- Prevent Organization GET views from creating CRM objects, reject ambiguous/foreign billing identities and scope short-lived cached summaries to the current WordPress user/contact/environment.
1.13.0
- Add native Stripe Billing & Delivery review with separate Sandbox, Test and Live credentials, mappings and records.
- Add explicit buyer linking, Price-to-plan mappings, reviewed manual account/organization provisioning, delivery templates and representative drafts.
- Report payment delays, cancellations, refunds/disputes and administrator-selected paid accounts requiring evidence review. Manual account actions and hosting receipts require explicit review; no automatic suspension or WHM changes.
- Verify signed webhook receipts and current payment state, hold ambiguous partial jobs for reconciliation, and remove private account/SQL/message values from affected legacy logs.
1.12.14
- Edit common account and plan properties with configurable structured fields or the manual JSON editor. Organization plans include access keys from the Downloads catalog.
- Preserve unedited JSON values and report failed account and plan saves.
1.12.13
- Search for a CRM contact when creating an account and generate a new account token from its name and contact ID.
- Restrict account statistics to the signed-in user’s linked contact, and limit database diagnostics to administrators.
1.12.12
- Search accounts by contact name or email and avoid empty-pagination warnings.
- Require ticket-specific or representative access for existing conversations, and protect logged-in display-mode updates with a session nonce.
- Store new conversation files and recordings privately, enforce configurable upload types and sizes, and provide ticket-level inventory, migration with private backups, and removal tools. Existing public files require migration; shared or unusual references are retained for review.
- Store new restricted catalog uploads outside the web root and warn about existing files in public uploads.
- Bind additional database lookups and refresh the bundled support application.
1.12.11
- Generic capability-checked download catalog extension API with revision conflicts and atomic option preservation; no AI or paid tool registration.
1.12.10
- Resolve Plugin Check output/input findings, bind account property writes and combined account search filters, keep shortcode parameters as data, and protect provider diagnostics and client IP rate limits.
- Bundle UI/chart libraries locally, document optional services, and remove automatic external IP lookups. Local server GeoIP remains supported.
- Keep Wiki and lead-form constants compatible with PHP 7.4 by defining them on the plugin class.
- Security: authenticate translation requests with ticket/contact proof, protect language refresh with an administrator nonce, bound translation use, and disable object instantiation in legacy metadata readers. Rebuild the Support app with ticket PIN authentication.
1.12.9
- Setup: authenticated account settings include callback fingerprints so connected plugins can detect a different selection without disclosing private callback URL values.
- Security: log Remote Connect updated property names only; private callback URL values are not written to the update log. Advertise private_callback_push support so connected sites can migrate private callbacks safely.
- Security: escape login form values, discard unverified submitted usernames and never reflect passwords.
1.12.8
- Fixed external Lead Form embeds to load their REST configuration from the Support CRM origin, rather than from the plugin directory.
- Added GA4/dataLayer form-view, form-start, and recorded-lead events; first-party landing/referrer/campaign attribution; cross-domain click-ID forwarding; mobile-friendly multi-select chips; and native input validation.
1.12.7
- Added an approved Lead Form integration API for Site Manager Pro agents, including configured field validation and safe embed-shortcode retrieval.
1.12.6
- Added per-lead-form editable defaults for selected departments and custom fields, including text, textarea, select, multiselect, and toggle controls.
1.12.5
- Added centrally managed, JavaScript-embedded Lead Forms with configurable CRM fields, opaque redirect prefills, analytics, retention controls, rate limiting, and reCAPTCHA support.
1.12.4
- Moved screenshots to SVN assets and updated WordPress.org support metadata.
- Replaced direct asset file tags with WordPress enqueue APIs in app and admin loaders.
1.12.3
- Improved Support Wiki Markdown rendering for tables, images, relative links, dividers, Fomantic UI-compatible classes, page-scoped Markdown styling, and WordPress auto-paragraph normalization
- Documented Site Manager agent-guide discovery for Live Support Tickets CRM tools
- Added VideoWhisper Site Manager integration hooks for CRM message notifications, safe account DB metadata, and external account statistics
- Added Site Manager contact summary support for account ownership counts used in admin CRM contact lists
1.12.2
- Fix: DB migration bump to add missing organizationId column to vws_contacts table
1.10
- Google tracking gtag for main events: contact view/new/confirm, conversation view/new, message new, form view/submit
- Tags
1.9
- Option to allow visitors start conversation before confirming contact (resulting in pending conversation)
- Counters for new and pending conversations in conversation list
- Support can see how many conversations a contact openeded and browse these
- Filter conversation list by status, department, contact
- Sort conversation list by status, created, updated
1.8
- Add/Remove contacts from conversations
- Reply to messages in tickets
- Set custom conversation/message price for MicroPayments support with videowhisper_support_micropayments
- Unsupported email provider domains (disable domains with email issues or common for spammers)
- Access contact fields from backend conversation view, by clicking contact
1.7
- Multilanguage conversations (each message can be in different language)
- DeepL integration for translating messages on request
1.6
- Create new converation for specific contact (registered or not registered) and send notification to join
- Invite by email to fill form, open conversation with specific department
- Sort contacts by last form update
- Canned messages/responses
1.5
- Insert audio/video recordings in conversations: webcam, screen, microphone
- Insert file uploads in conversations
1.4
- Custom fields can be added to departments and filled when starting conversations or associated to contacts with forms
- Link parsing in conversation messages & custom fields
- Forms enable contacts to fill and update contact fields
1.3
- MicroPayments integration for paid support: clients pay on request and providers when they answer
- Conversation management (close, delete)
1.2
- Custom support departments for website / report content / contact content owner / contact user
- Integrate Report Content for any post types
- Integrate Contact Owner for any post types
- Contact Creator in BuddyPress/BuddyBoss profile for configurable roles
- Floating support buttons (contact, new messages) on all pages (can be disabled)
- New message counter in backend (site support) and frontend (for creators)
1.1
- First release





