You can use a lead route action to target potential prospects into a sales persons inbox or similar.

What is a lead route?

A lead route enables users to identify and schedule contacts to be sent out (via email and attached file) for an action. Marketers gain more flexibility in responding to contacts and the ability to schedule an email with a list of contacts who have reached a defined point in a program. The lead route action lets you send the right lead to the right salesperson and can also be used by program admins to monitor the number of contacts on each step or track for testing or data gathering purposes.

Build the program

You can apply the lead route action to the program, track or step level. Within this action, you can specify rules to identify contacts who reach a particular point in a program. As contacts are identified, they are scheduled to be emailed to an end user (i.e. regional sales teams). The email sent includes a password protected link to a .CSV file that contains the identified contacts and information about the contacts.

As you build the program, identify where you want to flag your contacts for export:

• Program level: Contact raises hand anywhere in the program.
• Track level: Contact raises hand when within the track or maybe a data elements changes when still in the track.
• Step level: When the contact reaches a step, all contacts should be called.

Configure a lead route

To configure your lead route, complete the following:

1. Name your action.
2. Enter a description of the action.
3. Identify the contact(s) you want to send in the email. You pull all contacts that reach the action or you can specify a rule and only email the contacts that match the rule. For example, contacts that live in the state of Georgia should be sent to the Eastern salesperson.
4. Select the database field(s) that you want to be included for each contact.
5. Enter a lead route password that the end user will enter to view the .CSV. The password rules will follow what is set for the org. The user must notify the end user of what the password is. It will not be included in the email generated from the system.

   Note: If you forget the password, you can go back into the action and change the password (this changes the password for all links generated from the action including the any generated in the past).

6. Enter the email address(es) in which you want to send the .CSV link.
7. Enter the subject for the email.
8. From name, from address and reply to address automatically populate based on who is creating the program. You may want to change this if the end user needs to contact someone else.
9. Enter the message that should be included with the email.
10. Schedule the frequency of the email to be sent.

About lead route

• When a lead route is processed, the .CSV file is placed in resources/stored files under the shared folder.
• These .CSV files are only kept in stored files for 14 days, at which point the link in the email is no longer valid.
• This also applies to direct mail and telesales files.

Personalization fields and lead routes

You cannot use personalization fields to configure lead routes, but multiple lead routes can be placed in the same area of the program and different rules can be configured.

For example, if you had a field called 'Sales Rep', you could add personalization to send relevant program content (specific leads) to your relevant sales reps (specific sales reps).

Check lead route exported contacts that did not meet the program rules

To find out who did not complete or submit the web form within the last 30 days, use the following setup:

• Decision points can be added, for example, with wait intervals on the 'No' path so if the contact does complete the webform within 30 days, they are not marked until that time frame is up.
• Contacts are evaluated and marked for export when they arrive at the lead route. You cannot 'unmark' them for export after they're marked even if they take a different action later. The program does not re-evaluate a contact after it is marked based on the rules that are configured. Consider adding a wait time interval to allow the contact more time before you move to the lead route.
• Entrance criteria, wait times, placement of the lead route within the program, and the qualifying rule operator can impact when contacts are marked to be included in the export.

Lead route notification troubleshooting

If you have a lead route set up on the track level to send a weekly notification and the file is either not generated or is empty, your program might not be configured properly. This can mean that your program looks at the track level and processes what needs to be done, then continues to the Step level.

However, what happens if your track level lead route includes a condition that is not set until the contact passes through the steps of the track? In this instance, the opportunity is already gone. For a lead route with a requirement that is related to sending a specific email, place the lead route on top of the email step, or in a new track after the step the email is in.