What agents see as caller ID in TrueEngage calls
By default agents see the visitor's page URL as caller ID. Here is how to show something more useful, and what the caller ID can't do.
Every TrueEngage call carries a caller ID (ANI, automatic number identification). By default it is the URL of the page the visitor called from. The ANI is a label for the agent and cannot be dialled.
Show something more useful to the agent
You have two ways to identify the caller:
| Option | What it does | See |
|---|---|---|
| Pre-interaction form | The visitor fills in a short form before the call starts (for example name, phone number, email or topic). The answers are passed to Genesys Cloud, and the agent sees them in the TrueEngage Agent App. No code needed | Pre-Interaction Forms |
| Remote name | Your web team replaces the page URL with a value such as a customer ID, using the remote name methods in the JavaScript SDK | JavaScript SDK |
Note: The ANI appears in Genesys Cloud interaction details and reports. Use an opaque customer ID, and keep personal data out of it unless the customer has agreed to that.
Limits
| What | Effect of the TrueEngage ANI |
|---|---|
| Calling back from the interaction | Not possible, because the ANI cannot be dialled. Collect a phone number in a pre-interaction form if callbacks are needed |
Architect lookups on Call.Ani |
Will not match a phone number in a data table, data action or external contact. Look up on a value you set instead |
| Reports and recordings | Show the ANI value as the caller |