The email enrichment problem in Salesforce

Sales reps routinely encounter contacts in Salesforce with missing or bounced email addresses. The usual fix is to buy a data vendor subscription — ZoomInfo, Lusha, Apollo — and hope the contact exists in their database. Coverage gaps are a persistent problem, particularly outside major US and European markets.

But here's the thing most teams miss: your Salesforce org already contains a rich signal about how the companies you've emailed structure their email addresses. Every historical email thread, every contact with a confirmed deliverable email, every activity logged — these form a pattern.

What is Email Identifier Technology (EIT)?

Syftplus uses a method called Email Identifier Technology (EIT) to detect naming conventions from the confirmed email activity already logged in your Salesforce org. When a contact like james.chen@globaltech.com.sg appears in your activity history, Syftplus registers the pattern: firstname.lastname@domain.

When you later look up a new contact at globaltech.com.sg — say, Sarah Wong — Syftplus applies that same pattern and suggests sarah.wong@globaltech.com.sg as the derived email address.

The ECS score: know how confident to be

Not every derivation is equally reliable. Maybe acme.com uses j.chen@ for executives and james.chen@ for managers. Syftplus accounts for this ambiguity through its Evidence Confirmation Score (ECS) — a 0–100 confidence rating on every enrichment suggestion.

• Strong (ECS 70–100): Multiple confirmed signals. Push directly to Salesforce and sequence.
• Medium (ECS 30–69): Partial evidence. Worth using but flag for light verification.
• Weak (ECS 0–29): Thin signal. Review manually before sending.

How Syftplus works alongside ZoomInfo and Lusha

Syftplus isn't a replacement for ZoomInfo or Lusha — it's complementary. Those tools provide coverage from external databases. Syftplus derives coverage from your own CRM's confirmed activity history. Used together, they give you two independent verification paths: one from the outside in, one from the inside out.

In practice, many teams find that Syftplus covers contacts that ZoomInfo and Lusha miss, particularly at local and regional companies not well-represented in US-centric databases.

Setting up enrichment in Salesforce

1. Install Syftplus from the Salesforce AppExchange (admin approval required)
2. Open any contact record and click the Syftplus Chrome extension icon
3. Review the ECS-scored email suggestions and push your chosen result to the Email field
4. For bulk enrichment, use the Syftplus Reports job to enrich entire account segments automatically

Why ZoomInfo coverage thins out in certain markets

ZoomInfo's database is built predominantly from US and European contact data. Teams selling into local and regional markets frequently encounter lower match rates and stale email addresses for companies not well-represented in global databases.

This isn't a criticism of ZoomInfo — it's a structural reality. Their data sourcing methods (web scraping, third-party contributions, email verification networks) are more mature in the markets where B2B SaaS adoption has been historically concentrated.

What Syftplus does differently

Syftplus doesn't maintain a contact database at all. Instead, it reads the confirmed email activity already stored in your Salesforce org and derives email patterns for companies you've previously sold into or interacted with.

This approach has a counterintuitive advantage: your Salesforce activity data is highly localised to the markets you sell into. Syftplus gets more accurate the more you sell into a specific market — which is precisely the opposite of a generic contact database.

Typical use case: enriching contacts ZoomInfo missed

A common workflow for enterprise B2B teams:

1. Use ZoomInfo to pull a list of target accounts and contacts into Salesforce
2. For contacts where ZoomInfo returned no email or a bounced email, run Syftplus
3. Syftplus checks your Salesforce activity history for confirmed emails at that domain
4. If a pattern exists, it returns an ECS-scored email suggestion you can push to Salesforce and sequence

Coverage at regional and local companies

Where Syftplus particularly outperforms external databases is at companies that aren't well-represented in global databases: government-linked corporations, local financial services firms, regional telcos, domestic e-commerce players. These organisations interact with your Salesforce contacts through existing email threads — which Syftplus can decode.

How the modern outbound stack fits together

Most high-performing enterprise B2B sales teams run a stack that looks something like this: Salesforce as the system of record, ZoomInfo or Lusha for prospect discovery and contact data, Outreach or Salesloft for sequencing and cadence management, and Gong or Chorus for conversation intelligence.

Syftplus sits at the CRM data layer — specifically at the contact enrichment step that runs after a contact enters your Salesforce org and before it enters your sequencing tool.

Syftplus + ZoomInfo

Use ZoomInfo to identify net-new accounts and pull contacts. When a ZoomInfo-sourced contact lands in Salesforce without a valid email — or bounces on the first send — run Syftplus. Its Email Identifier Technology reads your Salesforce activity history to derive the email pattern at that domain and returns a confidence-scored suggestion.

Syftplus + Lusha

