> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/web-chat-widget/chat-links.md).

# Chat Links

Chat Links provide a simple way to create a direct web link for a specific customer conversation. This allows you to move an existing customer conversation to the web, where the customer can continue chatting while the conversation remains accessible through your **Inbox**.

### Creating a Chat Link

### to Create a Chat Link

1. Go to **Chat Links** from the left-hand menu.
2. Click **New Chat Link**.
3. Enter the required details.

#### 1. Phone Number

Enter the phone number of the customer for whom you want to create the chat link.

**Important:** Enter the country code without the `+` sign.

**Example:**\
`+91 9876543210` → `919876543210`

#### 2. Name

The **Name** field is optional.

You can enter the customer's name. When the link is opened for the first time, this name will be added to the contact.

#### 3. Expires In

Use this option to define how long the Chat Link will remain active.

Once the selected expiry period is reached, the link will automatically stop working.

#### 4. Single Use

Enable **Single Use** if you want the link to be restricted to the first browser that opens it.

When enabled:

* The first browser that opens the link gets access.
* The link can still be reloaded in the same browser.
* Forwarding the link to another person will not provide access.

This is useful for temporary or controlled customer interactions.

#### 5. Conversation ID

The **Conversation ID** field is optional.

* If left empty, the link will open the regular conversation associated with the customer's phone number.
* If a Conversation ID is provided, the link will open only that specific conversation.

4. After entering the required details, click **Create Link**.

### Sharing the Chat Link

Once the link is created, the generated Chat Link will be displayed.

Click **Copy Link** and share it with the intended customer through WhatsApp or any other communication channel.

When the customer opens the link, they can access the web conversation and continue communicating with your team through the **Inbox**.

### Managing Existing Chat Links

You can manage previously created Chat Links from the Chat Links section.

**Revoke**\
Use **Revoke** when you no longer want a Chat Link to work.\
Once revoked, the link will stop working immediately.

**Show Expired**\
Use **Show Expired** to view Chat Links that have already passed their expiry period.

**Security**\
Chat Links provide access to customer conversations and should therefore be treated as sensitive information.

**Always share the Chat Link only with the intended customer.**

{% embed url="<https://www.youtube.com/watch?v=xRZcLTuE6GE>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/web-chat-widget/chat-links.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.