Set Prospect Client Command

I've just completed a test project designed for adding more rules into how WhosOn Live Chat can decide on Prospect Detection. Prospect detection is used for setting up different rules for allocating the quality of visitors, and very commonly as something to send automatic invites based on. The new WhosOn V6 that will be released shortly allows for multiple types of prospect to be defined.

This uses the new Set Prospect command to insert the prospect into WhosOn and force the actions for that prospect to happen.

The system connects to a given site using the client protocol, and stores the visitors internally, subscribing to the WhosOn visitor event model (waiting for the @EV and @ER events, and using an internal array to hold the information).

The detection allows for second level triggering of time on site, time on page, time idle etc, and is easily plugable to allow for expansion of the types of filters that can be used.

It breaks down the rules into two types of rules - those that require timers, and those that don't.
If the rules don't require timers, then they wait for the events (or the initial visitor list population on connection) and check the rules at this stage.

For the rules that do require timers, these are executed based on the timer refresh length set in the program, and the number of seconds can be set here.

The rules are multi-threaded (along with each connection) so the program can deal with many connections for many different rule sets.

The rule set uses an XML structure for if a rule should be activated, containing the rule type and the login information.

Rules that I have created so far:

• Regular Expression for Current Page, Previous Page, Any Page this Session
• Form Variable Check
• Number of Seconds on Page
• Number of Seconds on Site
  

Possible Future updates:

• More Rules Types
• More intelligent timer - don't need to check every X seconds if there are no new visitors. This could be calculated by checking the current timer wait time, and minimum time for the rule, then setting up the internal timers to wait this long.
• More Actions (I.E. sending different messages through to the visitors in the invites, or sending messages to the operators about the visitors).
• Performance enhancements on the visitors arrays.
• Use reflection for loading the types, rather than just doing a case selection on the type name.

If you are interested in using this sort of rules engine, then please contact our professional services team, and we will endeavour to match up prospecting systems to deal with whatever your requirements for prospecting are. The link below shows information about our Configuration Professional Services for WhosOn Live Chat.

http://www.whoson.com/professionalconfiguration.aspx