How to install Presbot on your website

Before you install Presbot

Before adding Presbot to your website, make sure your assistant is ready for visitors.

Review:

• Your assistant name and business details
• Your Quick topics
• Your saved answers
• Your business Knowledge
• Your lead capture flow
• Your contact and follow-up information

If you are still preparing your assistant, start with how to create your first Presbot assistant.

What you need to install Presbot

Presbot is added to a website using a small embed code connected to your assistant.

You will need:

• Access to your Presbot account
• An assistant that is ready to publish
• Permission to edit your website
• Access to your website builder, content management system, or source code

If someone else manages your website, you can send the installation code and these instructions to that person.

Find your Presbot installation code

Sign in to Presbot and open the assistant you want to install.

Go to the installation or website setup area for that assistant. Copy the provided embed code exactly as it appears.

The code identifies your assistant and loads the visitor experience on your website.

Do not remove or rewrite parts of the code unless Presbot specifically instructs you to do so.

Choose where to add the code

For most websites, the Presbot code should be included in the shared layout used across the site.

This allows the assistant to appear on every page rather than only one page.

Common locations include:

• A global footer code area
• A site-wide custom code setting
• The page template before the closing body tag
• A shared layout or theme file
• A tag management tool used across the website

The exact location depends on how your website is built.

Install Presbot on a custom HTML website

If your website uses regular HTML files, open the shared page template or each page where you want Presbot to appear.

Paste the Presbot embed code near the end of the page, before the closing </body> tag.

For example:

<!-- Your page content -->

<!-- Paste your Presbot embed code here -->

</body>
</html>

Save the file and publish the updated website.

Install Presbot through a website builder

Many website builders include a place for site-wide custom code.

Look for settings with names such as:

• Custom code
• Footer code
• Code injection
• Tracking code
• Site scripts
• Before body closing tag

Paste the complete Presbot embed code into the site-wide footer or body area, then save and publish your changes.

Avoid placing the code in a visible text block. It should be added through a code or script setting.

Install Presbot on WordPress

WordPress websites can add site-wide scripts in several ways.

Depending on your setup, you may use:

• A theme setting for custom footer code
• A trusted header and footer script plugin
• A child theme template
• A tag management plugin

Paste the Presbot embed code into the footer or body script area so it loads across the site.

Avoid editing the main theme directly when the change could be removed by a future theme update.

After saving, clear any WordPress cache or optimization cache before testing.

Install Presbot on Shopify

For a Shopify storefront, the code should normally be placed in the theme layout so it can appear throughout the store.

Open your active theme’s code editor and locate the main layout file. Paste the Presbot embed code before the closing </body> tag.

Save the theme and test the live storefront.

Be careful when editing theme files. Keep a copy of the original code or duplicate the theme before making changes.

Install Presbot with Google Tag Manager

You may also be able to load Presbot through Google Tag Manager or another tag management system.

Create a custom HTML tag and paste the complete Presbot embed code into it.

Configure the tag to run on the pages where the assistant should appear. For a site-wide installation, use an all-pages trigger.

Preview the tag first, then publish the container after confirming that Presbot loads correctly.

Publish your website changes

Saving a code change does not always make it visible on the live website.

Depending on your platform, you may also need to:

• Publish the website
• Deploy the latest version
• Publish the active theme
• Publish your tag manager container
• Clear a website cache
• Clear a content delivery network cache

Confirm that you are testing the public website, not only an unpublished editor preview.

Open your website in a private window

After publishing, open your website in a private or incognito browser window.

This reduces the chance that an older cached version of your site will affect the test.

Check that:

• The Presbot launcher appears
• The launcher does not cover important page content
• The assistant opens when selected
• The assistant name and welcome message are correct
• Quick topics are visible
• Messages can be entered and submitted

Test on more than one page

If Presbot should appear throughout your website, test several page types.

For example:

• Home page
• Service or product page
• Pricing page
• Contact page
• Blog or article page
• Checkout or account page, when appropriate

If Presbot appears on only one page, the embed code may have been added to a page-specific block instead of the shared site layout.

Test the mobile experience

Open the website on a phone or use your browser’s mobile preview.

Confirm that:

• The launcher is easy to select
• The assistant fits within the screen
• The close button is visible
• The message field is usable
• The keyboard does not hide important controls
• Quick topics remain readable
• The assistant does not block navigation or purchase buttons

Mobile testing is important because a layout that works on a desktop may feel crowded on a smaller screen.

Test Quick topics and saved answers

Open each important Quick topic and confirm that it produces the expected response.

Check for:

• Clear topic labels
• Correct saved answers
• Working links
• Current pricing or policy information
• A useful next step

