Inside the “Download Plugin” file

🔍

The Download Plugin button under HelpWP -> Settings -> AI -> Chatbot packages the chatbot embed snippet into a tiny single-file WordPress plugin. This is the easiest way to install the chatbot on a customer’s site – they never edit theme files or paste code.

What you get

Clicking the button downloads helpwp-chatbot.zip. Inside the zip is a single PHP file – helpwp-chatbot.php – with a standard plugin header and one function that prints the chatbot script tag in the site footer.

The generated file is roughly:

<?php
/**
 * Plugin Name: HelpWP Chatbot
 */
add_action( 'wp_footer', function() {
    ?>
    <script
        src="https://helpwp.dev/cdn/chat.min.js"
        data-site-key="YOUR_SITE_KEY"
        data-agent-name="Luna"
        data-primary-color="#1a6c52"
        ...
        defer
    ></script>
    <?php
} );

Every data-* attribute you configured on the settings page is baked into the generated file at the moment you click Download Plugin. If you change settings later, re-download to get an updated zip.

Installing it on a customer site

1. In the customer’s WordPress admin, go to Plugins -> Add New -> Upload Plugin.
2. Pick the helpwp-chatbot.zip file.
3. Click Install Now, then Activate.

The chatbot launcher appears in the footer on every page. No further configuration needed; the plugin has no settings page of its own.

Updating the embed

There is no auto-update mechanism. To change the agent name, color, business hours, etc. on a deployed site:

1. Adjust the settings on your HelpWP admin.
2. Re-download helpwp-chatbot.zip.
3. On the customer site, deactivate and delete the old plugin, then upload the new one. (Or upload over the existing wp-content/plugins/helpwp-chatbot/ folder via SFTP.)

When to use this vs paste-the-snippet

• Use the plugin when you want a non-technical site owner to install the chatbot themselves and you do not want them touching theme files.
• Paste the snippet when you (or your developer) already manage the site’s footer, or when the site is not WordPress.

Both routes produce the exact same widget on the front-end.