> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-d-activate-through-customer-service.md).

# Option D – activate through customer service

Use this option when the **end user** calls the issuer’s customer service.

The customer service operator verifies the end user’s identity.

The operator then identifies the token to activate.

Finally, the operator activates the token.

{% hint style="info" %}
You choose where customer service operators perform these actions:

* **TSP portal**, provided by the payment network.
* Your own **customer care interface (CCI)**.

If you use your own CCI, integrate it with the Thales **TIG** APIs.
{% endhint %}

### Flow

The diagram below shows the call center activation flow and the Thales **TIG** APIs involved when the issuer uses its own CCI.

<figure><img src="/files/jJBuztBs7asWnoWS2Yos" alt=""><figcaption><p>Customer service token activation flow.</p></figcaption></figure>


---

# 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:

```
GET https://docs.payments.thalescloud.io/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-d-activate-through-customer-service.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.