API Nation
You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
Home > Common Questions > KW Command > KW Command > Sierra Interactive Workflow Configuration
KW Command > Sierra Interactive Workflow Configuration
print icon

Overview

This page describes the process of setting up your KW Command to Sierra Interactive 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 KW Command > Sierra Interactive integration syncs Leads and Notes between these two systems. It has the following functions:

  • When a Lead is created in KW Command, it will sync to Sierra.
  • When a Lead is updated in KW Command, it will sync to Sierra.
  • When syncing Leads to Sierra, 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 is added to a Lead in KW Command and there is a matching Lead in Sierra, sync the new Note into that Sierra Lead.
    • 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 contacts from your KW Command account to your Sierra Interactive account.
  • "Do not overwrite information in Sierra Interactive fields. Only add information into blank fields" is a setting that will prevent the sync from replacing information in Sierra Interactive. It will only send information into a Lead if that field is blank in Sierra Interactive.

 

 

Filter

Filters can be utilized to only allow specific Leads to flow from KW Command to Sierra Interactive. 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

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.

 

  1. Email: The main email used to identify this lead. Required.
  2. Password: The password that the Lead can use to log into Sierra Interactive. Not displayed on screenshot.
    1. By default, this is set to "Primary Email" from KW Command, as it is a required field.
    2. A different value (either another field or a static value) can be set. However, there must be a value in this field or else the Workflow will not run.
  3. First name: Lead's first name.
  4. Last name: Lead's last name.
  5. Lead status: The status of the Lead within Sierra Interactive.
    1. Only accepts these possible values: New, Qualify, Active, Prime, Pending, Closed, Archived, Junk, DoNotContact, Watch, Blocked
  6. Lender status: The status of the Lender within Sierra Interactive. Not displayed on screenshot.
  7. Email status: The status of the Lead's email within Sierra Interactive. Not displayed on screenshot. 
    1. Only accepts these possible values: Unknown, WrongAddress, ReportedAsSpam, TwoWayEmailing, ValidAddress, OptedOut
  8. Phone: The main phone used to identify this lead.
  9. Phone status: The status of the Lead's phone within Sierra Interactive. Not displayed on screenshot.
    1. Only accepts these possible values: Unknown, TalkingToProspect, ValidNumber, DoNotCall, WrongNumber
  10. Birthday: The lead's birthday.
  11. Lead Type: A numerical value denoting the Lead's type.
    1. 1 -> Buyer, 2 -> Seller, 3 -> Both.
    2. If lead type is not specified, its type will be set to Buyer.
    3. This can be set manually by the "Data Transpose" function. Please see below for an example
  12. Source: Source of the Lead's origin.
  13. 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.
  14. Tags: Any tags identifying or describing this Lead.
  15. Street Address: The Lead's address, mapping strictly Line 1 by default.
  16. City: The Lead's city of residence.
  17. State: The Lead's state of residence.
    1. Lead's state / province from US or Canada (AB, AK, AL, AR, AZ, ..., YT) in form of abbreviation.
  18. Zip: The Lead's zip code of residence.
  19. Short summary: Any text describing the Lead. Not displayed on screenshot.
  20. Note (create only): Descriptive note about lead which will be added as Note to lead's history.
    1. Notes can only be created; created notes cannot be updated.
  21. Partner Link: URL to identify the lead in the partner's system. Not displayed on screenshot.

 

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. Message: The main body of the note in Sierra Interactive. Sierra only accepts this single input; the pre-mapped value for this mapping will generate a note in a format such that it possesses both the Title and Note from KW Command.

  • Example Note Body:
    • Title: Lead is Cold; Message: Please be aware that this Lead has not messaged us back in some time. Unlikely to have continued interest.

 

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

Feedback
1 out of 1 found this helpful

Need Additional Assistance?
Submit a ticket by clicking here and an API Nation Success Specialist will reach you with a solution
 
scroll to top icon