> For the complete documentation index, see [llms.txt](https://docs.moderncollections.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moderncollections.io/webhooks/events/placement.disputed.md).

# placement.disputed

Fired the moment a dispute is opened on a placement. As of this event, outreach is paused server-side.

## When this fires

* Our voice agent identifies a dispute during a call (associated with `call.completed` outcome `dispute_raised`). Source is `voice_call`.
* An AI agent classifies a debtor's inbound email reply as a dispute, and a `Dispute` row is created. Source is `email_reply`.
* A debtor files a dispute through the portal (`POST /v1/portal/disputes`). Source is `portal`.

All three paths run the same dispute side-effect pipeline (pause outreach, notify the creditor, assemble the evidence packet) and fire this webhook identically. (There is no creditor-side dispute-creation endpoint.)

## Payload

```json
{
  "event": "placement.disputed",
  "timestamp": "2026-05-12T15:30:00+00:00",
  "placement_id": "550e8400-e29b-41d4-a716-446655440000",
  "dispute_reason": "Debtor claims the consulting engagement was never completed.",
  "source": "email_reply"
}
```

## Fields

| Field            | Type              | Notes                                                                                                 |
| ---------------- | ----------------- | ----------------------------------------------------------------------------------------------------- |
| `event`          | string            | Always `"placement.disputed"`.                                                                        |
| `timestamp`      | string (ISO-8601) | When the event was constructed.                                                                       |
| `placement_id`   | string (UUID)     | The placement the dispute is against.                                                                 |
| `dispute_reason` | string \| null    | Free-text reason captured at the point the dispute was raised. May be null if no reason was supplied. |
| `source`         | string            | Origin of the dispute — `"voice_call"`, `"email_reply"`, or `"portal"`.                               |

Dispute IDs, SLA deadlines, evidence URLs, compliance snapshots, and dispute-type enums are NOT included in the webhook payload today. Fetch the dispute via the REST API if you need those fields.

## What integrators do

* Pause their own dunning for this placement immediately.
* Route to whoever owns dispute response on the creditor side.
* Surface the dispute in their dashboard.

## See also

* [`call.completed`](/webhooks/events/call.completed.md) — also fires for the same event when the dispute came from a call.
* Dispute resolution does not emit a webhook today — poll [`GET /v1/placements/{id}/dispute`](/rest-api/disputes.md) to detect it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.moderncollections.io/webhooks/events/placement.disputed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.