Send to Support
Send a doc-site reader's assistant conversation to the project's support team, as the reader confirmed it.
The second Send to support step: sends a reader's conversation to your support team with the summary and email they confirmed. It goes to the project's support email, the support.handoff webhook, or both. Call Draft a Support Handoff first to fill the form. See Send to support.
Public (no API key required) and scoped to the project and the visitorId: a reader can only send their own conversation.
On your doc site this endpoint is also served same-origin at POST /_chat/handoff. The project comes from the site's hostname, so the path takes no projectId.
Path Parameters
projectIdRequest Body
visitorIdsessionIdemailsummaryincludeMemoryfalseWhat is sent
Every handoff is recorded first, then delivered to each destination that is set up:
support.email belongs to a verified member of your organization. The subject is [<project name>] Docs assistant handoff <ticket>: <conversation title>, and Reply-To is the reader's email, so replying reaches them. It contains the ticket, the reader's email, their summary, what the assistant remembers about them (only with includeMemory), and the transcript.support.webhook is true, a support.handoff event to every endpoint subscribed to it. Its payload carries the same content.The transcript is the conversation, oldest first, at most 100 messages. Code blocks the reader attached are left out.
A handoff is sent when at least one destination took it: the email was accepted for sending, or at least one active webhook endpoint subscribes to support.handoff (whether that endpoint then answers 2xx shows in its delivery log). With the webhook on but no endpoint subscribed, the webhook doesn't count: if there's no usable email either, Send to support isn't offered (features.handoff is false) and this route answers 409 HANDOFF_UNAVAILABLE.
Response — 201 Created
idhandoffId in the webhook payload.ticketid, without hyphens, in upper case. It's in the email subject and the webhook payload.tothe <project name> support team when only the webhook is set up.emailSending doesn't use your AI query quota.
Rate Limits
| Per | Limit |
|---|---|
| Visitor | 3 handoffs a day |
| Client IP | 10 handoffs a day — only for requests through your doc site |
| Project | 50 handoffs a day |
| Organization | 200 handoffs a day, across all its projects |
A request is only counted once the conversation is found to be the visitor's. Over a limit, the response is 429 with a Retry-After header. If the limits can't be checked, the request is refused with 429 rather than let through — see Agent mode action limits.
Error Responses
| Status | Code | When |
|---|---|---|
| 400 | validation_error | A field is missing or invalid: email not an address, summary empty or over 2000 characters |
| 403 | FORBIDDEN | The site is private (password, invite-only or SSO) and the request didn't come through the doc site ("Ask from the docs site") |
| 404 | NOT_FOUND | The project doesn't exist, or the conversation isn't this visitor's in this project |
| 409 | HANDOFF_UNAVAILABLE | The project has no usable support destination: no support email that belongs to a verified member of your organization, and the support.handoff webhook is off or no endpoint subscribes to it |
| 429 | RATE_LIMITED | A limit above was reached, or the limits could not be checked. retryAfterSeconds says when to try again |
| 502 | DELIVERY_FAILED | No destination took it: the email could not be sent and no webhook endpoint subscribes to support.handoff. The reader is asked to try again later |
| 500 | internal_error | The handoff could not be recorded |
Related
support.handoff webhook — the payload