> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/resources/phone-numbers/message-links.md).

# Message Links

This page describes how to create message links for a number.

## Create a QR code or wa.me link <a href="#generating-qr-code" id="generating-qr-code"></a>

QR codes can be created for API registered phone numbers in WhatsApp Manager.&#x20;

{% stepper %}
{% step %}
Meta Business Manager > WhatsApp Manager > **Phone Numbers**
{% endstep %}

{% step %}
Select the phone number to use for the QR code.
{% endstep %}

{% step %}
Click **Settings**
{% endstep %}

{% step %}
Click **Message links**
{% endstep %}

{% step %}
Click **Create message link**
{% endstep %}

{% step %}
Configure the message&#x20;

In the **Message** field, input the text for a pre-filled message that will populate for customers to edit and send to you after they scan the QR code. If you don't add text, your QR code will pop up as an open-ended conversation when scanned.
{% endstep %}

{% step %}
Click **Save**
{% endstep %}

{% step %}
You have the option to copy, download, edit or delete the QR code or wa.me link.&#x20;
{% endstep %}
{% endstepper %}


---

# 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.360dialog.com/docs/resources/phone-numbers/message-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.