BeesChat: WhatsApp Chat Widget, Lead Capture & UTM Tracking

By BeesBlaze

★ 5.0/5 (1 ratings)0+ active installationsVersion 3.3.7

Add a WhatsApp chat widget with custom enquiry forms, UTM campaign tracking, lead management, email alerts and CSV export.

Description

BeesChat is a WhatsApp chat widget and lead capture plugin for WordPress. Add a floating WhatsApp enquiry button to your website, collect enquiries using configurable form fields, and open a prefilled conversation in WhatsApp. Visitors choose whether to send their message.

Unlike a basic WhatsApp button, BeesChat also saves submitted leads in your WordPress database, helping you manage enquiries and understand which marketing campaigns generated them.

WhatsApp Chat Widget

  • Add a floating WhatsApp chat button with adjustable size, position and appearance.
  • Show a short enquiry form before visitors open WhatsApp.
  • Set desktop and mobile visibility, display conditions and targeting options.

Lead Capture and Management

  • Configure text fields, email inputs, dropdowns and other enquiry fields.
  • View saved leads in the built-in WordPress Leads dashboard.
  • Search and filter enquiries, update basic lead statuses, and export CSV files.
  • Enable optional lead notification emails.

UTM Tracking and Analytics

  • Capture UTM source, medium, campaign and supported ad click identifiers.
  • Save landing page and referrer information alongside enquiries.
  • Track beeschat_widget_open, beeschat_form_submitted and beeschat_lead_saved with optional GA4 integration or GTM dataLayer events.

BeesChat works as a standalone WordPress plugin. It does not require BeesForm or Bees CRM.

Plugin website: https://www.beesblaze.com/beeschat/

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.

Installation

  1. Install BeesChat from Plugins > Add New, or upload the plugin ZIP.
  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.

Does BeesChat require the WhatsApp Business API?

No. BeesChat opens WhatsApp with a prefilled message and does not require a WhatsApp Business API connection.

Can BeesChat track leads from Google Ads or other campaigns?

Yes. When campaign parameters are present in the visit, BeesChat can store UTM values and supported ad click identifiers with the saved lead.

Does BeesChat replace a full CRM?

No. It includes basic lead management in WordPress. It is not a full customer relationship management system.

Screenshots

Changelog

3.3.7

  • Optimize the WordPress.org listing title, feature descriptions, FAQs and screenshots.
  • Add a seven-day, dismissible admin review reminder with neutral rating language.
  • Track visits from the Plugins page author and plugin website links using UTM parameters.
  • Keep the BeesChat admin interface and mobile WhatsApp behavior from version 3.3.6 unchanged.

3.3.6

  • Open the WhatsApp native app directly on mobile after saving the lead. Keep a wa.me fallback link when the app is unavailable.

3.3.5

  • Faster mobile WhatsApp handoff: only refresh expired nonces and queue email notifications without blocking the visitor.

3.3.4

  • Refresh submission security tokens on cached mobile pages and avoid blank Safari tabs.

3.3.3

  • Fixed mobile widget initialization when browser storage is blocked.
  • Improved the chat panel layout on small screens and fixed input zoom on iOS.
  • Open WhatsApp reliably after saving a lead on mobile without creating a blank tab.

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.