Outbound campaign LinkedIn comment replies now get a delivery status (Sent, Failed) so campaign operators know whether a public reply was accepted by LinkedIn, rejected at send time.
What this feature does
When a campaign sends a public comment or nested reply through the LinkedIn connector, the system records what happened after the send attempt: LinkedIn created the reply, or the send failed before creation.
Statuses are posted as delivery notifications for campaign reporting. They apply to the campaign customer identity on that channel (the LinkedIn member being replied to), not to every person who can see the public thread.
Only new text or image replies generate these statuses. Editing or deleting an existing comment does not create a new Sent / Failed event.
Delivery statuses
|
Status |
What it means |
|---|---|
|
Sent |
LinkedIn accepted and created the outbound comment reply. This does not mean the member saw or opened the reply. |
|
Failed |
The reply could not be sent (API, auth, config, media, or other send-time error). |
Not tracked for this channel: Delivered, Bounced or Read/opened. LinkedIn does not provide recipient delivery or read receipts for public comment replies.
Inbound customer comments still work as before in Agent Desk and can be used for reply/engagement reporting. Those inbound comments are not shown as delivery statuses.
Where the campaign operators see this
These statuses appear in the Non Voice Campaign Summary Gold report (columns such as Sent, and Failed for the LINKEDIN channel).
This work is for campaign reporting only. What agents see in Agent Desk stays the same. There is no new Sent / Failed categorization in Agent Desk conversations.
What this means for campaign operators
-
Visibility into which campaign LinkedIn replies were accepted, or failed.
-
Regular inbound comments still work as before in Agent Desk.
-
This tracking is for outbound campaign sends (and the reply signals used for reporting).
What's not included in this release
-
No Delivered status (creating a public comment does not prove a member received a notification).
-
No Read / open tracking.
-
No automatic retry of failed sends from this feature.
-
No new alerting on failures beyond recording the status for reporting.
FAQ
Does this apply to LinkedIn personal profiles or only organization Pages?
This connector path is for organization post comments and nested replies configured in Expertflow. Personal-profile messaging is not covered by this reporting.
Is Sent the same as the member seeing the reply?
No. Sent means LinkedIn created the public comment. There is no later Delivered or Read signal for this channel.
Related pages
-
Outbound — parent hub for outbound campaign documentation
-
X (Twitter) Campaign Delivery Status Notifications - same delivery-notification pattern for the Twitter channel
-
Email Campaign Delivery Status Notifications -same delivery notification pattern for Email channel
-
Facebook Campaign Delivery Status Notifications -same delivery notification pattern for Facebook channel
-
Instagram Campaign Delivery Status Notifications -same delivery notification pattern for Instagram channel
-
SMS (SMPP) Campaign Delivery Status Notifications -same delivery-notification pattern for the SMS channel