Sierra Interactive > KW Command Workflow Configuration

Overview

This page describes the process of setting up your Sierra Interactive to KW Command Workflow. To proceed, you will need both applications connected to your API Nation account and the Workflows created. For instructions on how to set up your Workflows, please click here.

When your Widgets, Filters, and Mapping are complete, the Sync can be activated at the top of the page via the "Activate Sync" button.

Functionality

The Sierra Interactive > KW Command integration syncs Leads and Notes between these two systems. It has the following functions:

When a Lead is created in Sierra, it will sync to KW Command.
When a Lead is updated in Sierra, it will sync to KW Command.
When syncing Leads to KW Command, the integration will search for an existing, matching Lead with the same Email. If a match is found, that Lead will be updated. If not, a new Lead will be created.
When a Note added is added to an existing Contact, the integration will sync this Note to KW Command under the matching Lead within 15 minutes.
- Note: Only newly added Notes will sync. Updated/Deleted notes will not sync.
- Note: All notes created via this integration will have an ID appended to the end of the Note so that the integration can identify and prevent duplicate syncs.

Widgets

Set up your desired Workflow Configuration. Once prepared, hit "Subscribe."

"Sync all contacts on first run" is a setting that will sync ALL Leads from your Sierra Interactive account over to KW Command.
"Send to lead routing" is a setting that will send Leads to the Lead Pool. Even if you check this box, please scroll down to the "Mapping" section and ensure that "Assigned to email" has no field selected. Field mapping will override this option.
"Assign to agent" is a setting that will set the Assignee for all synced Leads to the selected Agent." Even if you check this box, please scroll down to the "Mapping" section and ensure that "Assigned to email" has no field selected. Field mapping will override this option.
"Source" is a setting that will set the Source fo all synced Leads to the selected option.
"Do not overwrite information in KW Command fields. Only add information into blank fields" is a setting that will prevent the sync from replacing information in KW Command. It will only send information into a Lead if that field is blank in KW Command.

Filter

Filters can be utilized to only allow specific Leads to flow from Sierra Interactive to KW Command. To set up a Filter:

1. Press the box that says "No Filter". Select the field that you would like to use as the criteria for the sync.

2. Choose your logic statement in the middle box. In order for a Lead to sync, it needs to make this statement equal "True."

3. Choose your value that completes the statement and acts as the "key" that allows a Lead to pass through.

In the example below, only Leads with a Tag of "kwcommand" will sync through.

Additional Filters can be added by pressing "Advanced mode" and then "Add filter." These will be additional critiera that a Lead has to meet in order to sync (additional locks requiring keys).

There is also an option to add additional rules to the Filter; these are additional "keys" that will allow Leads to pass through.

Mapping - Leads

Please see below for a list and explanation of all fields that can be manually set between the two applications. Noteworthy fields are highlighted below.

First Name: Lead's first name in KW Command.
Primary Email: The main email used to identify this lead in KW Command.
Primary Phone: The main phone used to identify this lead in KW Command.
Last Name: Lead's last name in KW Command.
Middle Name: Lead's middle name. Not displayed on screenshot.
Preferred Name: Lead's nickname. Not displayed on screenshot.
Name Prefix: Prefixes such as "Mr.", "Mrs.", etc. Not displayed on screenshot.
Suffix: Suffix such as "Jr.", "Sr.", etc. Not displayed on screenshot.
Address Line 1: The first line of the Lead's address.
Address Line 2: Any second lines of the Lead's address, usually used to identify apartment or suite numbers. Not displayed on screenshot.
City: The Lead's city of residence.
State: The Lead's zip code of residence.
Country: The Lead's country of residence.
Zip Code: The Lead's zip code of residence.
Neighborhood Name: The Lead's neighborhood of residence.
Date of Birth: The lead's birthday.
1. This is not mapped by default because Sierra Interactive automatically sets the year "1920" as the birth year.
Home Anniversary: Date of the Lead's purchase of their home.
Description: Any text describing the Lead. Not displayed on screenshot.
Source: Source of the Lead's origin.
1. NOTE: This field only can be created. Once Source exists in KW, it cannot be updated further through this Workflow sync.
Assigned to email: The email of the Agent being assigned this Lead. This will overwrite any settings or Widgets set at the top of the page ("Send to lead routing" or "Assign to agent").
1. If the field “Assigned to email” is set in the mapping, this Integration will disregard any Widgets . If you wish to use Lead Routing or Assign all Leads to a specific Agent, please scroll down to the “Assigned to email” field and remove the mapped field.
2. If the integration cannot find a match between the Sierra Agent and the KW Command list of Agents, it will send the Lead to the Lead Routing pool.
Tags: Any tags identifying or describing this Lead.
Legal Name: Lead's alternative legal name.

See below for a screenshot labeling and comparing several notable fields between both applications. Note that mapping was left at default values.

Mapping - Notes

Please see below for a list and explanation of all fields that can be manually set between the two applications when syncing Notes. Noteworthy fields are highlighted below.

1. Title: The summary of the note in KW Command.

2. Details: The main body of the note in KW Command. NOTE: This has a character limit of 300; if the submitted Details are longer than 300 characters, multiple Notes will be created and the Details split among them.