Lead processing allows you to tell ContactUs.com what to do with new leads. Its like having a little robot read every single piece of information that’s coming in from your leads and then having the robot decide what to do with those leads. In other words you can “Program” contactus.com to do thousands of different tasks without having to write a single line of code.
All it takes is for you to understand how lead processing works and how to set lead processing rules up!
Lead processing rules are pieces of logic that are grouped together to make statements. The statements tell ContactUs.com what to do when something happens or does not happen.
Every lead that comes into ContactUs.com creates specific information slots known as lead data fields. Some information is given by the lead, some information is automatically captured and some information can also be manually added by you by directly filling in any information field into to the lead profile. This data is important because it’s the information that the contactus.com bot uses to make decisions.
*Generic Fields 1-20 are fields for your custom types of information. You can define what kind of information each generic field captures and you can add generic fields in the online form builder. You can add as much as 20 different custom fields for each lead profile! Their names and ranges are defined when creating custom field forms.
Example: For example, this rule says that if a lead selects California, to send an email to email@example.com
So what actions can we ask the ContactUs.com bot to do?
Well, quite a lot, for example, Send a message to a specific email, send an SMS text message to specific number, send specific reply to lead based on what the lead asked, mark a lead as a priority, change a lead’s status or add a specific TAG to the new lead.
Every action has to directions: One, -if the statement is true and one -if the statement is false. For example: We could create a rule that says that if a website visitor fills in a form and in the form he states that he is a “previous customer”, to send and email with a custom message to your “customer service” people. But if the website visitor does not select that he a “previous customer”, then send a different custom email to your sales people. This lets everybody focus on relevant data, and guarantees you are not going to overlook an important lead or fail to call a lead that is hot and ready to negotiate. Forgetting and not responding to leads happens more than you think in businesses. The scariest think about this fact, is that most business owners and sales managers don’t even realize how many missed opportunities pass by them.
Lead processing allows you to tell ContactUs what to do with new leads, based on the lead data.
Leads come in through contactus-tracking-numbers, contactus-forms, adding leads manually or importing leads from a .csv file. Once leads are stored in the ContactUs.com lead management system they start getting processed and you start saving time and focusing on things that require your attention.
So, now we have an idea on how to tell ContactUs.com to automatically execute 1 activity based on yes/no situations. If this happens, send this email, if it does not happen, send this other email. But what happens when you need more actions? For example, lets say you have sales-reps in 6 different towns / And you want leads to be delivered specifically to the agent that resides in the lead’s location. If the lead says she or he is from new York, send the email to the New York team… if the lead is from Chicago, you would probably want to automatically send the Chicago lead to Chicago team, The San Francisco lead to the San Francisco team, Miami leads to the Miami team and so forth. This would require more than a yes / no rule. Luckily ContactUs.com offers parent rules! The combination of child and parent rules allow for complex processing rules without the PhD in computer science.
One great thing about lead processing rules is that you can combine them to create more complex lead processes. To do so, you may assign parent rules to any rule.