support.conversation.unblocked

When this fires

A creator lifts the block on a support conversation:

• Dashboard: Unblock member in the thread's header menu in the support inbox.
• REST: POST /v1/support/conversations/{conversation}/unblock.
• MCP: the unblock_support_contact tool.

It does not fire when:

• The conversation was not blocked. Unblocking an unblocked thread writes nothing and emits nothing; the call is idempotent.
• A banned member is unbanned. That is member.unbanned; a ban and a support block are independent, and lifting one does not touch the other.

Unblocking restores the flow of new messages. It does not replay anything the member sent while blocked; those messages were dropped at ingestion and are gone.

Caveats

• The thread's status is unchanged by an unblock, exactly as it was by the block. A thread that was resolved when blocked is still resolved now; the member's next message will reopen it and raise support.conversation.reopened as usual.
• Nothing is replayed. If the member wrote in while blocked, those messages produced no support.message.received and never will.
• The payload does not say how long the block lasted. Pair this event's created_at with the matching support.conversation.blocked by conversation_id if you report on it.

Related events

• support.conversation.blocked: the state this event reverses.
• support.conversation.reopened: what the member's next message may now trigger.

Header Parameters

The signed JSON envelope posted to your endpoint.

Response Body