Knowledge Base

How does Routing work?

• An Outbound API, once created, has to be attached to a route in order for it to be utilized.  Outbound APIs are the transport mechanisms while the Routing is the lead selection mechanism.  
• A route has the following components

• • Name

• • • Defines the name of the route

• • Enabled

• • • Turns the route on and off

• • Schedule

• • • Defines the start and the end date of the route.  If left blank, the route runs forever.

• • Trigger 

• • • Instant

• • • • Routes can be triggered instantly, meaning as soon as a lead arrives at your Inbound API, the lead is considered for this route.
    • After Auto Responder Success

• • • • Routes can be triggered after a lead arrives to your inbound API but has to first go through the autoresponder process for the lead to be considered for this route.  This way the lead first receives an autoresponder and if the lead opts-in, it is deemed to be a success and therefore, the lead not triggers the route.

• • • Action Type

• • • • A route can either use a straight “Post” or a “Ping and Post” methodology.
        

• • • • • Post routes methodology

• • • • • • A post route will only consider outbound APIs that have the post action.
            

• • • • Ping and Post routes methodology
        

• • • • • This type of route will allow a bidding environment where a Ping will be sent to all the outbound APIs that are Ping enabled first and then the process will wait for the answer to determine the highest bidder for that lead and then the process will Post the lead to the highest bidder.

• • • • Minimum Price

• • • • • A minimum price can be set optionally to meet for a Ping bid.  If all the participants of the Ping bid do not meet the minimum price, the Ping bid is deemed a failure and the Post is not issued.

• Filter describes the criteria in which a lead will be selected to use this route.

• This area defines which outbound APIs will be associated with this route