resolve_support_conversation

Purpose

Mark a conversation resolved. It leaves the open triage queue and stops competing for the creator's attention.

Required ability

support-conversation:update

Input schema

{
  "type": "object",
  "required": ["conversation_id"],
  "properties": {
    "conversation_id": {
      "type": "string",
      "description": "UUID of the support conversation to resolve."
    }
  }
}

Output shape

{
  "data": {
    "conversation_id": "sup_01HX...",
    "status": "resolved",
    "resolved_at": "2026-08-20T10:12:00Z"
  }
}

Example prompts

"That's handled — resolve the conversation."

"Resolve every support thread I've already replied to today." (list first, then resolve each)

Failure modes

• No support conversation found with that id. — unknown id, or outside the token's project scope.
• TOKEN_MISSING_ABILITY — token lacks support-conversation:update.

Caveats

• Resolving does not notify the member. Send a reply first if they should know the matter is closed.
• Resolving an already-resolved conversation succeeds and emits the event again. Harmless, but deduplicate if you are posting notifications downstream.
• The member's next message reopens the thread automatically and raises support.conversation.reopened. A blocked member's message does not — their thread stays resolved.

Related

• reply_support_conversation
• list_support_conversations
• support.conversation.resolved — the event this raises
• Support conversations API