Lusha excels at individual contact lookups from LinkedIn and web. It's fast for one-at-a-time prospecting. Syftplus complements it for account-level enrichment: if you're targeting an account where Lusha found the VP but missed the Director, Syftplus can fill that gap using the confirmed email format at that domain.

Syftplus + Outreach

Outreach sequences require a valid email before a contact can be enrolled. Syftplus reduces the "can't add to sequence — no email" friction by providing a confidence-scored email suggestion directly inside Salesforce, before the contact syncs to Outreach. High-ECS contacts can be pushed to the Email field automatically via Syftplus's bulk Reports job.

Syftplus + Gong

Gong captures conversation intelligence from your calls and emails. When Gong surfaces a contact mentioned in a deal conversation who isn't yet in Salesforce — or a contact whose email is missing — you can use Syftplus to enrich that contact using the established email pattern at their company domain.

Why CRM email enrichment matters

Contacts enter your CRM through many channels: inbound forms, trade show badge scans, outbound prospecting lists, imported CSVs, manual entry by reps. Many arrive without a verified email address. Others have emails that worked once but are now bouncing.

A database where 20–30% of contacts lack valid emails isn't unusual — and it represents a material pipeline leak. Contacts you can't email can't be sequenced, can't receive campaigns, and can't move through your funnel.

Step 1: Audit your email coverage

Before enriching, understand the scope. In Salesforce, build a report on your Contacts object filtered by: Email field is blank, OR email bounced in the last 90 days. This gives you your enrichment target list.

For most teams this is a larger number than expected — and it's the starting point for everything that follows.

Step 2: Segment by enrichment approach

Not all contacts can be enriched the same way. A useful segmentation:

• Contacts at companies you've emailed before: Syftplus can derive the email pattern from your Salesforce activity history. High confidence, no external lookup needed.
• Contacts at companies new to your CRM: External tools (ZoomInfo, Lusha, Apollo) or manual research required. Syftplus won't have pattern data for these domains yet.
• Contacts where the person is new but the domain is known: Syftplus's sweet spot — apply the known email format to the new contact name.

Step 3: Run Syftplus for pattern-derivable contacts

For Segment 1 and Segment 3 contacts, run Syftplus's bulk Reports job. Set it up in the Syftplus admin portal with your target Salesforce report (the audit you built in Step 1), set your ECS threshold, and schedule it to run overnight.

By morning, every contact where Syftplus found a derivable pattern will have a confidence-scored email suggestion ready for review or auto-push.

Step 4: Define your ECS policy

Work with your RevOps or Sales Ops team to define what action each ECS tier triggers:

• Strong (70+): Auto-push to Salesforce Email field. Enrol in sequence.
• Medium (30–69): Push to a secondary field. Flag for rep review before sending.
• Weak (0–29): Queue for manual research or external lookup tool.

Step 5: Validate and monitor

After the first enrichment run, set up a Salesforce report tracking your email bounce rate over the next 30 days. A well-configured Syftplus deployment typically reduces bounces by 60–80% on enriched contacts.

The cold contact problem

A contact goes cold for many reasons: the sequence ended, the rep moved on, the quarter closed and priorities shifted. But a significant fraction of "cold" contacts are actually unreachable — their email bounced silently, a role change made the address stale, or the email was never verified in the first place.

The opportunity in these contacts is real. A reopened account from a "cold" contact often converts faster than a net-new prospect — there's prior context, prior relationship, prior deal history in your CRM.

Finding cold contacts in Salesforce

In Salesforce, build a report on Contacts or Leads filtered by: Last activity date older than 90 days, AND either email field is blank OR email delivery status is bounced. This is your cold-but-enrichable target list.

Using Syftplus to re-engage cold contacts

For each contact on that list, Syftplus checks whether there's a confirmed email activity pattern at that company domain in your Salesforce org. If there is — whether from current colleagues, from past deals, or from your own outbound history — it derives a new email address suggestion with an ECS confidence score.

A Strong-tier ECS result on a cold contact is a direct re-engagement opportunity: you have a high-confidence email address for someone who already knows your brand, backed by CRM-derived evidence rather than a third-party database entry.

Automating cold contact enrichment

Rather than running enrichment manually on cold contacts, use Syftplus's Scheduled Reports job to automate it. Set up a Salesforce report for your cold contact segment and schedule Syftplus to re-check it weekly. As your CRM activity history grows, more domains become enrichable — contacts that couldn't be enriched three months ago may be enrichable today.

Why deliverability matters more than most teams realise

A bounce rate above 5% is a danger zone for most email providers. Once your sending domain accumulates enough bounces, ISPs start routing your emails to spam — for everyone, not just the contacts that bounced. This is a compounding problem: bad data in your CRM doesn't just affect one campaign, it degrades every campaign that follows.

The typical culprit is stale or unverified email data in Salesforce. Contacts imported from trade shows, old CSVs, or prospecting tools without verification carry high bounce risk.

