Skip to content
Lemma

Lemma Help Center

Find the next step

Enter at least two characters

Search by the job or state you see.

Results are grouped by guide, so each article is one keyboard stop.

First setup

Core concepts and state models

Learn how Leads, Senders, Missions, Sequences, and Outbox fit together without mixing their states.

In this collection
On this page

Lemma connects one outbound goal to the people, account, messages, controls, and evidence needed to run it.

The five product concepts

Lead

A person in Lemma. Lists, Mission membership, imported and inferred information, restrictions, and activity stay attached to the Lead.

Sender

The connected LinkedIn account Lemma may use. Identity, readiness, schedule, daily targets, pauses, restrictions, and provider health affect execution.

Mission

One outbound goal that joins a Lead set, research, plan, Sender, Sequences, approval choice, and outcomes.

Sequence

The ordered LinkedIn touches for one Lead in one Mission.

Outbox

The central queue of one Sequence per Lead and Mission. Use it for timing, available actions, replies, problems, and evidence.

Operator and provider confirmation

  • Operator is the public name for the person with full access to Lemma’s outbound controls.
  • Provider confirmation is evidence that LinkedIn or the connected provider accepted an external action. It is stronger than an internal queue or task status.

Keep the state models separate

Mission lifecycle

Public lifecycle labels include Needs input, Active or Live, Paused, Finishing, Completed, and Failed. An unlaunched Manual setup can appear as Draft. A Lemma-led Mission can also show the phase currently being worked: Clarify, Select leads, Research, Plan, Execute, or Monitor.

Outbox views

  • Open — current Sequences.
  • Needs you — Sequences with an action Lemma can currently offer.
  • Finished — completed, replied, opted-out, or stopped Sequences.

Open Sequence facets

  • Ready
  • Scheduled
  • Waiting
  • Paused
  • Problems

These are the filters shown in Outbox. Running and Sent are not top-level Sequence facets.

Touch and delivery evidence

Inside a Sequence, an individual touch can be pending, approved, sending, completed, failed, canceled, or otherwise constrained by its current task state. The detail and history explain whether it is merely planned, in progress, or provider-confirmed.

The row is a summary

Read the Outbox row for the next known step, then open the Sequence for touch-level timing, history, and provider evidence.

Approval is path- and scope-specific

  • Lemma-led Mission: choose Review approval or Auto approval from the Mission. Approve the exact Mission-level request in its conversation.
  • Lemma-authored Sequence: under Outbox → Open, choose Validate sequence to approve and freeze one eligible prospect’s current message bodies. Use Batch validate for an eligible selection or filtered Mission.
  • Manual: the wizard’s Review step checks the exact audience and rendered messages. Launch Mission commits that review. Manual Outbox actions appear only where the current Sequence supports them.

Next action

Read Create a Lemma-led Mission or Build a Mission manually.