Talin and Salesforce

Yes. Talin pushes prospects and their enriched contact details into Salesforce, and pulls records the other way so a prospect who already exists in your CRM is matched rather than duplicated. Every message Talin sends and every reply it receives writes back as a note on the prospect.

Your choice in the sync settings, so Talin matches however your Salesforce pipeline reports: Leads for a qualification flow, Contacts if your BD works accounts directly. Records write in real time or on the trigger you pick.

Yes. Push on import, on enrichment, on first message sent, or on first reply received. Teams that want a clean Salesforce typically choose reply received, so only engaged prospects become records.

About five minutes. You pick Salesforce in Settings → Integrations, sign in to Salesforce and approve the access it asks for, choose which events push records and write notes, and the first sync starts on its own. No engineering, no data migration.

Prospects, with the contact details Talin verified. You choose the trigger: every prospect uploaded to Talin, or only the ones whose email or phone number Talin enriched, so your CRM stays free of records that were never reachable.

No. Talin matches on the identifiers Salesforce already holds before it writes, so an existing prospect gets updated and noted instead of re-created. You can also have Talin pull prospect emails that already exist in your CRM so it never spends a credit re-finding them.

Every event is a switch. Push on upload or on enrichment; add a note when a prospect receives a message, when they reply, or when they enter and leave a campaign; include the full message body in notes or keep them to the headline. Change any of it later without reconnecting.

Syncing stops and nothing is deleted. Records and notes Talin already wrote stay in Salesforce, and your Talin campaigns keep running. Reconnecting picks the sync back up with your previous settings.