Version
DESTRUCTIVE

unblock_support_contact

Let the member behind a support thread write in again after block_support_contact. Messages dropped while blocked are gone.

Lift a block placed with block_support_contact. From this moment the member's messages reach the inbox again, and their next message can reopen a resolved thread as anyone else's would.

Nothing is recovered. Messages sent while the block was in place were dropped at ingestion, not held, so there is no backlog to release. Only what the member writes after this call arrives.

Emits support.conversation.unblocked when the block is lifted. Idempotent: unblocking a member who was not blocked changes nothing and emits nothing.

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Delivered to every endpoint subscribed to it once the change is made.

Annotations

DestructiveIdempotent

A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time.

Arguments

conversation_id*string

UUID of the support conversation whose member to unblock.

What it returns

{  "data": {    "id": "9e042b6f-5d81-4c37-a920-7b3e18cf6d45",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "channel": "telegram",    "status": "resolved",    "assigned_to_user_id": null,    "unread_count": 0,    "blocked": false,    "first_response_at": "2026-08-20T10:12:00+00:00",    "resolved_at": "2026-08-21T09:30:00+00:00"  }}

status is whatever it was before — unblocking does not reopen the thread. The member's next message will, or reopen_support_conversation can.

How it fails

VALIDATION_FAILED

the token's owner is on the project's team but their role lacks the support permission on it.

RESOURCE_NOT_FOUND

unknown conversation_id, another creator's thread, or a project outside the token's scope:project: allow-list.

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks support-conversation:update.

How is this guide?

Last updated on