Unsubscribe and bounce handling

Unwanted contact.Record it. Respect it.

Carry opt-out and failure records into future work.

LDG-029Implemented; configuration required
See how to use it
Lingdonggu sending-task history showing one old test task submitted, with empty unsubscribe and bounce lists below
Task history and unsubscribe/bounce directory· Real system screenshot

An old rich-text attachment test task shows submission complete; unsubscribe and bounce lists are empty. This does not prove current queue delivery or customer receipt. No queue controls were executed.

Unsubscriptions retain restrictions.
Bounces with reasons to check.

Carry opt-out and failure records into future work.

This feature's focus3

contact-status record types

Source: unsubscribed, bounced, and blocked addresses. Reimporting does not automatically lift restrictions.

See this feature's highlights.

real work.
Details worth exploring.

Unsubscriptions retain restrictions.

Review unsubscribed, bounced and blocked addresses.

See the actual steps

Bounces with reasons to check.

Retain handling records and contact restrictions according to actual receipts.

See the actual steps

Blocked addresses for future checks.

Keep checking existing states when preparing another list.

See how to check

Understand the tool and human handling separately

What the tool handles.
What you decide.

Feature assistance

Unsubscriptions retain restrictions.

Carry opt-out and failure records into future work.

Retain handling records and contact restrictions according to actual receipts.

Your review

3 key points.
After confirmation, continue.

  1. Provider acceptance does not mean final delivery.
  2. Reimporting does not automatically remove existing restrictions.
  3. Do not ignore an opt-out because the list has changed.

This compares feature handling scopes. Scenarios explain the sequence, not measured efficiency or completed customer cases.

Explain the feature through real work

This time.
Record it.

Suppose an unsubscribed address appears again in a new list.

Hypothetical scenario · Feature explanation, not a customer case or completed AI result
Previous handling steps

Treat it as a new contact eligible for outreach after reimporting.

With this feature

Continue checking existing restrictions and exclude addresses that should not be contacted.

When to use it

Prepare first.
Make this task specific.

When an unsubscribe, bounce or block occurs, carry that status forward into future list checks.

01

Status evidence

actual opt-out requests, receipts and block records.

02

Recipient information

the corresponding address and current task.

Complete steps

From the start.
To the next step.

Save unsubscribed, bounced and blocked addresses to avoid contacting people who opted out. Reimporting does not automatically remove restrictions. Check actual statuses separately for provider acceptance, delivery and replies.

01

Review unsubscribed, bounced and blocked addresses.

02

Retain handling records and contact restrictions according to actual receipts.

03

Keep checking existing states when preparing another list.

Connect the work from step to step

Make this step clear.
Connect the next step.

When editing the next task's list, retain opt-out and exception evidence and verify communication scope against actual status.

Return to Email and WhatsApp · Linbo for the complete workflow

Understand before use

Bring the actual conditions.
Continue this step of the work.

Reimporting does not automatically remove restrictions. Final delivery and replies follow actual status.

Product facts and FAQsBack to the product feature directory

More details in this product

Connection routes and conditions

Understand the usage conditions of each integration route separately.

Explore this feature on its own