Replace the key with the publishable key from your console."}},{"@type":"Question","name":"Can I embed an AI support widget without replacing my helpdesk?","acceptedAnswer":{"@type":"Answer","text":"Yes. Add the widget beside what you already run for human tickets. Keep your existing stack; use Rinhelp for grounded answers on the site. That is an “add alongside” install, not a switcher project."}},{"@type":"Question","name":"How do I install an AI chat widget on Shopify, Webflow, or WordPress?","acceptedAnswer":{"@type":"Answer","text":"Shopify: Custom Liquid. Webflow: custom code / embed. WordPress: footer or HTML-capable plugin. Same script tag. No app store install required today."}},{"@type":"Question","name":"Will an embedded AI chat widget break my site’s CSS?","acceptedAnswer":{"@type":"Answer","text":"The chat mounts in a shadow root with bundled fonts, so your stylesheet and the widget stay isolated."}},{"@type":"Question","name":"What happens after I paste the script — where do conversations go?","acceptedAnswer":{"@type":"Answer","text":"Every chat lands in your shared inbox. Threads the agent could not answer from your sources are flagged, so you can see what to write next."}},{"@type":"Question","name":"Does the AI invent answers if my pages don’t cover the question?","acceptedAnswer":{"@type":"Answer","text":"No. If confidence is too low, the visitor sees a clear fallback instead of a guess. Supported answers include citations back to the source page."}},{"@type":"Question","name":"Do I need to write frontend code?","acceptedAnswer":{"@type":"Answer","text":"No. The widget is hosted. Style it in the console and paste one script."}},{"@type":"Question","name":"Does live chat stream the answer?","acceptedAnswer":{"@type":"Answer","text":"Yes. Replies stream into the panel as they are generated. Citations appear with supported answers. If confidence is too low, the visitor sees a clear fallback instead of a guess."}}]}
Rinhelp
Start free trial
All posts

Add AI Support With One Script Tag

  • topic

    Setup

  • published

    Sep 08, 2026

  • reading time

    7 min

  • author

    Wilbert Liu

the short version

Add your website in Rinhelp so pages can be indexed, style the chat, and preview a real question. Then paste one script. The agent goes live in a hosted panel—your theme stays yours—and every conversation lands in your shared inbox. Cited answers from indexed pages, or a clear refusal when the pages cannot support the question. You can add the widget beside an existing helpdesk stack; Rinhelp is not a helpdesk replacement.

Paste one script. The agent goes live. Conversations land in your inbox.

That is the whole install story for Rinhelp live chat. You style color, corner, and greeting in the console, preview a real answer from your pages, then drop the snippet the same way you drop analytics. If you already run a helpdesk for human work—Gorgias is the example I hear most—you can leave it alone and add the widget beside it. This is not a rip-and-replace pitch.

When I say “one script tag,” I mean the HTML <script> embed. Not a ticket tag. Not a conversation label. Install.

I keep repeating that because support software has trained us to hear “tag” as chrome on a ticket. This guide is about the opposite job: get a launcher on the page with one line of HTML, then let the constrained agent do the rest.

Here is the shape:

html
<script src="https://rinhelp.com/api/widget.js?key=rhpk_YOUR_PUBLISHABLE_KEY" async></script>

What “one script tag” actually means

You are embedding a hosted chat panel. There is no package to install in your app, no component to wire unless you want a custom mount later, and no theme rewrite. The panel mounts in a shadow root with its own fonts, so your stylesheet and the widget stay out of each other’s way. Your theme stays yours.

It is also not a migration project. You are not moving tickets or history. You are putting a constrained support agent on the pages visitors already use.

The install is the door. What makes the door worth opening is the same product promise as the rest of Rinhelp: answers from indexed pages, citations on supported replies, and a clear stop when confidence is too low. Every thread shows up in the shared inbox.

The three-step install

This matches what you see on the live chat page.

1. Index a source

Paste the website the agent should learn from. Rinhelp crawls that host, uses the sitemap when one exists, and indexes the pages that are useful for support answers. Wait until crawling and indexing finish before you trust the preview.

2. Style the panel

Pick the accent color so the launcher matches the rest of the page. Choose a corner—bottom-right or bottom-left—depending on what else lives there. Write the title, description, and first greeting in your voice. Then ask a real question in the live preview against your indexed sources, before anyone else sees it.

That preview step is the part I refuse to skip. If the agent cannot cite a page you know is in the index, or if it invents an answer on a topic you left blank, you want to learn that in the console—not after the snippet is live on a Friday.

3. Paste the snippet

Copy the generated script tag and drop it on the site:

html
<script src="https://rinhelp.com/api/widget.js?key=rhpk_YOUR_PUBLISHABLE_KEY" async></script>

One asynchronous line is the full install. Conversations start landing in the inbox as soon as visitors open the launcher.

Where to paste it

