> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/repx-chat/setting-up-repx/launching-on-your-website.md).

# Launching on your website

Quick guide to going live with RepX on your website

Once you've tested out RepX and you like the quality of answers and conversations it has had, you can launch RepX on your website. RepX comes in multiple form-factors and you can pick what works for your situation. There are two ways to embed RepX:<br>

* embed RepX like a **traditional chat widget**
* embed as an **immersive view**

{% hint style="info" %}
The code for embedding RepX in either of these formats is available from [**Settings > Embed**](https://app.storylane.io/repx-dashboard/settings/embed)
{% endhint %}

#### Embed as a floating widget

When you choose this format, RepX appears on the corner of your website like a traditional chat widget. The element users can click on to launch the RepX chat experience is called the **launcher**. You can choose between three different styles for the launcher.&#x20;

#### Launcher styles

In the embed mode, RepX comes in **three launcher styles**. Choose anything you like based on what works best for your website. These are the three launcher styles:<br>

* **Type first** - the launcher is text box where users can directly start typing. The text box also shows starter questions.
* **Buttonish** - the launcher appears like a button that users can click on.
* **Floating video** - the launcher appears like a floating video tile&#x20;

<img src="https://2714158815-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5THBKNFo5kBfDJULy3RM%2Fuploads%2FL1wQpmyyF8JHZYTQl81P%2Funknown.png?alt=media&amp;token=bf9cc46d-9cbc-494a-8322-172960ef0b43" alt="" height="355" width="624">

#### Launcher position

This controls where the widget shows up on the page - you can either pick **bottom right** or **bottom center**.&#x20;

#### Primary color

The **primary color** is applied across RepX chat experience - in the CTA buttons, the chat background gradient, and in other places. Pick one from your suite of brand colors - ideally something that contrasts well against other colors on your website.

<img src="https://2714158815-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5THBKNFo5kBfDJULy3RM%2Fuploads%2FfHvJerE33av04LpyV1ZJ%2Funknown.png?alt=media&amp;token=28280c51-edb7-49da-be53-0e7fda061118" alt="" height="355" width="624">

#### Immersive view

We recommend embedding the immersive view is recommended in two situations:

* if you want to have a **dedicated page just for RepX,** which your website visitors can access to have conversations.
  * Backstory, one of our customers, has [this dedicated page](https://www.backstory.ai/ask-now) linked from their main navigation that visitors can start conversations from &#x20;
* if you want to **drive conversations after a conversion goal has been met** (once visitors submit a demo form, for instance)
  * E.g. Storylane launches RepX's immersive experience once our visitors submit the [demo booking form](https://storylane.io/book-a-demo).&#x20;

The immersive view can be embedded into your website by copy-pasting the code in the 'Embed page' under the 'Immersive view' tab. It's a simple \<iframe> tag - just make sure to set the right height and width when you embed this experience.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.storylane.io/repx-chat/setting-up-repx/launching-on-your-website.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.