> 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/feature-highlights/call-pop.md).

# Call Pop

Want to manage calls even better? Our call pop feature lets you see crucial contact info, like CRM or ITSM data, right on your agent panel. If embedding your CRM or ITSM URL isn’t working in an iFrame, just use the "Open Call Pop in New Tab" setting. This way, you can access the web page in a new browser tab without any hassle.

<figure><img src="https://1039569329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lm5wszNs6c24n4NZ30U%2Fuploads%2FNl8dW38JhyXBrwWu7RKr%2FCallpop%20Resized.gif?alt=media&amp;token=02aa510d-427c-4ac4-b2d4-cb1977dbdb39" alt="" width="375"><figcaption></figcaption></figure>

You can customize the URL and display settings within the queue setup to fit your needs. It’s all about making sure you have the info you need to boost productivity and keep those customers happy.

Here's how you can use the variable placeholders in your URL:

* **{scenarioid}**: The system will swap this out with your scenario ID.
* **{queuename}**: This will be replaced this with your queue name.
* **{callernumber}**: The system will swap this out with the contact's number.
* **{callername}**: This will be replaced this with your contacts's name.

Feel free to mix and match to suit your needs!

To configure a Call Pop URL, hop into Queues & IVRs, choose Queues, click Edit on a queue, head to the Integrations tab, and enter that URL into the Call Pop URL field. You're all set!


---

# 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/feature-highlights/call-pop.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.