Salesforce Call Result now sets the lemlist call status

If your reps call from outside the lemlist dialer (Nooks, Aircall, Orum, or Salesforce native calling), lemlist can now pick up the outcome. When a rep completes a lemlist call task in Salesforce and selects a Call Result, lemlist reads it, converts it into the matching call status, and completes the task with that status. From there, everything runs as if the status had been picked in lemlist: Interested / Not interested and stop the campaign, pause options, the verdict on the phone number, and call status reports.

  • Uses the mapping you already set in Settings > CRM > Activities (one Call Result value per call status), read in the other direction. A status with no mapped value matches on its name.

  • Matching ignores case and surrounding spaces.

  • An unknown or empty Call Result completes the task without a status, and the lead keeps going, same as before.

  • Your Call Result value in Salesforce is never rewritten.

  • A new warning appears in Settings > CRM > Activities if two call statuses share the same Call Result value, since a matching call will get the first status in the list.

We also fixed an issue across Salesforce, HubSpot, Pipedrive, and Attio where lemlist was completing a task a second time in the CRM right after the rep completed it, which could re-trigger the customer's own workflows on task updates.

This is live for all Salesforce teams, no beta flag. It only applies when the Call Result is set on the Task lemlist created — if your dialer creates its own task or call instead, nothing changes. A Call Result added after the task was already completed is ignored, and tasks completed before this release aren't replayed. HubSpot and Pipedrive support is coming next; Attio has no call result to read.