Review how to write effective Quick topics and how to write clear saved answers when the visitor flow needs improvement.

Test Smart Assistant questions

Ask questions that are not exact copies of your Quick topics.

Try different ways of asking about:

• Your services
• Your business hours
• Your location or service area
• Pricing
• Booking
• Policies

Confirm that the answers match the information your business has provided.

If an answer is too general or incomplete, review how to add useful Knowledge and how Smart Assistant uses your Knowledge.

Test lead capture from beginning to end

Complete a test follow-up request as though you were a visitor.

Confirm that:

• The lead capture option is easy to find
• Each question is clear
• The form accepts valid contact details
• The confirmation message appears
• The test lead is saved
• Your team can review the submitted details

Use an email address or phone number your team recognizes as a test.

Review how to set up lead capture in Presbot and how to review and manage captured leads for more guidance.

Check your browser console for errors

If Presbot does not appear, your browser’s developer tools may show a useful error.

Open the browser console and reload the page.

Look for messages related to:

• A blocked script
• An incorrect embed code
• A content security policy
• A browser extension
• A JavaScript error elsewhere on the page
• A network request that failed

You do not need to understand every console message. Save the relevant error text when asking your website developer or support contact for help.

Common reason: the code was pasted as text

Some website editors display code as visible page content instead of running it.

If visitors can see the Presbot code printed on the page, remove it from the text editor and place it in a custom code, script, footer, or HTML area.

Common reason: the website was not republished

Your changes may exist only inside the website editor.

Publish or deploy the website, then reload the public page in a private browser window.

Common reason: caching

A cache may continue serving an older version of your website.

Clear any relevant:

• Website builder cache
• WordPress cache
• Server cache
• Content delivery network cache
• Browser cache

Then reload the page.

Common reason: the code is only on one template

If Presbot appears on some pages but not others, compare the templates used by those pages.

The embed code may have been placed in one page template rather than the shared site layout.

Move it to the global footer or shared layout when the assistant should appear site-wide.

Common reason: duplicate installation

Installing the embed code more than once may cause the launcher or assistant to load twice.

Check your:

• Theme files
• Custom code settings
• Plugins
• Tag manager
• Page-specific scripts

Keep only one active site-wide installation unless you have a specific reason to do otherwise.

Common reason: security settings block the script

Some websites use a content security policy or privacy tool that limits external scripts.

If the browser reports that the Presbot script was blocked, your website administrator may need to update the site’s allowed script or connection sources.

Share the browser error and your Presbot embed code with the person who manages your website security settings.

Check whether a consent tool delays Presbot

Cookie consent and privacy tools may prevent optional scripts from loading until a visitor makes a choice.

Test both before and after accepting the relevant consent category.

Make sure the behavior matches your privacy settings and legal requirements.

Choose which pages should show Presbot

Presbot does not have to appear on every page.

You may choose to exclude it from pages where it could interrupt a sensitive or focused process, such as:

• Payment pages
• Account security pages
• Private customer portals
• Application forms
• Pages with a separate support experience

Make this decision based on the visitor experience and your business needs.

Review the launcher position

Confirm that the Presbot launcher does not overlap:

• A mobile menu
• A checkout button
• A cookie consent control
• An accessibility control
• A contact button
• Another chat or support widget

If several floating controls appear in the same corner, the page may become difficult to use.

Avoid running multiple visitor assistants

Two chat or assistant tools on the same page can confuse visitors.

They may also overlap visually or compete for attention.

Before publishing Presbot, decide whether an older chat, messaging, or lead capture widget should be removed.

Confirm that links open correctly

Test every important link inside your saved answers and assistant content.

Confirm that:

• Internal links go to the correct page
• External links use the correct destination
• Booking links are current
• Email and telephone links work
• Links do not point to unpublished pages

Review your assistant after installation

Installation is not the final step.

After visitors begin using Presbot, review:

• Common visitor questions
• Weak or incomplete answers
• Quick topics visitors select often
• Captured lead quality
• Questions that should become saved answers
• Business information that needs updating

Use those patterns to improve the assistant over time.

Installation checklist

Before considering the installation complete, confirm that:

• You copied the correct embed code
• The code is installed only once
• The website changes are published
• The launcher appears on the intended pages
• The assistant opens and closes correctly
• The desktop experience works
• The mobile experience works
• Quick topics and saved answers are correct
• Smart Assistant responses are accurate
• Lead capture works from beginning to end
• Links and contact details are current
• The assistant does not cover important page controls

Next steps

After installing Presbot, review how to write effective Quick topics, how to write clear saved answers, and how to add useful Knowledge.

You can also review how to set up lead capture and how to manage captured leads.

Create your Presbot assistant or compare Presbot plans.