third_party_delay_email
Write a transparent, proactive email to inform a client of a project delay caused by an external third party, such as a subcontractor or supplier outage, with mitigation steps and revised timeline.
Instructions
Write the email notifying a client of a delay caused by an external dependency outside your control — a subcontractor running late, a third-party API or platform outage, a supplier delay, or a required approval not arriving. Distinct from project_delay_warning (your own work is at risk), project_extension_email (you need more time), and late_delivery_apology (you missed a deadline): this is the specific communication for when the blocker is external. Structure: states what is delayed and why (naming the external cause clearly), what you're doing to manage or mitigate it, and a revised timeline if known. Tone: transparent and proactive, not defensive — you didn't cause this but you own communicating it. Does not count against your monthly draft limit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client's first name or full name | |
| project_name | No | Name of the project | |
| what_is_delayed | Yes | What specifically is delayed (e.g. 'the design handover', 'the API integration', 'the final build') | |
| external_cause | Yes | The external party or cause (e.g. 'the payment gateway API', 'our print supplier', 'the client-side legal sign-off', 'a subcontractor') | |
| mitigation | No | What you are doing about it (e.g. 'I've escalated with the supplier', 'I'm building a workaround in parallel', 'I'm in daily contact with the team') | |
| revised_eta | No | Revised delivery date or timeframe if known (e.g. 'Thursday 26 June', 'early next week'). Omit if genuinely unknown. | |
| your_name | No | Your name for the sign-off |