--- title: WordPress WhatsApp Support Pro — Installation Guide description: "# Overview The Resource Master name refers to the WeCreativez product currently documented as WordPress Support Using WhatsApp. It adds floating WhatsApp support, multiple agents, schedules, page targeting, analytics, GDPR messaging, and generated chat buttons. **When to use it.**Use it…" url: "https://nippylaunch.com/docs/wordpress-whatsapp-support-pro-installation-guide/" updated: "2026-08-16" category: "Resource Library / Communication & Utility" --- # WordPress WhatsApp Support Pro — Installation Guide # Overview The Resource Master name refers to the WeCreativez product currently documented as WordPress Support Using WhatsApp. It adds floating WhatsApp support, multiple agents, schedules, page targeting, analytics, GDPR messaging, and generated chat buttons. **When to use it.**Use it when visitors should start a WhatsApp conversation with a relevant support or sales contact directly from selected WordPress pages. # Before You Begin **Platform compatibility.**Use a WordPress and PHP combination supported by the current developer release. Minimum versions can change; verify the current official product page or plugin/theme metadata before production deployment. Do not bypass an activation or compatibility warning without identifying its cause. ## Requirements and dependencies - **-**A supported WordPress installation. - **-**A WhatsApp-capable phone number for each agent, entered in international format. - **-**Consent/privacy language appropriate to opening a third-party messaging service. - **-**The correct installable plugin ZIP; marketplace packages may contain an inner Plugin/plugin.zip file. ## Pre-installation checks - **-**Back up the site and record existing chat, analytics, consent, and floating-widget code. - **-**Confirm agent numbers, working hours, ownership, and escalation process. - **-**If the archive is a CodeCanyon distribution package, extract it once and locate the inner installable plugin ZIP. # Installation 1. 1. Go to [**Plugins**](https://nippylaunch.com/mp-files/wordpress-whatsapp-support-pro.zip/)> Add New Plugin > Upload Plugin. 2. 2.[Upload the installable ZIP](https://nippylaunch.com/mp-files/wordpress-whatsapp-support-pro.zip/)—use the inner Plugin/plugin.zip when the official marketplace package has that structure—then install and activate it. 3. 3. Open the plugin's WhatsApp support settings. 4. 4. Create at least one support person/agent and enter the number with country code. 5. 5. Publish the widget on a limited test page before enabling it site-wide. # License Activation 1. 1. If the installed version provides a license or purchase-code screen, use only a valid developer-issued entitlement and verify it through the official interface. 2. 2. Do not treat the resource archive as proof that a CodeCanyon purchase code, automatic updates, or direct support is included. **Important.**A premium download does not automatically establish ownership of the original developer's account, license key, automatic-update service, cloud features, or direct support. Use only [Credentials](https://nippylaunch.com/encyclopedia/credentials/) that are valid for this site and were supplied through an authorized account or an explicit [Nippy Launch](https://nippylaunch.com/encyclopedia/nippy-launch/) entitlement. # Initial Setup 1. 1. Configure layout, colors, icon, desktop/mobile behavior, offsets, popup timing, and right-to-left behavior when needed. 2. 2. Add agent name, title, number, schedule, and a useful prefilled message. 3. 3. Set page/URL visibility rules and working hours. 4. 4. Configure GDPR text and link the privacy policy using the documented placeholder when applicable. 5. 5. Enable analytics only through one measured implementation and test the resulting event. # Recommended Configuration - **-**Enter numbers in full international format and test both WhatsApp mobile and web. - **-**Use schedules so visitors are not promised an immediate reply outside staffed hours. - **-**Use page-specific agents or messages only when ownership is clear. - **-**Keep the widget away from cookie banners, accessibility controls, and other floating buttons on small screens. - **-**Use documented message placeholders such as page URL/title only after checking that they do not expose private data. # Main Features The installed edition can provide the following primary capabilities. Availability may depend on the active plan, add-ons, and current release. - **-**Floating WhatsApp support widget - **-**Multiple agents and working schedules - **-**Page and URL targeting - **-**Prefilled messages and button generator - **-**Built-in and external analytics options - **-**GDPR/privacy messaging # How to Use It **Practical starting workflow.**Create one sales agent for product pages and one support agent for account-help pages. Restrict each agent to the correct URLs, define working hours, send a test message from desktop and mobile, and confirm the event in the chosen analytics system. # Integrations - **-**Google Analytics and Facebook/Meta tracking options - **-**WooCommerce and page-specific button placement - **-**Optional Dokan integration under the versions documented by the developer - **-**Multilingual and RTL layouts Enable an integration only after its account ownership, permissions, data flow, and failure behavior have been tested. Keep secret [Credentials](https://nippylaunch.com/encyclopedia/credentials/) out of page content and screenshots. # Common Issues & Troubleshooting - **- Chat opens the wrong contact.**Verify the agent's number, page assignment, schedule, and cache. - **- Widget does not appear.**Check device, URL/page filters, schedule, scroll threshold, user role, and CSS stacking. - **- Message text is malformed.**Review international number and supported placeholders; URL-encode only through the plugin workflow. - **- Analytics event duplicates.**Use one analytics path and remove overlapping manual or tag-manager events. - **- Plugin upload reports no valid plugin.**Locate the inner installable ZIP rather than uploading the full marketplace package. If the problem persists, reproduce it on staging, capture the exact error and relevant logs, and compare the behavior with nonessential plugins temporarily disabled. Restore the production site rather than troubleshooting destructively in place. # Updating the Plugin or Resource 1. 1. Back up and review release notes, then update on staging. 2. 2. Test numbers, messages, schedules, page filters, mobile placement, GDPR text, and analytics. 3. 3. Recheck optional WooCommerce/Dokan behavior after their updates. - **-**Confirm that the backup completed and can be accessed independently of WordPress. - **-**Review the official changelog and compatibility notes. - **-**Update during a low-risk window and keep a tested rollback path. - **-**Clear relevant caches and perform the product-specific functional tests listed above. # Uninstallation 1. 1. Document agent configurations and remove any analytics snippets or external integrations no longer needed. 2. 2. Deactivate the widget before deleting the plugin so no cached page continues to advertise unavailable support. 3. 3. Confirm whether plugin data should remain before using any cleanup option. Deactivation and deletion are not the same as data removal. Confirm the product's current cleanup options, [Database](https://nippylaunch.com/encyclopedia/database/) tables, uploaded files, remote data, connected accounts, and continuing external billing or scheduled actions before removal. # Security & Best Practices - **-**Do not place private order or account data in a public prefilled message. - **-**Publish response expectations and privacy terms. - **-**Restrict plugin settings to trusted users. - **-**Review former staff numbers and schedules promptly. - **-**Use unique administrator accounts, least-privilege roles, HTTPS, and multi-factor authentication where supported. - **-**Keep the resource, WordPress, PHP, theme, and dependencies on supported versions. - **-**Store backups and recovery instructions outside the WordPress site. # Final Checklist - ✅The correct resource and developer identity were confirmed. - ✅A restorable backup was created before installation or major configuration. - ✅All required core plugins, themes, services, and accounts are active. - ✅The resource is installed and activated without WordPress or PHP errors. - ✅A valid developer license is connected when one is required and available. - ✅The product-specific initial and recommended settings are complete. - ✅The practical workflow was tested as an administrator and as the intended visitor/customer/member. - ✅Email, payments, webhooks, cron, cache, and integrations were tested where applicable. - ✅Security, privacy, consent, data retention, and access rules were reviewed. - ✅The update and rollback process is documented and owned by a named administrator.