Create Accounts/Orgs in CRMs, Create Contacts in SalesForce

New 3 weeks ago Paul Mendoza , Founder/Developer

SigParser has added support for automatically assigning/creating Accounts/Organizations to Contacts in CRM systems like SalesForce and Pipedrive.

This new option makes it possible to fill out more of the data in your CRM system automatically in an organized way.



How Are Accounts or Organizations Matched?

SigParser finds the best Account or Organization for a Contact with the following rules:

  • Email domain of other contacts - SigParser looks at all the other Contacts in the CRM system, what their email domains (ie. are and then which Accounts/Organizations those Contacts are assigned to. SigParser then matches the Contacts in the CRM based on email domain to the contacts in SigParser by email domain. 
  • Website Field *(planned future enhancement)* - In the future SigParser will use the Website field in CRM systems like SalesForce on the Account record.

Naming New Accounts/Orgs with Domain Names

SigParser names the Accounts/Orgs with the domain name like or The name of the Account/Org can be changed by a user later and it won't impact the matching logic SigParser uses.

Exclude Public Free Hosts

SigParser also won't add contacts if the email domain is a common free host like or

Teams and contact access controls

New 3 months ago Paul Mendoza , Founder/Developer

We've added more support for teams and controlling access by to contacts based on the mailboxes the contact appeared in.

Let's say you're at an organization with three sales teams. You want to build a database of all contacts for the organization but you don't want every team member to be able to see all the contacts for other teams. You can configure the teams a user is a member of so a user can only see their team member's contacts.

You'll need to customize the roles a bit. For example, here is the Team Member role modified to only allow a team member to see their team's contacts.

Additionally, a team member can either share or not share contacts with their team. For example, a manager might not want to share contacts with their team but still wants to see the team.

We also added a new Export option to control which user roles are allowed to export contacts.

You can no longer add users or teams to SigParser without a Team level subscription.

SigParser Email Parsing Improvements (Chinese, Italian, Korean, Google Meetings...)

Improvement 4 months ago Paul Mendoza , Founder/Developer

We've made a lot of improvements to how we parse emails this week in order to reduce bad parses.

These changes improve both the SigParser core product and the SigParser Email Parsing API.

Chinese, Italian and Korean Email Splitting

When there is an email chain and the dividers between emails in the email chain are Chinese, Italian or Korean then SigParser can now properly split those emails. This reduces the chance of mis-attributing contact data to a different person.

Google Meeting Notifications

Google Meeting notifications will no longer be parsed for contact data in signatures. We may bring it back later as a special parser but currently the notifications are too unstructured and can cause contact data to be assigned to the wrong contacts. You'll still get the email addresses of the people on the root email.

Other Improvements

  • Exclude more email address patterns for spammy contacts
  • Improved Gmail signature block detection when -- is present but no email address is in the signature.
  • Edge case with line breaks not adding a whitespace which caused a bad name to be generated in rare cases.
  • New German Gmail style reply header handled.
  • Titles get the "at" stripped from the end. For example, "Founder at BigCo" but the title was "Founder at" so we remove the "at" now.
  • Added more training emails to the plain text spammy emails to improve plain text detection of spam or non-human sent type emails.
  • Improved false detection of signature data algorithm.

Custom Roles and New Permissions

New 5 months ago Paul Mendoza , Founder/Developer

Define your own custom roles to best suit your organization in our latest release. In an effort to better support a wide variety of organizations with their own requirements, we've made it possible to define the roles and permissions your team needs.

When you go to Settings -> Users you'll see on the right side a list of roles. From here you can add new roles.

When you are editing an existing role or a new role, you'll be able to pick from a set of permissions. Over time we'll add new permissions to this list.

One of the new permissions in this release is the External Email Reader permission. This is disabled by default on all roles but combined with the Can See All Contacts when disabled this is useful for allowing team members to read the emails sales and support have been exchanging with customers for example.

When a user has Can See All Contacts disabled then they'll only be able to see contacts in the tags you define in the Visible Contacts By Tags section. So if you are tagging customers or prospects then they'll be able to see those contacts.

Other features in the latest release:

  • New Permission: Add Data Sources - Useful to disable this when all the CRM and email connections are setup by the administrator in SigParser and you don't want users to go adding their own mailbox connections.
  • When adding a new email account or CRM, there is a video tutorial on the configuration screen.
  • Added a new, easy to understand email connection setup screen.
  • Added a new link to the main menu to make it easy to add an email account to SigParser.
  • Added buttons to purchase history to the dashboard. It was very buried before and users couldn't find it.

API Fields Additions - Name quality, email type, address parts, to and cc fields

New 5 months ago Paul Mendoza , Founder/Developer

We continue to improve the results of the SigParser API to return more valuable data about emails. The new API exposes things we think will help you to build powerful integrations with platforms.

Name Quality

When SigParser finds names for contacts, those names can come from different locations. With the API you can now see exactly where and how the name was derived. A quality score indicates how we think you should prioritize one name over another. For example, if a name comes from a header, that is almost always a better name than what SigParser might have guessed the name was in the email signature which isn't as exact. SigParser also generates names by using the email address in cases like "" and that's better than nothing but not a great name.

Email Types

Emails are sometimes human type emails with email signatures. But when they aren't, you might want to know that to skip some processing on them. We've exposed a new emailTypes field which is an array of attributes. We made it an array so later we can add more attributes. For example, right now we have a type for MeetingNotification but later we might add a new types for MeetingInvite and MeetingDeclined but it would still be a MeetingNotification as well. We might even add further attributes like GoogleMeetingNotification so you know what format it is.

Address Parts

In the last release you'd just get a single address field like "888 Grand Ave, San Diego, CA 92033" but then you still had to try and split the address into parts. Now the field addressParts contains the parts of the address if SigParser was able to split it. This isn't always perfect but it's better than writing your own algorithm in most cases.

To and CC

When sending an email to SigParser pass the to and cc fields to get those back with the response in the first email in the list of emails. Previously only the emails parsed from the body would have to to and cc which made some email handling more difficult than it needed to be.

You can see the full API spec updates here.