Trellus for lemlist

Turn lemlist call tasks into a parallel calling block

Keep the campaign, contact, and task context in lemlist. Trellus works the call rows your rep chose, then returns the note, task action, sequence pause, or callback after lemlist acknowledges it.

lemlist's own dialer is the clean choice for one call at a time with lemlist numbers, credits, recordings, and call controls. Trellus adds a separate parallel workflow.

Where Trellus works in lemlist

Starts in: Tasks, a campaign Lead list, or one contact
Queue: the selected current work
Calling: Trellus power or parallel
After the call: contact note, call status, and Task result
Follow-up: native lemlist callback Task
Product walkthrough

Watch Trellus start from lemlist Tasks

The recording shows the platform-specific starting surface and call flow. see your own selected-row behavior, phone fields, campaign rules, and acknowledgements before a team-wide use.

Trellus walkthrough for lemlist. It does not demonstrate lemlist-native phone controls or every workspace configuration.

Where it works

The lemlist starting points Trellus understands

The source matters because a task, a campaign lead, and a one-off contact do not have the same follow-up controls.

Current lemlist Tasks

Use the call-task filters your rep intends to work. When rows are selected, Trellus keeps the queue scoped to those task IDs instead of silently adding more.

A campaign Lead list

The current campaign's lead list can supply contact context, but those rows are not treated as completable call tasks and do not receive task-only controls.

The current contact

A one-off call keeps the lemlist contact and available phone context attached without pretending a campaign task existed.

Open Trellus callback tasks

A callback Trellus created as a native lemlist call task can return to the queue later with its due date and phone context.

Rep workflow

From selected rows to an saved result

01

Choose the lemlist work

Filter Tasks, select selected rows, open a campaign Lead list, or start from one contact.

02

Confirm the phone field

Review the default or mapped phone fields. Unusable duplicates are removed; unusual custom fields need an explicit mapping check.

03

Run the Trellus call block

The active answer retains the lemlist contact, campaign, task, and chosen phone context.

04

Choose the real post-call action

Write a note, complete an task with a known lemlist status, explicitly pause an lead, or schedule a callback.

05

Wait for acknowledgement

Pause and task-completion checkpoints are ordered so a failed pause does not quietly advance the campaign.

Choose the right dialer path

lemlist Focus mode or Trellus?

Stay with lemlist's dialer

Use native Focus mode when Mark as Done and Call next is fast enough and the team needs lemlist phone numbers, minutes, recordings, transfers, reporting, and native call-status automations.

Add Trellus for parallel work

Use Trellus when the same lemlist Tasks or campaign context should remain visible but the rep's bottleneck is the number of separate attempts required to reach a live person.

What can return

Separate actions, each with its own scope

A generic “two-way sync” would hide the important parts. The note, task completion, optional lead pause, and callback are distinct lemlist operations.

Structured contact note
Known lemlist call status
task completion
sequence pause
Native callback task
Stable retry key
Concrete example

Eighteen tasks—not the whole campaign

Maya filters a 42-task event campaign, then selects the 18 accounts in her territory. Trellus verifies those task IDs and uses a mapped Direct line field. A prospect answers and asks for the security overview before Tuesday.

Expected result
Maya chooses Connected positive, adds the note, and schedules Tuesday morning. Trellus writes the structured note, completes the saved call task with the known status, and creates a Trellus Callback Task.
FAQ

lemlist and Trellus

Does lemlist already have a dialer?

Yes. lemlist supports native calls from Tasks and Contacts, one-at-a-time Focus mode, call statuses, notes, recordings, and its own phone-number and minute setup. Trellus adds a separate parallel workflow.

Where does Trellus work in lemlist?

Trellus works with current lemlist Tasks, an campaign Lead list, the current contact, and open Trellus callback tasks in the web app.

What is written back after a call?

The core result is a structured lemlist contact note. tasks can also receive a known native call status and completion after acknowledgement.

Can Trellus pause a lemlist sequence?

Only for an non-manual campaign task with complete context, and only when the rep explicitly requests it. A pause is reversible and is not the same as ending the campaign.

Can Trellus create a lemlist callback?

Yes, in the task path. It creates a native lemlist call task titled Trellus Callback Task with the due date, phone, and available call context.

Does Trellus sync connected CRMs or remove leads from campaigns?

Keep connected-CRM updates in the team’s existing workflow. Trellus can save a reversible sequence pause when the rep requests it.

Test the lemlist campaign you actually run

Bring the Tasks filters, call step, phone fields, completion rules, and follow-up actions. See the full calling and follow-up flow.