> For the complete documentation index, see [llms.txt](https://docs.nlx.ai/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nlx.ai/platform/developers/conversation-sdk/examples/advanced/voice+-tm-over-the-phone.md).

# Voice+™ over the phone

Voice+ can be very useful in multi-modal interactions where users calling in over the phone are directed to a particular webpage, where they can continue talking over the phone but the conversation and the web experience are in sync.

Generally the basic setup is usually that the user is directed to a specific webpage (perhaps via SMS or other medium) that includes the Conversation ID in the URL. Then Touchpoint is initialized in `external` mode with that particular Conversation ID (Touchpoint will then remember that Conversation ID automatically, so following links will keep the same conversation active for the user).

{% stepper %}
{% step %}

### Send the user a URL with a conversation ID

This can be achieved via a *Data request* node, for example:

<figure><img src="/files/oeR8CXPEEO7T3KvT7yLz" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Start a Voice+ node

Turn your conversation into a Voice+ session using a Voice+ node:

<figure><img src="/files/seOuyFD6Nm8QUK0MmMkT" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Integrate Touchpoint in external mode

On the destination page (the one you sent to your users), add the following snippet:

{% tabs %}
{% tab title="HTML" %}

<pre class="language-javascript" data-overflow="wrap" data-full-width="true"><code class="lang-javascript">&#x3C;html lang="en">
  &#x3C;head>
    &#x3C;title>Touchpoint Sample HTML&#x3C;/title>
    &#x3C;meta name="viewport" content="width=device-width, initial-scale=1">
  &#x3C;/head>
  &#x3C;body>
    &#x3C;script type="module">
      import { create } from "https://unpkg.com/@nlxai/touchpoint-ui/lib/index.js?module";
      
      const touchpoint = await create({
        config: {
          applicationUrl: "REPLACE_WITH_APPLICATION_URL",
          headers: {
            "nlx-api-key": "REPLACE_WITH_API_KEY"
          },
          languageCode: "en-US",
<strong>          conversationId: new URLSearchParams(window.location.search).get("cid")
</strong>        },
<strong>        input: "external",
</strong><strong>        bidirectional: {}
</strong>      });
    &#x3C;/script>
  &#x3C;/body>
&#x3C;/html>
</code></pre>

{% endtab %}

{% tab title="Typescript + NPM" %}

<pre class="language-typescript" data-overflow="wrap"><code class="lang-typescript">import { create } from "@nlxai/touchpoint-ui";
      
const touchpoint = await create({
  config: {
    applicationUrl: "REPLACE_WITH_APPLICATION_URL",
    headers: {
      "nlx-api-key": "REPLACE_WITH_API_KEY"
    },
    languageCode: "en-US",
<strong>    conversationId: new URLSearchParams(window.location.search).get("cid")
</strong>  },
<strong>  input: "external",
</strong><strong>  bidirectional: {}
</strong>});
</code></pre>

{% endtab %}
{% endtabs %}

Note the `cid` parameter added to the message which is used to link the conversations together.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
In `external` mode Touchpoint renders no visible user interface, since we expect that all of the communication will still happen over the external channel. So all Touchpoint is providing in this case are its Voice+ capabilities.
{% endhint %}

You can customize the Voice+ experience exactly like regular Voice+:

{% content-ref url="/pages/wPqGhGwfQWfDpDGyPRuf" %}
[Voice+™](/platform/developers/conversation-sdk/examples/voice+-tm.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nlx.ai/platform/developers/conversation-sdk/examples/advanced/voice+-tm-over-the-phone.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.