Steps
1
Match the list
2
Read the result honestly
A row can be matched, not found, or could not verify. The last one means a lookup failed,
for example a rate limit, and is labeled with the reason. Salesfinity never reads a failed
lookup as “not in the CRM”.
3
Bring the CRM context alongside
Any table with CRM matches can carry CRM columns. These are read per row and are free.Available account columns: owner, last activity, next activity, pipeline, deal stage, open
deals, loss reason, tasks, recent engagement, and notes. Contact columns: match, owner,
engagement, and an email summary.
4
Pull a specific CRM field
Any standard or custom property in your CRM can become a column. Say the field in your own
words and the companion finds the matching property in your portal’s schema.If the property does not exist, the companion says so rather than inventing one.
5
Act on the split
What happens behind the scenes
Matching runs against the CRM’s own search, one row at a time, with the lookups that fail recorded separately from the lookups that found nothing. That distinction is what lets the companion say “could not verify” instead of “not there”. CRM columns come from the record’s associations and properties, so what you see is exactly what is in the portal at that moment.Prompts to try
Next
Re-engage closed-lost accounts
Start from the CRM instead of matching to it.
Integrations: how data moves
What happens after you dial a CRM-matched contact.