Skip to main content
Every call you log ends up on the record it belongs to, in the platform the contact came from. You log once in Salesfinity, and the rest happens in the background. Salesfinity never becomes a second CRM. It copies people in so you can dial them fast, and writes everything that happened on the call back out.

​
Inbound: from your platform into Salesfinity

An import is a snapshot. Salesfinity reads the list, report, sequence or due tasks you chose and copies each person into a Salesfinity contact list. For every contact it keeps:
  • The fields from your field mapping: name, title, company, email, phone numbers and any custom fields.
  • The source (HubSpot, Salesforce, Outreach and so on) and the record ID there. Task imports also keep the task ID and, where the platform has them, the sequence and step.
  • The list name, taken from the platform’s list, report or sequence.
The list’s contacts are replaced with a fresh copy, in the same Salesfinity list. Each contact’s latest disposition carries over, and call history is kept. Edits made in the CRM after an import only show up once you import again.One exception: a list that Boss Mode has already checked is never overwritten. Importing it again creates a new list with the same name next to it.
It fails with No active call tasks found, whether you picked a list or imported your due tasks. See Fix integration problems.
Contacts you upload from a CSV or add by hand have no source record. They are still matched to your CRM when you log a call, as described below.

​
During the call

The live transcript, recording, AI notes and the disposition you pick all stay in Salesfinity until you log the call. Nothing is written to your CRM mid-call.

​
Outbound: from the call log to your platform

When you log a call, Salesfinity saves it right away and marks it queued. A background worker does the rest, so logging never waits on a CRM.
1

Wait for the recording and transcript

For recorded calls longer than five seconds, the worker waits for the recording link and transcript, so the activity in your CRM carries the recording. It checks once a minute, up to 15 times. If the recording still has not arrived, the call syncs without it rather than being dropped.
2

Send it to the platform it came from

A contact from HubSpot, Salesforce, Outreach or another integration is logged back to that platform, using the stored record ID. See what lands in HubSpot, Salesforce and Outreach.
3

Fan out contacts with no source

A CSV or custom-list contact is logged to every CRM you have connected among Salesforce, HubSpot, ActiveCampaign and Attio, at the same time. Salesfinity looks the person up in each CRM by LinkedIn URL, email or phone number, and creates the record if nobody matches. A CSV contact that already carries a Salesforce or HubSpot ID is logged only to that CRM.Two more sources take this road. A Lemlist contact has its Lemlist task completed first, because Lemlist has no call activity to write, and then fans out to your CRMs. A row on the Sequencer (early access) dial list goes to the HubSpot or Salesforce record it was enrolled from when it carries that ID, and fans out like a CSV contact when it does not.
4

Close the task

If the contact was imported from a task, that task is completed in the platform. In Outreach the sequence step moves on. In Salesforce an active cadence step is marked complete.
5

Record the result

The call log stores the ID and link of the activity created in each platform, and its sync status updates. Call history shows it in the Sync status column. Hover an Error or Warning badge to read the reason.

​
Sync states

Salesfinity retries a failed sync on its own, up to five attempts one minute apart. The status reads Error or Warning between attempts and turns to Success when a retry lands. There is no manual retry button. A retry only writes to the platforms still missing the call, so a partial failure never creates duplicates.

​
Keep deals current with Ari

Logging a call puts the activity on the record. Deal fields, such as stage, next step or close date, still need someone to update them. Ari can do that from what was said on the call. Ask Ari in the chat panel after a call: Ari reads the call, then shows you each field it wants to change. Nothing is written to your CRM until you approve. Ari can update HubSpot and Salesforce records, and is available on Enterprise and Enterprise+ plans.

​
Other things that flow between systems

  • Phone numbers. A number found by enrichment or edited in the dialer can be pushed onto the CRM record, so your next import already has it.
  • Sequences. Adding, moving or removing someone in a sequence from the dialer writes straight to the platform’s sequences. See the sequence section on each platform guide.
  • Gong. When Gong is connected, recorded calls of at least ten seconds that were not voicemails are uploaded under the rep’s mapped Gong user. The upload runs in its own queue, so a CRM problem does not hold it up. See Send your calls to Gong.
  • Calls made in other dialers. Calls made in a connected platform’s own dialer can be pulled into Salesfinity, transcribed and turned into follow-up tasks. Your follow-ups then cover calls made anywhere.
  • Your own systems. Every logged call is also available through webhooks (set up under Settings › Connections › API & Webhooks), the REST API and the MCP server. These read from Salesfinity’s call log and do not depend on the CRM sync. Start at the developer portal.

​
Where credentials live

Each integration stores a sign-in session or API key per Salesfinity user and team. Tokens refresh automatically in the background, and each platform guide says when a reconnect is needed. Disconnecting deletes the stored credentials first and then the integration’s settings, so a failed disconnect can be retried safely.

​
Next steps

Fix integration problems

What to do when a call shows Error or Warning.

Connect HubSpot

See exactly what lands on a HubSpot contact.

Connect Salesforce

See exactly what lands on a Salesforce record.

Meet Ari

Keep your CRM current without typing.