> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/appendix/call-popup.md).

# Call Pop

When a new call is presented to an agent, a web page can be shown in the contact center agent panel or in a new browser tab. This web page can be populated with contact specific information. The URL and where the page is displayed can be configured in the queue setup under the [Integrations](/setup/set-up-voice-channel/setup-service.md#integrations) tab. If the web page does not support being imbedded in an iframe, we recommend enabling the setting "Open Call Pop In New Tab". This will open the web page in a new browser tab. This option is only available after entering a URL.

When an opening curly brace is entered, a dropdown list of available placeholders will appear, and they can be selected from the list.

#### Call Pop URL

This call pop URL is used for inbound and outbound queue calls. The placeholder values are sourced from the current call.

#### Automatic Callback Call Pop URL

This call pop URL is used for automatic callback calls. The placeholder values used for the Automatic Callback Call Pop URL are sourced from the original call that created the callback record, not from the callback call itself.

#### Placeholders:

The below variable placeholders can be placed in the URL:

| Placeholder           | Description                                                                                                                                                                                    |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| {callername}          | Contact Name                                                                                                                                                                                   |
| {callernumber}        | Contact Number                                                                                                                                                                                 |
| {callerupn}           | Contact User Principal Name                                                                                                                                                                    |
| {calleradid}          | Contact Entra ID                                                                                                                                                                               |
| {callersearch}        | Returns the first available property from the following, in this order: callernumber, callerupn, or calleradid.                                                                                |
| {queuename}           | Queue Name                                                                                                                                                                                     |
| {scenarioid}          | Unique id of interaction                                                                                                                                                                       |
| {datavalue#}          | See [Data Collection placeholders](/administration/data-collection.md#queue-call-popup)                                                                                                        |
| {callbackdescription} | The call back description value that was populated in the IVR callback block on the original callback record. **This place holder is only available for the Automatic Callback Call Pop Url.** |

We recommend using a PowerApp when integrating with a CRM.


---

# 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://cc.docs.landis.cloud/appendix/call-popup.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.