BeesChat

Description

BeesChat by BeesBlaze adds a floating WhatsApp lead form to a WordPress website. Visitors enter their details before opening WhatsApp with a prefilled message. The website saves submitted enquiries locally and can export them as CSV.

Features include:
* Floating WhatsApp button for supported pages and mobile screens.
* Custom form builder with editable fields and dropdown options.
* UTM campaign and ad click identifier capture with landing page attribution.
* WordPress lead storage and CSV export.
* Adjustable widget appearance, schedules, triggers, and targeting.
* Optional GA4 events and GTM dataLayer integration.
* Optional, consent-based installation telemetry (disabled by default).

Product details and feature requests: https://www.beesblaze.com/ (the dedicated product page must be made public before approval)

External Services

WhatsApp (Meta)

When a visitor submits the enquiry form, BeesChat saves the submitted fields to the WordPress database and then opens a WhatsApp wa.me link with a prefilled message. Form field values, any configured message introduction, and selected campaign/page attribution are included in that link. The visitor chooses whether to send the message. WhatsApp may process the information when its website or application opens.
Terms: https://www.whatsapp.com/legal/terms-of-service
Privacy: https://www.whatsapp.com/legal/privacy-policy

Google Analytics (optional)

When the site administrator configures a GA4 Measurement ID, BeesChat can load Google’s gtag.js library from googletagmanager.com and transmit widget-open, form-submitted and lead-saved events. The event stream and request metadata may be processed by Google. The plugin also supports GTM dataLayer events. Administrators must manage any required visitor consent.
Terms: https://marketingplatform.google.com/about/analytics/terms/us/
Privacy: https://policies.google.com/privacy

Installation telemetry (optional)

Disabled by default. Only if an administrator opts in and supplies an HTTPS collection endpoint, the plugin transmits a randomly generated installation identifier, plugin version, event type and UTC timestamp to the administrator-configured endpoint. That endpoint’s provider and applicable policies depend on the address supplied by the administrator. The endpoint operator may receive network metadata such as IP address. Disabling telemetry clears the locally stored identifier. No submitted lead data is intentionally included.

Cloudflare (optional)

Country targeting may use the CF-IPCountry HTTP header supplied by the site’s Cloudflare configuration. BeesChat does not initiate a separate Cloudflare API request.
Terms: https://www.cloudflare.com/website-terms/
Privacy: https://www.cloudflare.com/privacypolicy/

Source Code and Build Instructions

BeesChat ships with the human-readable source for its frontend and admin assets.
JavaScript source files are included directly in assets/admin.js,
assets/form.js, assets/widget.js, and assets/leads-admin.js.
CSS source files are included directly in assets/admin.css and assets/form.css.
No bundled or proprietary third-party JavaScript libraries are included,
and no compiler, bundler or minification step is required to build the plugin.
The JavaScript and CSS files in the plugin ZIP are the editable source files
used by WordPress at runtime. You can review and modify them directly.

Privacy

BeesChat stores information submitted through the form in the site’s WordPress database, including customer-provided fields, campaign parameters, referring page and landing-page information. When the visitor opens WhatsApp, the selected details are included in a prefilled message that the visitor can choose to send. The site administrator is responsible for a suitable privacy notice, retention rules, and lawful collection of personal data.

If the site administrator enters a GA4 Measurement ID or enables analytics through Google Tag Manager, event data may be sent to Google according to the site’s configured analytics settings. Administrators should obtain any legally required consent before enabling such analytics.

Optional installation analytics are disabled by default. If an administrator explicitly opts in and enters an HTTPS collector endpoint, BeesChat may send an installation identifier, plugin version, event type and UTC time to that endpoint. This telemetry does not intentionally include submitted lead contents or campaign parameters. The receiving server may see network metadata such as the source IP address. Turning off telemetry stops subsequent transmissions and clears the locally saved identifier.

Email Notifications

Administrators can opt in to email notifications for newly saved leads. Configure up to 10 recipients and customize the subject in Leads and Analytics. Each notification contains submitted fields, campaign attribution, landing and referral details. Uses wp_mail; delivery depends on the site’s mail configuration. A test email button is provided.

2.7.5

  • Hide the Conditional Fields for Elementor Form review promotion on BeesChat pages without suppressing WordPress system notices.

2.7.4

  • Added optional existing WhatsApp link interception and #open-beeschat button trigger.

Screenshots

Installation

  1. Upload the plugin through Plugins > Add New > Upload Plugin, or install it from the WordPress plugin directory once approved.
  2. Activate BeesChat.
  3. Go to BeesChat in the WordPress dashboard.
  4. Enter your WhatsApp number with its country code and save.
  5. Configure form fields, appearance and targeting as needed.
  6. Optionally add [beesblaze_whatsapp_form] to a page for an inline form.

FAQ

Does BeesChat send WhatsApp messages automatically?

No. Visitors must confirm and send the prefilled message in WhatsApp. Leads saved by the plugin are not proof that a WhatsApp message was delivered.

How are enquiries stored?

Submitted details and campaign attribution are stored in the site’s WordPress database. Administrators can export CSV records.

Can I track GA4 events?

Yes. BeesChat can emit beeschat_widget_open, beeschat_form_submitted and beeschat_lead_saved through its configured tracking integration. Avoid configuring duplicate tags that count the same interaction twice.

Reviews

13 de noviembre, 2026
BeesChat makes WhatsApp lead capture simple for WordPress websites. It offers a customizable WhatsApp chat widget, flexible enquiry forms, and a built-in lead management dashboard. The UTM tracking feature helps identify where leads come from, while email notifications and CSV export make managing enquiries easier. A useful plugin for businesses looking to collect and manage WhatsApp enquiries directly from their WordPress website.
Read all 1 review

Contributors & Developers

“BeesChat” is open source software. The following people have contributed to this plugin.

Contributors

Translate “BeesChat” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

3.3.2

  • Reduced the promotional header box to fit its content without reducing text size.
  • Added an Event Tracking heading and a neutral WordPress.org review link on the About screen.
  • Simplified the version badge to show the version only.

3.3.1

  • Added a compact, responsive BeesBlaze promotional banner to the settings header with tracked contact link.

3.3.0

  • Updated BeesChat admin branding with a single BeesChat logo derived from the approved artwork.
  • Refreshed settings wizard, form field editor, live preview and Leads interface styling.
  • Preserved the existing WhatsApp widget, form configuration, lead storage and basic CRM functionality.

3.2.5

  • Unslash posted settings with wp_unslash() before applying field-specific sanitization, addressing Plugin Check MissingUnslash.

3.2.4

  • Cached the custom lead detail lookup and documented its use of a prepared SQL query.
  • Clarified per-field sanitization of nested settings and retained nonce verification.

3.2.3

  • Addressed Plugin Check output-escaping and settings-notice nonce issues.
  • Documented intentional use of wpdb insert and CSV output streaming.
  • Removed extra root Markdown documentation; all source guidance remains in readme.txt.

3.2.2

  • Fixed PHP 7.4 compatibility in lead details by replacing a PHP 8-only function.

3.2.1

  • Reformatted JavaScript assets as human-readable source for WordPress.org review.
  • Documented bundled source files and build requirements.

2.9.0

  • Replaced footer inline CSS with enqueued stylesheet rules.
  • Removed arbitrary Custom CSS option.
  • Expanded disclosure of external services and updated submission metadata.

2.6.1

  • Updated WordPress.org licensing metadata and readme documentation.
  • Retained v2.6 plugin functions.

2.6.0

  • Compact form builder and improved admin preview.