Two Ways to Embed Help & Support

Muin’s help and support is one system with two faces. The same answers, the same knowledge base and the same office queue sit behind both, so it is never a question of which product to buy, only which one a page should show.

	Simple mode	Rich mode
What a visitor sees	A chat bubble in the corner	A full help page: search, topics, articles, and the same chat
Where it fits	Every page of your site	Your Help page, or its own address
Best for	Someone with one question	Someone who wants to look before asking

Simple mode: the chat bubble

Paste this before the closing </body> tag on any page.

<script
  src="https://muin.falaah.ai/embed/widget.js"
  data-type="support"
  data-tenant-slug="your-org"
  data-position="bottom-right">
</script>

data-position accepts bottom-right (the default), bottom-left, top-right or top-left. The snippet you copy from Support Settings already carries the position you saved under Design Portal. If you change the position later, copy the snippet again.

Your own button instead of ours

Add data-hide-launcher and open it from a button you already have. Commands sent before the widget has finished loading are queued, so an early click is never dropped.

<script
  src="https://muin.falaah.ai/embed/widget.js"
  data-type="support"
  data-tenant-slug="your-org"
  data-hide-launcher>
</script>

<button onclick="MuinHelp.open()">Need help?</button>

MuinHelp.open(), MuinHelp.close() and MuinHelp.isReady() are the whole API.

A labelled pill instead of an icon

<script
  src="https://muin.falaah.ai/embed/widget.js"
  data-type="support"
  data-tenant-slug="your-org"
  data-launcher="pill"
  data-launcher-label="Need help?">
</script>

Rich mode: the whole help page, inside your own page

Rich mode is a real help center: a search box that understands the question rather than matching keywords (a parent who types “how much does it cost” finds your “Tuition and fees” article; it is the same retrieval the chat uses, over the full text of your articles), your topics down the side, the articles themselves, the most-read answers, and the same assistant docked on the page.

It has two homes, and you can use both:

1. Hosted, at https://muin.falaah.ai/go/your-org/support. Link it from your site’s menu. Nothing to install.
2. Inline, inside a page of your own site. Add a container where you want it and name that container in the tag:

<div id="muin-help"></div>

<script
  src="https://muin.falaah.ai/embed/widget.js"
  data-type="support"
  data-tenant-slug="your-org"
  data-mode="page"
  data-target="#muin-help">
</script>

The frame is an ordinary block element: it fills the width of your container and grows to fit its own content, so your header, navigation and footer stay yours. It is not a pop-up and it never covers your page.

Both modes obey the same list of websites you allow in Support Settings, enforced on our servers. A copy of your snippet pasted on a domain you did not list renders nothing.

Going from the bubble to the full page

The panel’s expand control opens the help center carrying the visitor’s conversation and language with them (?c=…&lang=…), so the chat continues instead of starting again. If you do not want the bubble to offer that at all, switch rich mode off in Design Portal.

You can also link straight to one answer: …/go/your-org/support?article=article-slug.

Choosing what each page offers

Support → Support Settings → Design Portal holds one list of capabilities for your whole help and support system: the chat, search, articles, topics, most-read answers, the language picker, and whether a visitor can check a request they sent.

A single page can offer LESS than that, with data-capabilities:

<script
  src="https://muin.falaah.ai/embed/widget.js"
  data-type="support"
  data-tenant-slug="your-org"
  data-capabilities="chat">
</script>

That page shows the chat alone. A page can only ever narrow the list: a tag cannot switch on something you turned off, and Message the office is always available because a family must be able to reach a person. You choose the channel, never whether the door exists.

What is not built yet

Announcements and product tours have switches reserved in the capability list, and nothing renders them today. “Check a request” is built and is off by default; turn it on only once somebody is working the queue, because a status page for requests nobody reads is worse than no status page.