Get Leads Into goBluebird

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 goBluebird!

This can be done automatically via Email Endpoint, or Post API, or Manually via CSV Upload, or Individual Form Fill.

Email Endpoint

Most lead sources will be able to send generated leads to an email address, or email endpoint. This is the easiest way to get leads into goBluebird the moment they are generated.

To find your email endpoint open the left sidebar, and select Integrations from the Configuration section. Towards the top of the page you will see your Email Endpoints.

Be careful not to reveal this information, as emails sent to this email address will be parsed and sent into your company as new leads.

Post API

The second way to get leads into goBluebird automatically is via Post API. This method is a little more technical than Email Endpoint, but allows for more control and consistency of leads being sent into goBluebird. Read our full API Documentation here.

Individual Form Fill

You can manually add leads one at a time using the New Lead form found by clicking the red plus in the bottom righ of the leads page.

1. In the left sidebar under Usage click Leads
2. Click the red plus in the bottom right to open the New Lead form

This will open the New Lead form. Fill out the relevant information and click Create New Lead to add a new lead.

CSV Upload

The best way to quickly add multiple leads into the platform is with a CSV upload.

1. In the left sidebar under Usage click Leads
2. Click the red plus in the bottom right to open the New Lead form
3. Scroll down to the CSV Importer section
4. Click the paperclip to select a CSV from your files, and click Upload CSV when you are ready

All leads should have a name and either a email address or a phone number.

We can handle many other fields, some common ones are:

• Address
• Tags
• Message
• zip code
• campaign id
• contact form id

Download a sample CSV

Lead input widget

goBluebird has a widget that you can embed into a webpage in order to add leads directly to a goBluebird 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 goBluebird.
The API key can be obtained by visiting https://app.gobluebird.io/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.gobluebird.io/';
la_token = 'YOUR_API_KEY_HERE'; 
la_company = 'YOUR_COMPANY_SLUG';
</script>
<script src='https://app.gobluebird.io/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:

la_first_custom

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