support.conversation.resolved
A support conversation is marked resolved and leaves the open queue.
When this fires
A conversation is marked resolved from the dashboard inbox, the REST API, Zapier, n8n, or the resolve_support_conversation MCP tool.
Resolving is not closing. The thread and its full history are kept, and it reopens by itself the moment the member writes again, which raises
support.conversation.reopened.
Caveats
- Resolving does not notify the member. If you want them to know the matter is closed, send a reply before resolving.
- The event fires even if the conversation was already resolved. Deduplicate on
id. - A resolved conversation still counts toward the member's history and still appears under the Resolved tab in the inbox; it is filtered out of the open queue, not deleted.
Related events
support.conversation.reopened: what happens when the member writes back.support.message.sent: the reply that usually precedes resolving.
Header Parameters
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Request Body
application/json
The signed JSON envelope posted to your endpoint.
TypeScript Definitions
Use the request body type in TypeScript.
The envelope every event is delivered in.
Response Body
Example Requests
/support.conversation.resolvedHow is this guide?