A one-step Ring Tree Target is the default type. When you check whether a one-step Ring Tree Target wants to buy an incoming call, you send all the required information about the call. If the information meets the buyer's requirements, the call connects. A two-step Ring Tree Target, on the other hand, is configured to send limited data at first and later an extra confirmation step sends more call data at the time the call connects.
The first of the two steps is to send the minimum information the buyer requires to decide whether they’ll accept the call, for example, the geolocation. If the buyer accepts the call, the second step is to send the full information about the call, such as CID, inbound call ID, and tags. Your account sends this information as the call is connecting. This is why "two step" is also called "ping and post": first you ping the Target and, if the buyer accepts the call, you post the rest of the call information.
Caller information is sensitive and should be shared only with those who need it to complete the call. A two-step ring tree target helps protect caller information by limiting access until you’ve identified the buyer who agrees to accept the call.
Your buyer tells you whether they should be set up as a one-step or two-step Ring Tree Target. The buyer determines what information they need at each step, and their lead management system’s API determines how you share that information. You can have both one-step and two-step Targets in the same Ring Tree.
To set up a two-step ring tree target, toggle on the Confirmation Request switch on the Ring Tree Target.