How to add an AI chatbot to WordPress or Shopify

A website chatbot is commonly added with a short script supplied by the service. Tellvira gives you a bot-specific snippet in the dashboard. Copy the whole snippet, including its attributes, and place it in a website area intended for custom code. You do not need to invent a URL or a bot identifier.

Understand what the script does

The script loads the website assistant for your configured bot. It does not copy your store database into Tellvira, connect to a booking calendar, or grant access to private orders. The assistant's answers come from the website pages, FAQs, and uploaded documents you provide in the dashboard. Treat the snippet as website code and install it only where you are allowed to edit the site.

The dashboard instruction is: 'Paste this snippet before the closing body tag.' On hosted platforms, the equivalent is often a footer or body-end custom code area. Keep the complete generated snippet intact. Avoid adding unknown script attributes or copying a sample identifier from another website.

Add it to WordPress or WooCommerce

A footer-scripts plugin can place the snippet without changing the theme's files. In the plugin's settings, choose the site-wide footer or body-end area, paste the full dashboard snippet, save, and view a published page. Plugin labels vary, so follow the documentation for the one your site already uses. Check that the snippet is added once, rather than once by the plugin and again by the theme.

If your team edits theme code instead, use a child theme or another maintainable method. Changes made directly to a theme may be lost during updates. WooCommerce uses the same WordPress website placement for the assistant; installing the script does not give it access to WooCommerce orders. Order-specific problems should be emailed to your support team.

1. Copy the exact snippet from your bot's Install page
2. Choose a supported site-wide footer location
3. Save, publish, and inspect a public page
4. Test a routine answer and an emailed inquiry

Add it to a Shopify storefront

Shopify provides a theme code editor for stores that need code changes. In the active theme, use the supported code location near the closing body tag and paste the complete snippet once. Work in a duplicate theme first if your store uses a customized theme, then preview and publish according to your normal process. A theme change may need the snippet added again.

Test on a product page, a collection page, and a policy page. The assistant on your storefront does not automatically run inside hosted checkout. The online store solution explains the useful boundary: it can answer published shipping, returns, sizing, and care questions, then collect order-specific requests for staff. It cannot see an order's status or live inventory.

Use the code areas on other platforms

Webflow has a Footer code area for custom code. Wix offers custom code placement at the end of the body on eligible sites. Squarespace offers code injection for supported plans and site configurations. Names and availability can vary by plan and editor version, so use the current help for your own account before making changes.

Place the snippet in a site-wide area if you want the assistant on every page. A page-specific area is useful only when you deliberately want narrower coverage. After saving, publish the site and check a real URL. Some editors suppress third-party scripts in preview, so the public page is the better installation test.

Check performance and page behavior

A new script should not cover a checkout button, mobile navigation, or accessibility controls. Open the site at phone width, use the keyboard to reach the launcher, and confirm the page remains readable. Check several templates rather than only the homepage. Look for duplicate launchers, which usually mean the snippet was inserted in two places.

If your site uses a content security policy, ask the person who manages it to review the script source. If the assistant appears only on some pages, compare their shared theme and footer settings. Keep a record of where you installed the snippet so the next theme or platform update does not silently remove it.

Test answers and requests separately

An installation can be technically successful while the content is incomplete. Ask a question that is answered in an approved FAQ, then ask one whose answer is missing. The first should reflect the supplied source; the second should state the limit or offer staff follow-up. Finally, submit a request and verify the business receives the email.

Use the FAQ template to prepare those first answers. If your site serves a dental practice, read the after-hours front desk guide before adding starter questions so you do not invite health details into chat.

Keep the setup maintainable

Document who owns the site code, who updates assistant content, and who checks inquiry emails. When a theme is replaced or a site is redesigned, recheck the launcher. When policy text changes, update the knowledge source and test the affected answer. A useful assistant depends as much on current content and staff follow-up as on the script itself.

If you are choosing a plan, see pricing. For a placement or setup question, contact Tellvira. Starting with a few verified FAQs and one reliable handoff is easier to maintain than publishing every possible answer at once.

Avoid common placement mistakes

A script copied from the wrong bot can load a different greeting and source content than expected. Confirm the bot name in the dashboard before copying. A snippet pasted into a visible text block may display code to visitors instead of running it. Use a code injection or footer script field designed for scripts, then inspect the public page.

Watch for duplicate installation after a redesign. A developer may add the script to the theme while a marketing plugin also inserts it. If two launchers appear, find both placements and keep one. Do not “fix” duplication by editing the generated bot identifier or adding unrecognized attributes.

Keep content and installation separate

A correctly placed script only makes the assistant available. It does not supply accurate answers by itself. Add your own website pages, FAQs, and approved documents in Tellvira, then test the questions visitors are likely to ask. For a store, include shipping and returns policies. For a practice, include public office details but keep health information out of chat.

When a website platform changes its editor or theme, review the code placement again. When your business changes a price or policy, update the supplied source content. Assign these tasks to named people; otherwise a launcher may keep working while its answers quietly become stale.