> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/general/voipnow-guides/how-to-add-an-incoming-caller-id-prefix-with-an-ivr.md).

# How to add an Incoming Caller ID Prefix with an IVR

This article explains how to prefix an incoming call's Caller ID Name with the advanced extension "IVR".

{% hint style="info" %}

* This Caller ID prefix is only visible on extensions / phones / soft-phones within the VoIPNow system, calls transferred to external sources (e.g. Mobiles and other land lines) will not be able to see the Caller ID Prefix.
* This article assumes you already know how to create an IVR.
  {% endhint %}

## Steps <a href="#howtoaddanincomingcalleridprefixwithanivr-steps" id="howtoaddanincomingcalleridprefixwithanivr-steps"></a>

To setup a incoming Caller ID Prefix follow the steps below:

**Step 1 -** In a IVR that you have already created navigate to the context where you would like the prefix to apply

i. If you want it to apply to all incoming calls regardless of department apply it to the **"Start"** option

ii. If you want a separate Caller ID prefix depending on the option/department set it on one of the **"Number"** options (e.g. 1, 2 or 3)

![](https://www.hostednetwork.com.au/support/kb/files/15663126/15663123/1/1548226329079/image2019-1-18_15-5-14.png)

**Step 2 -** Once you have selected the option where you want to enable the Caller ID prefix you will need to add a new **"Action"**. Under the **"Add Action"** section select the option **"Alter CallerID Name with Static Value"** from the action dropdown menu

i. If you already have a rule in the selected option make sure to change **"Add in position"** to **"1"**

**Step 3 -** Under the **"Action Details"** section select the variables and values you would like to use

i. Select either **"Prepend"**, **"Append"** or **"Replace"** to specify where you would like the altered CallerID to be placed

* **"Prepend"** - Place the CallerID Prefix before the incoming CallerID Number
* **"Append"** - Place the CallerID Prefix after the incoming CallerID Number
* **"Replace"** - Completely replace the CallerID with the Caller ID Prefix

ii. Enter the CallerID Prefix you want to be applied

![](https://www.hostednetwork.com.au/support/kb/files/15663126/15663125/1/1548226329026/image2019-1-18_15-28-55.png)

**Step 4 -** Click **"Ok"** to apply the Prefix settings

You may need to click the **"Regenerate IVR"** button at the top of the window to make the changes go **"Live"**


---

# 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://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/general/voipnow-guides/how-to-add-an-incoming-caller-id-prefix-with-an-ivr.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.
