--- name: follow-up-drafting description: Composes chase emails for missing documents, approaching deadlines and unanswered communications, with tone calibrated to urgency and recipient. Shows the draft inline, asks for confirmation, calls the matching send_* tool for a preview, then calls confirm_email_send on the user's explicit yes; if the email was parked for review it reports that it is waiting for approval, not sent. Use when the TC asks to follow up, chase a document, nudge an agent or lender, or remind a party about a deadline. license: MIT --- # Follow-Up Drafting ## When this fires The TC says any of: - "Follow up with [party] about [topic]" - "Chase [recipient] on [missing doc / deadline]" - "Nudge the [agent / lender / inspector]" - "Remind [recipient]" - "Send a check-in to [buyer / seller]" - "Draft a weekly update to [buyer / seller]" - "Reply to [thread]" Also fires from `email-triage` when the TC approves drafting a chase. ## The recipe ### Step 1 — Pull context 1. **`get_transaction`** — full state of the deal (status, parties, financials) 2. **`get_key_dates`** — deadline proximity for tone calibration in step 3 3. **`get_missing_documents`** — if this is about a missing doc 4. **`get_open_tasks`** — what else is in flight 5. **`get_contacts`** or **`find_contact_by_email`** — resolve the recipient ### Step 2 — Pick the right tool | User intent | Tool | |---|---| | Weekly update to buyer or seller | `send_client_update` | | Specific missing-doc chase | `send_document_request` | | Agent-to-agent on a topic | `send_agent_followup` | | Generic email with talking points | `send_email_to_agent` | (Detailed mapping in the `execution-workflow` skill.) ### Step 3 — Calibrate tone #### By urgency (days from deadline) | Days out | Tone | Example opening | |---|---|---| | 7+ | Friendly check-in | "Just wanted to touch base on..." | | 3-7 | Polite, specific | "We have [item] due by [date], could you please..." | | 1-2 | Firm, action required | "This is due tomorrow — please send..." | | Overdue | Direct, professional | "This was due on [date]. Please provide at your earliest convenience to avoid delays." | #### By recipient role | Recipient | Tone | |---|---| | Buyer / Seller | Warm, reassuring, simple. No jargon. | | Listing Agent / Buyer Agent | Professional peer. Assume process knowledge. | | Lender | Formal. Reference loan number when known. | | Title Company | Direct. Reference file number when known. | | Inspector / Appraiser | Brief, scheduling-focused. | ### Step 4 — Compose You (the model) compose the subject + body using the context. Include: - **Property address in subject line** (always) - **The relevant deadline in the body** when applicable - **Specific ask** (not "let me know" — "send the survey by Friday") - **Brief** — TCs value brevity; aim for < 150 words ### Step 5 — Confirm in chat Per `execution-workflow`, show the complete draft inline before you call anything: ``` Drafted for Mike Park (buyer agent): Subject: Survey needed for 412 Oak St — closing 5/22 Hi Mike, Quick reminder — we need the property survey for 412 Oak St in hand by Wednesday 5/20 to keep our closing on track. Can you send it over today? Thanks, Casey Want me to send it? ``` Wait for the user's "yes" before calling the tool. ### Step 6 — Call the right `send_*` tool (this previews; it does not send) Pass `transactionId`, `recipientContactId` (or `recipientRole`), `subject`, `bodyHtml`, `bodyPlainText`. The recipient must already be a contact on the deal. The result is one of: ```json { "status": "awaiting_confirmation", "confirmCode": "djc_...", "expiresAt": "2026-11-06T18:00:00Z", "recipient": "Mike Park (mike@parkrealty.com)", "preview": { "to": [...], "subject": "Survey needed for 412 Oak St — closing 5/22", "bodyHtml": "...", "bodyText": "...", "attachments": [] } } ``` or `"status": "parked_for_review"` (the email is NOT sent; it waits in the DocJacket review queue for a team member, `reviewReason` says why, and there is no code). Send once. If a call timed out, retry with the same `X-DocJacket-Client-Request-Id` (see `execution-workflow`). ### Step 7 — Show the preview, then confirm For `awaiting_confirmation`, show the user the COMPLETE email from `preview` (recipients, subject, full body, attachments) and ask. Only on an explicit yes, call `confirm_email_send({ confirmCode })`; on no, `confirm_email_send({ confirmCode, decision: "discard" })`. If it returns `CONFIRM_CODE_EXPIRED`, `CONTENT_CHANGED` or `SUPERSEDED`, call the send tool again and show the new preview. For `REVIEW_REQUIRED`, `NOT_ALLOWED_TO_CONFIRM`, `RECIPIENT_NOT_ALLOWED` or `NO_LONGER_PENDING`, tell the user it is waiting in the review queue. Full table in `execution-workflow`. ### Step 8 — Report to the user Only when `confirm_email_send` returned `queued`: ``` Approved and on its way to Mike Park (mike@parkrealty.com) Subject: "Survey needed for 412 Oak St — closing 5/22" ``` For `parked_for_review`: "It is waiting for approval in DocJacket, not sent yet." For `discarded`: say nothing was sent. ## Email rules (in the composed body) - Always include property address in subject line - Include the relevant deadline date when applicable - Keep emails under 150 words - One ask per email (combine related items on the same party into one email) - Never threaten or use adversarial language ## Examples **Missing-doc chase to listing agent, 2 days from deadline:** ``` Subject: Survey needed for 412 Oak St — closing 5/22 Hi Mike, Quick reminder — we need the property survey for 412 Oak St in hand by Wednesday 5/20 to keep our closing on track. Can you send it over today? Thanks, Casey ``` **Weekly update to buyer:** ``` Subject: Weekly update — 412 Oak St Hi Jane, Quick update on 412 Oak St. The inspection cleared Tuesday with only minor items the seller agreed to address. We're tracking to close on 6/15, and I'll have the CD timeline locked by Friday. Let me know if anything comes up. Casey ``` ## Don't do - **Don't call `send_*` without an explicit user yes.** Per `execution-workflow`. - **Don't say the email is on its way** unless `confirm_email_send` returned `queued`. `parked_for_review` means it is waiting for approval. - **Don't call `confirm_email_send` without the user's explicit yes to the complete preview.** - **Don't impersonate the TC's personal voice perfectly on day 1.** Use a professional default; the TC can ask you to adjust before sending. - **Don't fabricate facts.** Only state things the tools confirmed. - **Don't pile on.** If multiple items need follow-up with the same party, bundle them into one email. - **Don't say "Pending Review" or link `/prepared-work`.** That UI is retired. Say the email is waiting for approval.