---
title: visits.draftRecap | Doing Work API
description: Draft the recap email for the customer after a visit. Pass what_we_saw in the worker's own words (or leave it out to use measurements from a saved recordin
url: https://doingwork.work/docs/reference/visits-draftrecap/
---

# visits.draftRecap

Draft the recap email for the customer after a visit. Pass what_we_saw in the worker's own words (or leave it out to use measurements from a saved recording) and the next step. Nothing is sent: show the worker the draft, edit it with visits.editRecap, and send only when they approve with visits.approveRecap. Drafting again replaces the open draft.

|  |  |
|---|---|
| Who | Agents can call this |
| REST | `POST /v1/visits/recap/draft` |
| MCP tool | `visits_draftRecap` |
| Writes | yes, send an Idempotency-Key |
| Area | [Scheduling and visits](https://doingwork.work/docs/reference/#scheduling-and-visits) |

## When to use it

Use these when a worker is heading to, standing at, or just leaving a visit. Everything happens in conversation with the worker: there are no buttons for them to tap and no app to open.

## What to tell the owner

Say what you did in plain words and what happens next.

## Input

| Field | Type | Required |
|---|---|---|
| `visit_id` | string (uuid) | yes |
| `what_we_saw` | array | no |
| `next_step` | string | no |

## Example

```http
POST https://doingwork.work/v1/visits/recap/draft
content-type: application/json
Idempotency-Key: 3f1c...

{
  "visit_id": "00000000-0000-4000-8000-000000000000"
}
```

## Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are `{code, message, status}`.

## Errors

| Code | Status | What to do |
|---|---|---|
| `invalid_input`, `invalid_token`, `rate_limited` |  | Can happen on any call. See [errors](https://doingwork.work/docs/errors/). |