Get Leads Into Lead Assign

Once the salesperson roster and tags are set up, and after the routing method is configured, the most important step is to get leads into Lead Assign. 

Almost every lead source will send generated leads to an email endpoint. This email endpoint must be changed to the email address found on the “Integrations” page. An example of this is: yourcompanyname@md.leadassign.com.

For other types of lead sources, please review the full documentation for more information.

Creating lead source forms

When a potential customer is visiting a company website, a popular call-to-action is for the visitor to fill in a form. Once the customer submits the form, the website software will turn this form into an email. This email should be sent to the same email endpoint. (There is also the option of posting information with an API, or using Facebook or Zapier.) Gravity Forms, Contact Form 7, Typeform, jot form, etc. can all be used as call-to-action forms on a company website.

Formatting incoming leads

Lead Assign has been designed to parse any format of incoming lead. However, it is highly recommended to format the initial lead submission in the following way to ensure leads are routed correctly.

Lead Assign specifically looks for items following these labels with sample inputs:

  • Name: Susan Customer
  • Phone: Susan’s phone number
  • Email: Susan’s email
  • Address: Susan’s address (in one line)
  • ZIP: US postal code
  • Postal Code: CAN postal code
  • Message: I am interested in your product; it looks really interesting. Can you provide more information. I am considering purchasing this week. Thanks, Susan.

Note that all the fields are optional. The lead form may be longer or shorter, which is acceptable too.

Lead Assign can take leads that are not in this format and still be able to determine the name, phone, and email of the potential customer. Furthermore, Lead Assign can read leads that are non-formatted chat transcripts, verbose leads from third party lead generators, and many more variations.

Lead input widget

Lead Assign has a widget that you can embed into a webpage in order to add leads directly to a Lead Assign account.

Setup

Setting up the widget requires two access tokens: a company slug and an API key. The company slug indicates the company receiving leads and is found in the url after logging into Lead Assign.

The API key can be obtained by visiting https://app.leadassign.com/YOUR_COMPANY_SLUG/apikey/. Press the ‘Generate new auth token’ button to generate a new API key. Then add the following code to the webpage from which you wish to add leads:

<script>
la_endpoint = 'https://app.leadassign.com/';
la_token = 'YOUR_API_KEY_HERE'; 
la_company = 'YOUR_COMPANY_SLUG';
</script>
<script src='https://app.leadassign.com/js/form-widget.js'></script>

Set the la_token field to the API key generated as per above. Set the la_company field to the company’s slug. This will inject a button into the account page.

Clicking the ‘Create a new lead’ button will open a modal containing a form. After filling out the form, click the ‘Create a new lead button.’ If the lead was created successfully, a pop up with the message ‘Request sent’ will appear. If the lead was not created successfully, a pop up with the message ‘Please try again’ will appear.

Configuration options

The plugin comes with various configuration options:

  • Adding a div with ID “la_widget_form” appends the form directly to the page as opposed to using a popup modal.
  • Creating a variable called la_geolocation and setting its value to true adds an address field to the form.
  • Creating a variable called la_source and setting its value to true adds a source email field to the form.
  • Creating a variable called la_first and setting its value to true adds a first agent field to the form.
  • All of the labels for the fields on the form can be customized. Setting any of the following to a string will change the label on the corresponding field to the string provided:
    • la_name_custom
    • la_phone_custom
    • la_email_custom
    • la_text_custom
    • la_geolocation_custom
    • la_source_custom
    • la_first_custom