send_review_request
Send a review request email NOW for a specific closed escrow.
Send a review request email NOW for a specific closed escrow. REQUIRES EXPLICIT USER CONFIRMATION IN CHAT BEFORE EXECUTION. The assistant MUST first call draft_review_request_email to show the user the proposed subject + body, and MUST receive an unambiguous "yes, send it" (or equivalent confirmation) from the user before invoking this tool. This is a write tool that sends a real email. The service enforces the email suppression list, blocks repeat sends to the same client for the same escrow within 60 days, and applies the per-user limit of 50 sends per day — the same safeguards enforced by the REST endpoint. Returns { message_id, sent_at, status } on success or a structured skipped_* / error outcome that explains why the send did not happen.
Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
escrow_id | string | Yes | Identifier of the closed escrow. A text identifier (e.g. "ESC-2026-0042"), not a UUID. · Max length: 100 · Min length: 1 |
template_variant | enum | No | Tone variant to send. Defaults to the user's saved review-request tone preference (typically "warm"). Pick explicitly when the user asked for a specific tone in their confirmation. · One of: warm, professional, casual |
custom_body | string | No | Optional custom body override. The current template does NOT include this text in the sent email — it is recorded on the audit trail only. Pass it when the user dictates exact words, but be aware the recipient still receives the standard template body for now. · Max length: 5000 |
Example prompts#
- "Yes, send that review request to the Garcias now, the warm version."
- "Go ahead and send the review email for ESC-2026-0107 with the casual tone."
Safety#
Creates data + external action. Creates a record and triggers an action in a connected external service.