A short tour of every tool in the portal — what it does, when to reach for it, and the guardrails that keep your CRM tidy.
The vendor flow is built around a single contract: check before you submit.
Open Account, sign in, then paste your API key to bind it to this session. We tie it to your sign-in so you don't have to re-enter it on every check.
Use Check Leads → Individual for one-off lookups, or Bulk Upload to score an entire workbook in parallel.
Validate Leads runs schema and row-level checks against your workbook. Submission is gated until all ERROR rows are fixed.
Every check returns one of three verdicts and a recommended action.
A confident hit on email or phone — the lead already exists in CRM.
Partial signal (e.g. fuzzy company match, last-10-digit phone). Worth a human eye before submitting.
Nothing meaningful overlaps with existing records.
Conflict signals
When the email and phone you sent point at different records in our CRM, we flag the row as a conflict. It's worth a human review before you submit.
Two complementary tools for getting a clean workbook over the line.
Drop an .xlsx, .xls, or .csv and we score every row in parallel. Big runs throttle themselves automatically so you don't have to, and you can export the annotated results as a CSV when the run finishes.
Schema, format, US state, ZIP+4, and free-text checks run server-side. Rows are grouped by severity:
Validate Leads expects Microsoft Excel .xlsx workbooks. Bulk Check is more permissive — .xlsx, .xls, and .csv all work. The first sheet must use the canonical headers shown in the template.
Each row comes back with one of three verdicts. EXACT_MATCH means we found a confident duplicate; POSSIBLE_MATCH means part of the row overlaps and a human should look; NO_MATCH means the row is clear to submit.
When the email and phone you sent point at different records in our CRM, we flag the row as a conflict. It's worth a human review before you submit.