This component has additional usage costs. The component is available in all accounts, but you need to have an Identity Standard license or a trial version.

To ensure that the callers’ phone number is verified against any fraudulent activity, and SHAKEN/STIR call attestation is presented as part of caller ID spoofing detection, you need to add the “Validate phone” component to a Studio flow. 

The “Validate phone” component has two purposes:

• The first is to fetch phone insights, spoof caller ID information, and present them to agents in the Identity tab inside the Conversations app, and to supervisors in the Identity app itself.
• To allow call routing within Studio.

In the example that we are presenting in this article, we show how to accomplish both in one Studio flow.

1. In the Initial step, set up the source_phone variable from this component. In our example, we’ve named it “Contact_Phone_Number”.
2. Add a "Validate phone" component to the Initial step exit for successful outcomes (exit “OK”).

3. On the “Phone number” step, configure the variable you set up in the Initial step.

Note: If you are using the “Validate phone” component only to present the phone validation insights and the call attestation result to agents and supervisors, it is unnecessary to configure any Variables. Proceed to configure the Exits section.

We check if the phone number is risky by evaluating the Fraud score (>= 85% is considered High Risk), and if the caller ID has been spoofed by assessing the call attestation value (if the call attestation is TN-Validation-Passed-C or TN-Validation-Failed-C, the caller may have been spoofed). 

In Explaining the Variables in the “Validate phone”, all the variables and their corresponding values are explained in detail.

4. Configure the fraud score and call attestation variables that will be used in the flow to route the calls according to their value.

5. Set up the “Validate phone” exits, depending on the flow you would like to define.

We have added a “Conditional Statement” as the Success exit of the “Validate phone” component in order to evaluate the Fraud Score value and route the call depending on what it is.

6. In the “Conditional Statement” component, called “Is Risky”, add a condition to verify if the FRAUD_SCORE value is equal to or greater than 85. If the condition is met, then the caller will hear an audio message informing them that they will be contacted later, by email or SMS, and the call is terminated, mitigating any risk the agents may face.

7. Another verification that is done, in this example, is if the caller ID has been spoofed. Add another “Conditional Statement” in the “No Match” exit of the “Is Risky” component. When the conditions CALL_ATTESTATION equals either TN-Validation-Passed-C or TN-Validation-Failed-C, the caller hears the same audio message informing that they will be contacted later.

8. If the caller doesn’t pose any risk, then the call is routed to an agent that will be able to see the caller’s Spoofing detection and Phone validation insights in the Identity tab in Conversations in real-time as soon as the call is answered. 

This article shows an overview of the Identity tab functionalities.

Explaining the Variables in the “Validate phone” component

The Variables in the “Validate phone” component only need to be configured if you want to route calls within Studio.

There are two sets of variables:

• Phone validation insights.
• SHAKEN/STIR call attestation.

What are the insights from Phone validation and their value ranges?

The following table displays the relationship between Talkdesk Global Communications Network (GCN) call attestation levels and Spoofing detection status.

To read the complete information about the SHAKEN/STIR call attestation value ranges, please click here.

To know more about Identity, please consult our documentation.