If you can paste a script tag, you can run the chat.

  • Shopify — Custom Liquid section. There is no Shopify app yet, and you do not need one.
  • Webflow — embed / custom code where you already put third-party scripts.
  • WordPress — theme footer or a header/footer plugin that accepts HTML.
  • Framer — custom code embed.
  • Plain HTML — before </body> is the usual place.

Same line everywhere. Depth and screenshots live on live chat; this guide stays at the job-to-be-done level: paste, load, ask.

A few install objections I hear from technical founders, answered plainly:

  • Will this fight my theme CSS? The panel is hosted and mounts in a shadow root, so your theme stays isolated.
  • Do I need a Shopify app? No. Custom Liquid is enough.
  • Will it invent policies? Supported answers cite pages; below the confidence threshold it refuses.
  • Do I have to change my helpdesk? No—add the widget beside what you already have.

Beside your existing stack

A lot of teams already have something for human tickets. That is fine.

You can add Rinhelp’s widget for the questions your published pages already answer, and keep the tools you already use for the rest. Gorgias is the contrast I use in conversation: keep Gorgias doing ticket work; put cited site chat on the storefront or docs beside it.

What I am not saying: rip out your helpdesk, run a switcher project, or position Rinhelp as an Intercom / Zendesk / Freshdesk / Gorgias replacement. Rinhelp is not a mailbox or ticketing product. Pricing and About already say it has live handoff and a shared inbox, without ticketing maturity. The install pitch is “add alongside,” not “tear out.”

Why the install is worth it

A one-line embed that opens ChatGPT on your site is easy and dangerous. Rinhelp’s install turns on a constrained AI agent:

  • Supported answers cite the page they came from.
  • Below the confidence threshold, the visitor sees a clear fallback instead of a guess.
  • Replies stream into the panel as they generate.
  • Every conversation—including the misses—lands in the shared inbox, so unanswered threads become a content list instead of invisible failure.

Install is how you get there this afternoon. The cite + refuse behavior is why I bother shipping the script at all.

Here is the kicker for small teams: the install does not ask you to become a RAG engineer first. You point at the site you already ship, style a panel, and prove the behavior with two questions—one your pages cover, one they do not. If that loop works, the script tag is just how visitors join it.

If you want the deeper refusal rationale, read why support bots should refuse. For the commercial cite + refuse how-to for buyers, see AI support with citations that refuses when it can’t.

What this is not

Keep the scope honest so the trial is not a mismatch.

  • Page-grounded chat first. This install turns on answers from indexed pages. Connected Shopify order lookup and human-approved refunds are separate surfaces—not part of the one-line install story. Published-page questions—sizing, shipping policy, returns policy, docs—are what this script unlocks on day one.
  • Not a helpdesk or ticket queue. No rip-and-replace of the tools you use for human work. No ticket tagging story. Script tag means HTML install.
  • Not open-web ChatGPT. The agent answers from indexed pages on your site, not from broad model knowledge. That is why citations and refusals exist.

FAQ

How do I add AI support to my website with one script tag?

Add your website in Rinhelp, style the chat, preview a real question, then paste the generated script on your site. Full detail: live chat.

What does a one-line AI chat widget install look like?

html
<script src="https://rinhelp.com/api/widget.js?key=rhpk_YOUR_PUBLISHABLE_KEY" async></script>

Replace the key with the publishable key from your console.

Can I embed an AI support widget without replacing my helpdesk?

Yes. Add the widget beside what you already run for human tickets. Keep your existing stack; use Rinhelp for grounded answers on the site. That is an “add alongside” install, not a switcher project.

How do I install an AI chat widget on Shopify, Webflow, or WordPress?

Shopify: Custom Liquid. Webflow: custom code / embed. WordPress: footer or HTML-capable plugin. Same script tag. No app store install required today.

Will an embedded AI chat widget break my site’s CSS?

The chat mounts in a shadow root with bundled fonts, so your stylesheet and the widget stay isolated.

What happens after I paste the script — where do conversations go?

Every chat lands in your shared inbox. Threads the agent could not answer from your sources are flagged, so you can see what to write next.

Does the AI invent answers if my pages don’t cover the question?

No. If confidence is too low, the visitor sees a clear fallback instead of a guess. Supported answers include citations back to the source page.

Do I need to write frontend code?

No. The widget is hosted. Style it in the console and paste one script.

Does live chat stream the answer?

Yes. Replies stream into the panel as they are generated. Citations appear with supported answers. If confidence is too low, the visitor sees a clear fallback instead of a guess.

Closing

Add the site. Style the chat. Paste one line.

By the end of the afternoon you will know what your content already answers—and, from the flagged conversations, exactly what it is missing.

Keep reading

ProductAI Shared Inbox That Flags the Miss Pile8 min readAccuracyAI Support With Citations That Refuses When It Can’t8 min readShopifyShopify Refund with Human Approval7 min read

Start with the support questions your website can already answer.

Add your site, style the chat, and paste one line into your page. By the end of the afternoon you will know what your content already answers — and, from the flagged conversations, exactly what it is missing.

Start free trial