> For the complete documentation index, see [llms.txt](https://ac.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://ac.docs.landis.cloud/settings/caller-info.md).

# Caller Info

Settings | Caller Info

#### Call pop lookup URL

The call pop lookup URL is queried when there is an incoming call. The webpage will be shown in an Iframe on the call pop panel. The caller display name, caller number, queue name, and/or call ID can be included in the URL by using the supported placeholders. See example URL with placeholders below:

<https://apps.powerapps.com/play/b232?callernumber={callernumber}&displayname={displayname}&hidenavbar=true>

#### Open call pop in browser

If selected, the above URL will be shown in a new browser tab instead of the call pop panel.

#### Adaptive Card

Alternatively, an adaptive card can be displayed in the call pop panel when there is an incoming call. Adaptive cards can be designed [here](https://adaptivecards.microsoft.com/designer) and the JSON code copied into the Adaptive Card text field. Place holders that can be used in the call pop URL can also be used in the adaptive card.

Example Adaptive Card

```json
{
  "type": "AdaptiveCard",
  "body": [
    {
      "type": "TextBlock",
      "size": "Medium",
      "weight": "Bolder",
      "text": "Call Information:"
    },
    {
      "type": "TextBlock",
      "text": "${displayname}",
      "wrap": true
    },
    {
      "type": "TextBlock",
      "text": "${callernumber}",
      "wrap": true
    },
    {
      "type": "TextBlock",
      "text": "${queuename}",
      "wrap": true
    },
    {
      "type": "TextBlock",
      "text": "${callid}",
      "wrap": true
    }
  ],
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.5"
}
```


---

# 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://ac.docs.landis.cloud/settings/caller-info.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.