VisWapp Chat Widget

Paste the install snippet from your VisWapp account and the chat bubble appears on your site. No code to edit.

• Paste the snippet once; the plugin reads your widget ID and settings from it.
• Show the widget on every page, every page except some, or only some pages.
• Hide it from roles such as Administrator or Shop manager.
• Optional: identify logged-in customers so chats arrive with their name, email and phone (WooCommerce billing phone supported). Identities are signed on your server with your Identity secret, which never reaches the browser.
• When an identified customer logs out, their chat is cleared from that browser.
• Login with WhatsApp: a “Continue with WhatsApp” button on the WordPress login page, WooCommerce My account and checkout, or anywhere with the [viswapp_login] shortcode. WhatsApp opens with a message ready; the customer taps send and is logged in. Existing users are matched by WhatsApp number or WooCommerce billing phone; new numbers can get an account automatically.
• Lead forms: add a form from VisWapp → Web Forms to any page with the “VisWapp form” block or the [viswapp_form] shortcode, in the page or as a popup button. Every response becomes a VisWapp contact and can create a lead, send a WhatsApp message, add a Google Sheet row or call your webhook.
• Abandoned cart recovery (WooCommerce): carts are sent to VisWapp once the shopper’s phone or email is known, and VisWapp sends a WhatsApp reminder with a link that restores the cart and opens checkout.

Abandoned cart recovery

The WooCommerce tab appears when WooCommerce is active.

What is sent: whenever the cart changes (add, remove, quantity, coupon, emptied) or the shopper’s contact details become known, the plugin sends one signed cart.updated to your VisWapp Delivery URL at the end of that page request (in the background, so pages don’t wait). Nothing is sent until a phone number or email is known, and an unchanged cart is not sent again on refresh. When the order is placed, cart.converted is sent with the order number. Requests are signed like WooCommerce webhooks (X-WC-Webhook-Signature, HMAC-SHA256 with the Webhook secret).

Where the phone comes from: logged-in customers use their WooCommerce billing phone and email. Guests are captured on the checkout page as they type: the classic checkout (billing phone, email, first and last name) and the block checkout (email and the billing or shipping phone and name) both post the fields to this site, which keeps them in the WooCommerce session. Numbers without a country code get the billing country’s (or the store’s) calling code.

Consent: optionally show a “Send me cart and order updates on WhatsApp” checkbox at checkout (your wording), and also on registration and My Account → Account details. The answer is saved on the customer’s account and sent with every cart, so returning customers don’t have to tick it again; unticking it in My Account withdraws consent. Opting in through Login with WhatsApp counts as consent. A VisWapp journey set to “Only shoppers who opted in” only reminds shoppers who said yes. The block checkout shows the checkbox with WooCommerce 8.9 or later.

Reminders: carts left idle become abandoned in VisWapp and start your “Abandoned cart recovery” journey (reminder, second nudge, team alert). When the shopper orders, the journey stops. Without a journey, VisWapp can still send one template mapped to “Cart abandoned” in Integrations → WooCommerce → Store events.

The cart link: each reminder contains a link such as https://yourstore.com/?viswapp_recover=…. It rebuilds the cart (replacing what is in the browser’s cart), fills in the shopper’s details, applies the optional Recovery coupon and opens checkout. Links work for 14 days and stop working once the order is placed; an expired link opens the cart with a notice.

Cart identity: each cart is reported under the WooCommerce session’s customer id for guests, or u for logged-in customers. A cart keeps the key it was first reported under, also when the guest logs in, so it stays one cart in VisWapp; after an order the next cart starts fresh.

Developers can change or skip a body with the viswapp_woo_cart_payload filter:

add_filter( 'viswapp_woo_cart_payload', function ( $payload, $topic ) {
    return $payload; // return null to skip sending
}, 10, 2 );<h3>Lead forms</h3>

The block and the shortcode print a placeholder that the VisWapp forms script (f.js) fills in. The script is added only to pages that show a form, and each form is drawn in its own isolated area, so your theme’s styles don’t change it.

[viswapp_form id="vw_frm_…"]
[viswapp_form id="vw_frm_…" mode="popup" label="Get a quote" position="left"]

• id: the form key from VisWapp → Web Forms → Share (required).
• mode: inline (the form in the page, default) or popup (a floating button in the form’s colour that opens it).
• label and position: the popup button’s text (default: the form title) and corner (right or left).

The form’s look, questions, thank-you message and what happens with each response are all set in VisWapp; changes show on your site straight away. Responses record the page they came from and its UTM tags.

Developers can change the printed markup with the viswapp_form_markup filter ($html, $key, $atts); its output is checked against an allow-list.

External services

This plugin connects your site to VisWapp (https://viswapp.com), a WhatsApp Business messaging service. Nothing is loaded or sent until you enter your VisWapp details on Settings → VisWapp, and each feature below works only when you turn it on.

• Chat widget. On the pages you choose, visitors’ browsers load the widget script from the address in your install snippet (by default https://cdn.viswapp.com/w.js) and talk to your VisWapp Data API address. The widget sends the page address and referrer, the page and browser language, basic device details (browser, screen size, time zone), UTM parameters and what the visitor types in the chat. With “Identify logged-in users” on, the logged-in user’s ID, name, email and phone number are sent, signed on your server.
• Login with WhatsApp. On the login, My account and checkout pages (and wherever you place [viswapp_login]) browsers load login.js from your VisWapp sign-in address. When a customer signs in, your server sends the one-time code and your client credentials to that address (/oauth/token) and receives the customer’s verified WhatsApp number.
• Lead forms. On pages that show a [viswapp_form] shortcode or a VisWapp form block, browsers load f.js (by default from next to the chat widget script, e.g. https://cdn.viswapp.com/f.js) and read the form from your VisWapp API address. When a visitor submits, their answers, the page address and referrer and the page’s UTM parameters are sent to VisWapp. In the block editor, the form’s title is read from the same address for the preview.
• Abandoned cart recovery (WooCommerce). Once a shopper’s phone number or email is known, your server sends the cart (products, quantities, prices, totals, cart link) and the shopper’s name, phone number, email, country and marketing consent to your VisWapp delivery URL, and again when the cart changes or the order is placed.

VisWapp terms of service: https://viswapp.com/terms-conditions
VisWapp privacy policy: https://viswapp.com/privacy-policy

Privacy

Lead form answers (for example name, phone number and email) are sent straight from the visitor’s browser to VisWapp and are not stored in WordPress. Mention your forms in your privacy policy, and add a consent checkbox to forms that lead to WhatsApp messages.

With abandoned cart recovery on, cart contents (products, quantities, prices, totals) and the shopper’s name, phone number and email address are sent to VisWapp so WhatsApp cart reminders can be sent. The plugin adds suggested text to Settings → Privacy → Policy guide; add it to your privacy policy. Use the consent checkbox where the law requires opt-in for marketing messages. Cart links are stored on your site for 14 days.