SalesForce

SigParser finds contact matches by email address.

Auto Create Leads

SigParser can automatically create Lead records in SalesForce. This is a great way to add contacts to SalesForce from SigParser and then allow someone in SalesForce to determine which Leads will get promoted to full contacts.

SigParser won't create a Lead if a SalesForce Contact with the same email address already exists.

Contact records are searched by email address using any fields with the type "email" in SalesForce or the field is named "Email".

Lead records are searched by the "Email" field. If the email field is missing SigParser won't be able to update the Leads.

Updating SalesForce Leads

SigParser will update the following fields. It will only fill in missing values or values it previously set.

  • FirstName
  • LastName
  • Phone
    • Ext__c - If this field exists, SigParser will set it with the phone number extension and not put the phone extension into the Phone field. If this field doesn't exist, the whole phone number goes into the Phone field.
  • MobilePhone
  • Fax
  • Title
    • Optional: Some teams have their own title scheme so don't want to push whatever SigParser finds.
  • Address Fields
    • Street, City, State, PostalCode, Country
    • Will update either all these fields at once or none of them.
    • If any one of the address fields is already filled in, SigParser won't update any of the address fields.

Auto Create Contacts

We don't automatically create contacts in SalesForce. Instead, you should setup Leads to be pushed (see above). Leads are better because they give you a staging area to choose which contacts should actually be contacts all from within SalesForce.

FAQ: Why not offer Contacts anyways?

We might someday. The main challenge is Account assignment. SalesForce Contacts by default need an Account created/assigned to them at the time of creation. This is difficult to handle well on the SigParser side as many organizations have different rules for how accounts are handled. For example, some companies have an account for every office location and other companies will configure SalesForce with accounts for every household. It is better to just let the SalesForce Leads feature handle this for us.

Update SalesForce Contacts

SigParser will update the following fields. It will only fill in missing values or values it previously set.

  • FirstName
  • LastName
  • OtherPhone
  • MobilePhone
  • HomePhone
  • AssistantPhone
  • Fax
  • Title
    • Optional: Some teams have their own title scheme so don't want to push whatever SigParser finds.
  • Address Fields
    • MailingStreet, MailingCity, MailingCountry, MailingState
    • Will update either all these fields at once or none of them.
    • If any one of the address fields is already filled in, SigParser won't update any of the address fields.

Bulk Import Contacts into SalesForce

We suggest reading this guide on how to import contacts into your CRM system. It is very detailed but is a good starting point if you want to merge multiple sources of contacts together before importing into SalesForce.

Non-Profit Starter Pack FAQ

If you are a non-profit and use the Non-Profit Start Pack, you might have some concerns. There shouldn't be anything extra you need to do but just in case, we've answered some of the common questions below.

Be aware this guide was written on 1/10/2019 for the current version of NPSP. The account model in older versions was different.

How does SigParser handle Contacts and Accounts in the NPSP?

SigParser doesn't have to do anything different for NPSP accounts and contacts if using the latest NPSP account model. The model is close enough to the standard SalesForce Accounta and Contact model that nothing really changes for how SigParser needs to operate.

salesforce npsp account model

Will Phone workflow rules break with the NPSP and SigParser's updates?

No, SigParser will set the proper phone field for a contact. From the SalesForce NPSP Documentationdocs:

When you change the Preferred Phone or Preferred Email pick-list field values, Salesforce automatically copies the related Phone or Email into the standard Phone or Email field, respectively. For example, if you selected “Mobile” as the preferred phone, Salesforce copies the value from the Mobile Phone field (“609-111-3333” in the example below) into the standard Phone field (which you can see on things like related lists containing Contact information).

salesforce npsp preferred phone

How are address updates handled between NPSP and SigParser?

The NPSP Address Management system works nicely with SigParser's updates. Since SigParser never overwrites addresses manually entered, SigParser won't ever set a bad address on a contact. If there are multiple contacts in a household, NPSP Address Management always ensures all contacts in that household have the same address.

salesforce npsp preferred phone