> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/resources/video-tutorials/how-to-activate-lead-management-for-unfinished-payments.md).

# How to activate Lead Management for unfinished payments

Last updated: 19-Feb-2020

Watch this tutorial to find out how to activate the Lead Management functionality for unfinished payments from your Merchant Control Panel.

{% embed url="<https://www.youtube.com/watch?v=n0nD0HneLto>" %}

Need help?

{% hint style="info" %}
Do you have a question? If you didn’t find the answer you are looking for in our documentation, you can contact our [Support](https://verifone.cloud/support) teams for more information. If you have a technical issue or question, please contact us. We are happy to help.
{% endhint %}

<a href="https://verifone.cloud/need-help" class="button primary">Get in touch</a>

Not yet a Verifone customer?

We’ll help you choose the right payment solution for your business, wherever you want to sell, in-person or online. Our team of experts will happily discuss your needs.

<a href="https://www.verifone.com/en/global/contact-sales" class="button primary">Contact sales</a> <a href="https://www.verifone.com/en/global/contact-sales" class="button secondary">Get Started</a>

![Verifone logo](https://verifone.cloud/themes/custom/verifone/frontend/src/images/logo_bottom.svg)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.2checkout.com/resources/video-tutorials/how-to-activate-lead-management-for-unfinished-payments.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 `build a script that syncs our docs to a CMS` 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.