re_engagement_email
Draft warm re-engagement emails to past clients with three route options—check-in, new service, or availability—requiring only client name and last project detail to refresh the relationship.
Instructions
Write the email you send to a past client you haven't worked with in a while — to reopen the relationship, explore new work, or simply stay on their radar. Distinct from cold_pitch (these people already know and trust you — the tone is warm, not selling), referral_request (you're not asking for a name, you're reopening your own relationship), and testimonial_request (you're not asking for a review). Three routes: check_in (low-pressure — catch up, mention what you've been up to, no explicit ask; best for high-value relationships you don't want to pressure), new_service (flag a specific new offering that's relevant to what you did together; works when you have something concrete to offer), availability (you're available and thought of them first; works when you ended on a strong note and timing is the only variable). Required: client_name, last_project (a brief description of what you worked on together — keeps the email from feeling generic). Optional: time_since (how long it's been — e.g. '6 months', 'last year', 'a while'; omit and the copy stays vague), what_you_did (a specific outcome or result from the last project — adds credibility), new_service_name (for new_service route — the specific offering to highlight), new_service_relevance (for new_service route — why it's relevant to this client), route ('check_in' | 'new_service' | 'availability' — default check_in), your_name. Does not count against your monthly draft limit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | First name of the past client | |
| last_project | Yes | Brief description of what you worked on together — e.g. 'the brand refresh', 'your Q3 campaign', 'the e-commerce migration'. Keeps the email specific and personal. | |
| time_since | No | Optional: how long it's been since you last worked together — e.g. '6 months', 'about a year', 'a while'. Omit to keep it vague. | |
| what_you_did | No | Optional: a specific outcome or result from the last project — e.g. 'the site we built is still converting well', 'the campaign hit 140% of target'. Adds credibility without bragging. | |
| new_service_name | No | For new_service route only: the specific new offering you want to flag — e.g. 'a new SEO audit package', 'a monthly retainer model', 'video content production'. | |
| new_service_relevance | No | For new_service route only: why this new service is relevant to this particular client — e.g. 'given the growth you were seeing with organic', 'now that you've launched the new product line'. | |
| route | No | check_in (default): warm catch-up, no explicit ask — best for high-value relationships. new_service: flag a specific new offering that's relevant to what you did together. availability: you're available and they're your first call — works when you ended on a strong note and timing is the variable. | |
| your_name | No | Optional: your name for the sign-off |