client_access_request_email
Draft professional emails to request client system access, with routes for initial request, follow-up, or partial workaround. Clearly state what access is needed and why.
Instructions
Write the email requesting access to client systems, tools, platforms, or repositories needed to start or continue work. For when you need logins, permissions, API keys, or repository invitations from the client side. Three routes: initial_request (default — first-time ask for specific access required to kick off or progress the project; tone is clear and practical, lists exactly what's needed and why), follow_up (chasing outstanding access that was promised or discussed but hasn't arrived yet — tone is patient but firm, reiterates the blocker clearly), partial_workaround (you've found a temporary workaround but still need full access eventually — explains what you've done, what you still need, and the impact of the delay). Distinct from client_material_chase_email (chasing files or content, not system access) and project_restart_email (restarting stalled work after a break). Does not count against your monthly draft limit. Required: client_name, access_needed (what you need — e.g. 'admin access to the WordPress dashboard', 'an invitation to the GitHub repo', 'read access to Google Analytics'). Optional: project_name, access_reason (why you need it — e.g. 'to set up the staging environment', 'to start the content migration'), workaround_description (for partial_workaround route — what you've done in the interim), deadline (when you need access by — e.g. 'by end of week', 'before Thursday's call'), route ('initial_request' | 'follow_up' | 'partial_workaround' — default initial_request), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client first name | |
| access_needed | Yes | What you need access to — e.g. 'admin access to the WordPress dashboard', 'an invitation to the GitHub repo', 'read access to Google Analytics', 'the Figma project files', 'your hosting control panel'. Required. | |
| project_name | No | Optional: name of the project — e.g. 'the Westbrook website', 'your brand identity', 'the app build'. | |
| access_reason | No | Optional: why you need this access — e.g. 'to set up the staging environment', 'to start the content migration', 'to connect the analytics integration'. Makes the request feel purposeful, not administrative. | |
| workaround_description | No | For partial_workaround route: what you've done in the interim — e.g. 'I've been working from the exported files you shared', 'I've set up a temporary admin account to keep things moving'. Explains what's been done so far. | |
| deadline | No | Optional: when you need access by — e.g. 'by end of week', 'before Thursday's call', 'in the next day or two'. Adds urgency without being pushy. | |
| route | No | initial_request (default) — first-time ask, clear and practical; follow_up — chasing outstanding access, patient but firm; partial_workaround — you've found a temp fix but still need full access. | |
| your_name | No | Optional: your name for the sign-off |