Dropcontact

@Dropcontact I have a CSV of 120 leads from our last conference. Can you enrich them with verified emails and company details?

I've submitted your 120 contacts for batch enrichment. Dropcontact is now validating email addresses, appending missing company information (industry, size, location), and cross-referencing against their B2B database. The request ID is `req_8x3k9m2p`. Enrichment typically completes in 2-5 minutes depending on data complexity. I'll retrieve the results once processing finishes, then return a summary showing which contacts gained verified emails, which companies were identified, and any records that couldn't be matched.

This example shows Dropcontact's core batch-enrichment workflow. The MCP handles up to 250 contacts per request. You'll need an API key with sufficient credits — each enriched contact consumes one credit. The tool submits the job asynchronously, so you must poll or use webhooks to retrieve results; immediate responses aren't guaranteed.

@Dropcontact retrieve the enrichment results for request `req_8x3k9m2p` and show me which contacts now have verified work emails.

Enrichment complete for request `req_8x3k9m2p`. Out of 120 contacts: 87 now have verified work emails (SMTP-validated), 31 had emails corrected or appended, 12 remain unverified due to insufficient data. Company details were enriched for 104 records, including industry classification and employee count. 16 contacts couldn't be matched to a company in Dropcontact's database. The full dataset includes confidence scores for each field — emails marked 'high confidence' passed deliverability checks, while 'medium confidence' entries may need manual review.

This read-heavy example demonstrates result retrieval after batch processing. Dropcontact returns structured data with confidence scores, so you can filter by quality thresholds. The MCP surfaces these scores, but interpreting them (e.g., deciding whether to email 'medium confidence' addresses) requires your judgment. Results expire after 30 days in Dropcontact's system.

@Dropcontact list my active webhook subscriptions so I know which enrichment events are being pushed to our CRM.

You have 2 active webhook subscriptions configured: (1) `webhook_7a4n` listening for `enrichment.completed` events, posting to `https://crm.example.com/api/dropcontact-ingest` — this fires whenever a batch finishes processing. (2) `webhook_2m9x` listening for `email.bounced` events, posting to `https://alerts.example.com/bounces` — this triggers if an enriched email later hard-bounces during a campaign. Both webhooks are set to retry up to 3 times on delivery failure. No subscriptions are currently paused or failing.

This example highlights Dropcontact's webhook infrastructure for real-time integration. Webhooks let you push enrichment results directly into your CRM or data warehouse without polling. The MCP lists subscriptions but doesn't create or delete them — you'll manage webhook lifecycle through Dropcontact's dashboard or a separate API call. Ensure your endpoint can handle Dropcontact's payload schema and respond with 2xx status codes to avoid retries.

When Dropcontact saves a sales team from bounce hell

A 6-person sales team exports 200 leads from a conference signup sheet and needs valid emails before the first outreach. Dropcontact's batch enrich tool validates emails and appends company data in one pass, catching typos and dead addresses before the campaign goes out. The API key setup takes under five minutes, and the 250-contact batch limit matches most weekly prospecting volumes. If your list is over a thousand contacts or you need real-time enrichment during live calls, you'll hit the batch ceiling fast and need a streaming solution instead. For teams running weekly or bi-weekly cold campaigns with clean CRM hygiene, this MCP turns a half-day manual scrub into a ten-minute API call. Worth the seat if your bounce rate is above 8 percent.

Why this MCP works for post-event lead enrichment

A 3-person marketing team collects 180 business cards at a trade show and wants to route leads by company size and industry before the first follow-up email. Dropcontact's enrichment pulls firmographic data and validates contact info in a single batch request, letting the team segment leads in their CRM the same afternoon. The webhook subscription tool notifies Slack when enrichment finishes, so no one has to poll the API manually. If your event pipeline is under 250 contacts per show and you have a week to follow up, this MCP handles the append without custom scripting. Teams running multiple events per month or needing same-day turnaround should budget for a higher-tier plan or a real-time enrichment service. For quarterly or monthly event cycles, Dropcontact keeps your follow-up data clean without hiring a VA.

When Dropcontact isn't the right call for live support

A 4-person support team gets 40 inbound tickets daily from users who forget to include their company email, and agents need to validate contact info before escalating to account managers. Dropcontact's batch enrichment works, but the 250-contact ceiling and async retrieval model add friction when agents need answers in under two minutes during a live chat. The retrieve-results tool requires polling by request ID, which doesn't fit the support workflow where each ticket is a one-off lookup. If your support volume is under 10 tickets per day and you can batch-enrich overnight, this MCP works as a nightly cleanup job. For real-time ticket triage, a synchronous lookup API or a CRM-native enrichment plugin will close tickets faster than a batch-first MCP.