> 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.first_contact.md).

# placement.first\_contact

Fired when the **first voice call** for a placement completes. Today this is emitted after the placement's first completed call, whatever its classified outcome (connected, voicemail, even no-answer) — the trigger is the placement's `first_contact_at` being set for the first time. Future contact channels (email reply, portal login) may add to this surface.

## When this fires

* The first call we placed for this placement ends and is processed. Subsequent calls on the same placement do not re-fire this event.

The event is dispatched immediately after [`call.completed`](/webhooks/events/call.completed.md) for the same call.

## Payload

```json
{
  "event": "placement.first_contact",
  "timestamp": "2026-05-12T14:32:00+00:00",
  "placement_id": "550e8400-e29b-41d4-a716-446655440000",
  "contact_method": "call",
  "outcome": "payment_agreed"
}
```

## Fields

| Field            | Type              | Notes                                                                                                                                                 |
| ---------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `event`          | string            | Always `"placement.first_contact"`.                                                                                                                   |
| `timestamp`      | string (ISO-8601) | When the event was constructed.                                                                                                                       |
| `placement_id`   | string (UUID)     | The placement that just had its first successful contact.                                                                                             |
| `contact_method` | string            | Currently always `"call"`.                                                                                                                            |
| `outcome`        | string \| null    | The call outcome (see [`call.completed`](/webhooks/events/call.completed.md) for the enum). May be null if the call record had no classified outcome. |

## What integrators typically do on this event

* Update internal dashboards to surface "first contact made" timestamps for SLA reporting.
* Notify the account owner on the creditor side.

## See also

* [`call.completed`](/webhooks/events/call.completed.md) — fires for the same call, with richer detail.
* [`placement.status_changed`](/webhooks/events/placement.status_changed.md)

Note: there is no webhook for placement *creation* — your own `POST /v1/placements` call is the trigger point if you need to mirror creation server-to-server.


---

# 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.first_contact.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.