Step 1: Identify your high-risk contacts

In Salesforce, create a report on contacts who bounced in the last 90 days. Segment by source: which lead sources contribute the most bounces? This tells you where your data quality problem originates.

Step 2: Enrich rather than delete

The instinct is to delete bounced contacts. A better approach: attempt enrichment first. A bounced contact may be reachable at a new address, particularly if the bounce reason was "address changed" or "user unknown" rather than "domain does not exist."

Syftplus can enrich bounced contacts by deriving the current email format at their company domain from your confirmed Salesforce activity history. If a derivation is possible with Strong ECS confidence, the contact is rescuable.

Step 3: Implement ECS-gated sequencing

Work with your Outreach or Salesloft admin to add an ECS filter before contacts enter sequences. Only contacts with verified or Strong-ECS enriched emails should be enrolled automatically. Medium-ECS contacts require rep review. Weak-ECS contacts should not be enrolled until manually verified.

Step 4: Automate ongoing database hygiene

Schedule a Syftplus bulk enrichment job to run weekly on a Salesforce report of contacts with no email or bounced email status. This keeps your database current as your CRM activity history grows — new confirmed emails at a domain make previously un-enrichable contacts enrichable.

Why rep-driven enrichment fails at scale

When enrichment is left to individual reps, coverage is inconsistent. Some reps enrich every contact before sequencing; others skip it entirely. The result is a Salesforce database where data quality varies by rep behaviour rather than by deliberate policy — and where your email deliverability is hostage to whoever last touched a contact.

RevOps teams should own enrichment as an infrastructure layer, not a rep task.

Architecture: the enrichment pipeline

A well-designed enrichment pipeline for a Salesforce org has three layers:

1. Ingestion layer: When a contact enters Salesforce (from any source), a flag is set: "needs enrichment."
2. Enrichment layer: Syftplus's scheduled Reports job runs nightly on all flagged contacts. Results are written to the Salesforce Email field (for Strong-tier) or a review field (for Medium-tier).
3. Sequencing gate: Outreach or Salesloft syncs only contacts with a verified or Strong-ECS email address. Medium-tier contacts route to a rep review queue. Weak-tier contacts are held back.

Setting up the Syftplus Reports job

In the Syftplus admin portal, navigate to Scheduled Jobs and create a new enrichment job. Connect it to a Salesforce report containing your target contact segment. Set your ECS threshold for auto-push (typically 70 for Strong-tier). Set the schedule — most teams run nightly at 02:00 to avoid business-hours API contention.

Defining and documenting your ECS policy

Every RevOps team should have a documented ECS policy. Ours is a starting template:

• ECS 70–100 (Strong): Auto-push to Email field. Enrol in default outbound sequence.
• ECS 30–69 (Medium): Push to Email_Enriched__c custom field. Route to rep review queue in Salesforce. Enrol only after rep approves.
• ECS 0–29 (Weak): Log to an enrichment audit report. Route to manual research queue. Do not enrol in sequences.

Measuring the impact

Track these metrics monthly: email coverage rate (% of contacts with a valid email), bounce rate on outbound sends, sequence enrolment rate, and pipeline generated from re-enriched contacts. The last metric is often the most striking — pipeline from contacts that would otherwise have been stuck in "no email" limbo.

The Gong-to-Salesforce contact gap

Gong captures every person mentioned in your calls, emails, and meetings. When a prospect mentions "you should also talk to our Head of Procurement, Lily Tan," Gong logs it. When your rep manually creates Lily Tan as a contact in Salesforce, she often arrives without a verified email address.

This is where Syftplus steps in.

How the Syftplus + Gong workflow runs

1. Gong surfaces a new stakeholder mentioned in a deal call
2. Rep creates the contact in Salesforce with name, title, and account — no email yet
3. Syftplus's nightly enrichment job picks up the new contact
4. Syftplus checks your Salesforce activity history for confirmed email patterns at that company domain
5. If a pattern exists, it derives the email (e.g. lily.tan@company.com.sg) and returns it with an ECS score
6. Strong-tier results are auto-pushed to the Salesforce Email field. The contact can now be sequenced immediately.

Why this works particularly well for complex enterprise deals

Enterprise deals typically involve more stakeholders than a rep initially maps. Gong excels at surfacing these late-stage contacts — the technical evaluators, the procurement leads, the CFO who appears in the final call. These contacts are often at companies you've been selling into for months, which means Syftplus is likely to have strong pattern data for their domain.

Setting up the integration

There's no direct Gong-Syftplus connector required. Both tools work through Salesforce. Gong writes its insights to Salesforce objects; Syftplus reads from Salesforce contacts and activity history. As long as Gong is syncing to your Salesforce org and Syftplus is installed, the enrichment pipeline runs automatically on any new contact, regardless of how it was created.