Chasing clients for tool access is one of the most reliable ways to lose their trust in week one. Here's how to stop doing it.
Every agency has been here: you finish the kickoff call, send the access request email, and then wait.
Three days pass. You send a follow-up. Another two days pass. You send another. The client apologizes, says they'll handle it "today," and then you start week two of a supposedly three-week project with access to one out of six required tools.
This isn't a client problem. It's a system problem. The way most agencies request access is optimized for writing, not for getting a response.
Here's what to change.
Why the Standard Access Email Fails
Most access request emails look like this:
"Hi [Client], as we kick off the project, we'll need access to the following tools: Google Analytics, Search Console, your CMS login, the brand asset folder, and your ad accounts. Please share these at your earliest convenience. Let us know if you have any questions."
That email has three structural problems:
1. No numbered list. A paragraph of tool names reads as one thing to process. A numbered list of items reads as a checklist — each item can be completed and mentally ticked off. The brain processes them differently.
2. No deadline. "At your earliest convenience" has no urgency. It gets filed under "later." A specific date — even a soft one — creates an anchor point. Clients don't miss calendar-linked deadlines the same way they miss open-ended requests.
3. No per-item action. Saying "share access to Google Analytics" requires the client to interpret what "share access" means, navigate to the right settings, remember their login, and figure out the right permission level — all while running their actual business. The email that gets replies explains exactly what to do for each tool.
The Three-Part System
Part 1: The Access Request Email Template
The template that gets replies has four components:
Opening (1 sentence): Warm, specific, and not "per our discussion." Reference something from the kickoff call.
Numbered access list: One item per line. For each item: the tool name, the exact action required, and the email address to share it to. Example:
1. Google Analytics 4 — Go to Admin → Account Access Management → Add User.
Share with [email]. Access level: Analyst.
2. Google Search Console — Go to Settings → Users & Permissions → Add User.
Share with [email]. Access level: Full.
3. CMS (WordPress/Webflow/etc.) — Add a new user account for [email].
Role: Editor.
Deadline: "We'll need these by [specific date] to keep the project timeline on track." Three business days from send is the right target — short enough to feel real, long enough to be reasonable.
Reply anchor: "If any of these aren't available right now or you need help locating them, just reply to this email and I'll help you through it." This removes the friction of the client not knowing how to do something without feeling like they need to figure it out alone.
Part 2: The Follow-Up Sequence
One follow-up isn't a system. A follow-up sequence is.
Day 3 (deadline day): Short, specific. List which items you still need. Don't re-explain why. "Quick check — we still need access to items 2 and 4 above to stay on schedule. Let me know if you hit any issues."
Day 5 (two days after deadline): Same short format, but now name the impact. "We're at [project day], and we haven't been able to start [specific deliverable] yet because we're waiting on [tool]. This will affect [specific milestone] if we don't get it today."
Day 7 (escalation decision point): This is where you need a protocol. Either (a) put the specific deliverable on hold formally ("this is a scope hold, not a delay on our end"), or (b) escalate to a different contact if available. Both options require documentation.
Most agencies improvise this sequence. The result is inconsistent response times and no paper trail if scope disputes come later.
Part 3: The Access Tracker
A project board isn't enough. Access collection needs its own tracker — a simple table with:
| Tool | Required | Received | Date Received | Notes |
|---|---|---|---|---|
| GA4 | ✓ | ✓ | 2026-05-03 | Analyst access |
| GSC | ✓ | ✗ | — | Chased 2× |
| CMS | ✓ | ✓ | 2026-05-04 | Editor role |
This does two things: it makes incomplete access visible at a glance (stopping the "I thought we had that" problem), and it creates a timestamped record of when you asked and when you received, which matters if a timeline dispute comes up.
The Variant Problem
Access needs vary by project type, and a generic access email creates a generic problem: either it's too long (lists tools that don't apply) or too short (forgets a tool specific to this engagement type).
The fix is one template per project type, with a master list of all possible tools and a simple "applies / doesn't apply" filter before each send.
For a marketing agency client, the list typically includes: ad accounts, analytics, tag manager, landing page builder, CRM, and social channels.
For an SEO client: analytics, search console, CMS, site audit tool access if applicable.
For a web design client: brand asset folder, current CMS or site access, domain registrar access, hosting access, and any existing design files.
Running the wrong template for the project type is how important access items get missed until mid-project.
The Bigger Picture
Access collection isn't really about access. It's about whether the client trusts that you're organized.
An agency that sends a vague access email and chases twice signals: we don't do this often enough to have a system. An agency that sends a numbered, deadline-specific access email and follows up precisely on schedule signals: we've done this many times, we know what we need, and we respect your time by being specific.
That first impression doesn't show up in the analytics. It shows up in the reference call six months later.
Free Resources
We built the access collection system above into the Agency Onboarding OS — including the email templates, follow-up sequence, access tracker, and project-type variants.
The free resources are a starting point:
The full system — templates, SOPs, automation recipes, and LLM prompts — is at agencyonboardingos.com.
If your access collection system looks different and it works, I'd actually like to know. What changed the reply rate for you? Email or reply here.
Top comments (0)