# Call Personalisation

{% hint style="info" %}
Build secure and personalised calling experiences with end to end authentication of every call. \
Deliver personalised context and identity with APIs that seamlessly integrate into your existing calling infrastructure.
{% endhint %}

### Here are some use cases for Call Personalisation APIs:

* Enhance your Verified Business identity by making every call secure with call-by-call assurance through an automated signing process.
* Calling operations done through non-company owned numbers where a permanent identity cannot be listed.
* Scheduled calling operations that are run daily, where your business wants to add a clean identity and personalised call context for optimal performance.
* Calls often made from one business number to multiple users.
* Refreshing your identity on Truecaller easily, if your business has limited calling numbers.

### Pre-requisites for using Call Personalisation APIs:

* **Android Device Pre-requisite**: Please make sure that the settings mentioned in this documentation [here](https://docs.truecaller.com/truecaller-for-business/get-to-know-truecaller-customer-experience-solution/what-are-the-android-settings-required-to-enable-the-truecaller-caller-id) are followed for the **Dynamic Caller Id** to work.
* **iOS Device – Live Caller ID Limitation:**Dynamic Caller ID is currently not supported on iOS devices. However, Static Caller ID can still be enabled and used on iOS.\
  For settings on iOS, kindly refer [here](https://docs.truecaller.com/truecaller-for-business/get-to-know-truecaller-customer-experience-solution/what-are-the-ios-settings-required-to-enable-the-verified-business-caller-id-badge)
* **Dynamic Label ID**: Only “Dynamic Label IDs” can be used in the API request for placing calls. [*These dynamic label IDs need to be created in the Truecaller for Business console, after which the dynamic label ID can be copied from the Caller ID page in the console* ](#user-content-fn-1)[^1]<br>

<figure><img src="/files/jOzm6YENZjdRuGqOdY8D" alt=""><figcaption></figcaption></figure>

* A subscription to a package that includes Call Personalisation APIs.&#x20;

### Integration steps:

* #### [Create an API Key](/truecaller-for-business/verified-business-api-documentation/getting-started/authentication.md).
* #### [Generate Access Token](https://app.gitbook.com/o/F5twjTXEkQfiqVXPqwwO/s/pyyDYzpD4A2zU6fYohHS/~/changes/79/getting-started/generate-access-token).
* #### Create a dynamic label on Truecaller for Business console:
  * Log in to the Truecaller for Business console.
  * Navigate to Business Identity in the left hand side panel.
  * Click on "Identity" and then go to the Caller ID Details section.
  * Click on "Create a Label".
  * Select the caller ID type as Dynamic Caller ID.
  * Add a logo for your dynamic caller ID. The logo should be a PNG file, with dimensions 200x200 and file size less than 2 MB.
  * Add a label name of less than 40 characters for your Dynamic Caller ID.&#x20;
  * Choose the category for your business from the dropdown after creating a label name.
  * Click on "Create Caller ID' to finish creating your dynamic caller ID.
* #### Check the status of pushed records.
* #### Hit the dialer and place the call.

{% hint style="success" %}
If your business is interested in knowing more about Call Personalisation APIs, please reach out to -> **<cs@truecaller.com>**
{% endhint %}

[^1]:


---

# Agent Instructions: 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.truecaller.com/truecaller-for-business/verified-business-api-documentation/call-personalisation.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.