Find out why your lemlist campaign stopped getting replies

Reading the numbers, then reading the messages

The stats tool wants a date range, which forces the useful question: compared to when.

A companion pulls sent, opened, clicked, replied, bounced and unsubscribed counts for that window, then lists the leads by state, reads who the bounced ones were, and looks at what the repliers actually said.

The diagnosis is specific enough to act on: thirty-one of the last hundred were at companies under ten people, and every one of them ignored step two.

How do you stop outreach to one person without erasing the history?

Unsubscribe rather than remove.

lemlist keeps the record and the history when you unsubscribe a lead; removing deletes it. The integration defaults to unsubscribe and deletes only when someone asks explicitly.

Pause, resume, unsubscribe and remove all wait for you. Each one needs an explicit confirmation on top of your approval before it runs.

Credits and seats, checked before the ask

A companion reads the enrichment and verification credit balance before proposing any work that consumes it, and lists the team’s sender seats so you know which mailboxes are carrying the campaign this week.

Both are one lookup each and both change the plan. You hear “add these two hundred leads, knowing enrichment covers about ninety of them and two of your five senders are unassigned”.

Why does the diagnosis need a browser at all?

Because the numbers say what happened and the web says why.

A campaign that dies at step two might be badly written, or it might be pointed at companies that stopped hiring for the role your offer assumes. That evidence is on their careers page.

A companion reads both sides in one sitting: the campaign data through the native tools, the recipient companies through the tabs it opens. For the marketing-side version of the same loop see marketing; for the outbound side it is the tail end of sales prospecting.

Frequently asked questions