Forward a message to somebody else
Sends one message of the thread onward with a note, as a NEW email carrying no threading headers — a colleague’s answer must never land in the prospect’s conversation. The original’s attachments ride along. Recorded on the thread for the record, but the conversation’s last activity is left alone.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Response
Successful Response
NEW-A: hard vs soft severity of a BOUNCE message.
Only HARD marks the contact bounced (§29's condition, the enrolment analytics bounce rate, §57's per-message outcome) — SOFT still fills the Bounces view and never looks like a reply, but the address may still be reachable, so the cadence is left alone.
hard, soft INB-25: this message's own channel. Threads merge channels, so the reader captions each message by what it actually is — a LinkedIn DM involves no email addresses.
email, linkedin outbound, inbound What an inbound message turned out to be.
REPLY stops the cadence; BOUNCE (a DSN) marks the contact bounced and never looks like a reply; OUT_OF_OFFICE never stops anything and defers the cadence to the stated return when one is parsed.
reply, bounce, out_of_office Whether a message has actually left.
Only meaningful on LinkedIn. An email row is written after the provider
accepted it, so it is SENT the moment it exists; a LinkedIn reply is
written when it is QUEUED, and cannot become SENT until the customer's
own browser has delivered it. Showing the two the same way would have the
product assert a delivery it has no evidence for.
sent, queued, failed INB-09: the sender's raw HTML part; sanitise before rendering.
§78: the sequence this message was sent from, when it came from one.
§78: which step sent this message — carried per-message (not just on the thread) because a contact re-enrolled in a different sequence keeps their earlier messages' own sequence/step, distinct from the thread's current one.