---
title: "A support conversation is handed to a team member, or its assignment cleared."
method: POST
path: "support.conversation.assigned"
tags: ["support.* events"]
---

# A support conversation is handed to a team member, or its assignment cleared.

`POST support.conversation.assigned` (webhook)

### When this fires

A conversation's assignee changes: it is handed to a team member from the dashboard inbox, the REST API, Zapier, or n8n, or an existing assignment is cleared.

> Clearing an assignment fires this same event with `data.assigned_to_user_id: null`. There is no separate "unassigned" event; branch on the null.

### Caveats

- `assigned_to_user_id` is a **team member's** user id, an account with dashboard access, not the member's `subscriber_id`. The two are different namespaces.
- Assignment is advisory. It does not restrict who may reply; anyone on the team with `support-conversation:update` still can.
- Re-assigning to the same person fires the event again. Deduplicate on `id` if you are posting notifications.

### Related events

- `support.conversation.resolved`: the usual next step once the assignee has answered.
- `support.message.received`: what typically prompts an assignment.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'support.conversation.assigned', required: The event name, always `support.conversation.assigned` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `conversation_id` string, uuid, required: The conversation whose assignee changed.
    - `project_id` string, uuid, required: Mirrors the envelope `project_id`.
    - `subscriber_id` string, uuid, required: The member the conversation belongs to.
    - `assigned_to_user_id` string, uuid, nullable, required: The team member now responsible. **`null` means the assignment was cleared.**

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)