Download requests are easy to count and hard to talk to. A list of 200 people who wanted your checklist can sit for months while you guess which of them want help.
What moves them is a follow-up that's easy to reply to, then a response matched to where each person is: finished with the resource, stuck partway, or a step away from needing it.
By the end you'll have a day-4 question email, example responses for all 3 paths, a call invitation that reads as an offer of help, and a tracker showing which sources produce calls. The example continues with Leah Morgan, an illustrative coach for new engineering managers, and her First 1:1s Planner.
Jump to the free Download-to-Call Follow-Up Planner
Identify the task the subscriber is trying to complete
Each download implies a task: someone who requested a 1:1 planner is trying to run better 1:1s. Write that task in 1 line, then sort every reply by how far along it the person got: used the resource, stuck partway, or not yet in the situation it's for.
Leah's task line
"The subscriber is trying to plan and hold a useful first 1:1 with each direct report." The 3 paths follow from it.
Read the signals in order of reliability
| Signal | What it tells you | Reliability |
|---|---|---|
| Reply in their own words | Where they are and what's in the way | High |
| Optional form answer | Their situation, such as Leah's team size question | Medium |
| Click on the resource link | Someone followed the link at least once | Medium |
| Booking page visit, no booking | Interest, with timing or doubts | Low |
| Email open | Very little | Low |
Opens rank last because open tracking counts the loading of a hidden image (SendGrid's explanation), and Apple Mail's Protect Mail Activity setting, when it's on, downloads remote content privately as a message arrives (Apple's Mail privacy page). An open can register for an unread email, so plan the follow-up around replies.
Keep signals out of the email itself, since "I saw you clicked twice" makes people feel watched.
Respect the consent line
Only people who ticked the follow-up box get the question email. When someone without that consent replies to the delivery email, answer their question and leave them out of the series unless they ask to join.
Keep the tracker as private as your CRM: contact IDs or initials, consent in its own column and no reply text pasted into shared sheets.
Ask a useful follow-up question and recognize readiness
Send 1 question on day 4 that takes a line to answer and shows which path the person is on. Read each reply for readiness: a named person or situation, a date, a question about how you work. Answer every reply with help first, and offer a call only when the reply points there.
The day-4 email sits between emails 2 and 3 of the welcome email sequence for coaches and consultants, under the same rules: ticked-box contacts only, stopping on a reply or a booking.
The day-4 question email
Subject: Quick question about your 1:1s
Hi {{contact.first_name}},
Just 1 question, and a one-line answer is plenty: which of your 1:1s are you finding hardest right now, and why?
I answer every reply myself, usually within 2 working days.
Leah
It asks about the reader's situation, so it works whether or not they've opened the planner. Each reply turns a subscriber into someone you're in conversation with, the first move from audience toward the community described in the Community Engine guide.
Path A: used the resource
Sofia (illustrative) replies: "Did 3 of my 5 so far. Biggest surprise: 2 of them want to move to the platform team, and I don't know whether to fight it or help them go."
Thanks, Sofia. Hearing this now beats hearing it in a resignation. Before you decide, ask each of them what the platform team has that yours lacks. If it's the work, you may be able to bring some of it to them. Happy to talk it through on a 20-minute call if that would help: [Book a time].
Named people and a pending decision make a call fit.
Path B: stuck
Dana (illustrative) replies: "Haven't started. My problem is Jordan, who applied for my job and has been short with me in standups. No idea how to open that 1:1."
That's one of the hardest 1:1s a new manager faces, so it makes sense it's the one holding you up. One way in is to name it early and briefly: "I know you went for this role too, and I'd like this to work for both of us. What would make that true for you?" Then listen more than you talk. If you'd like to plan it together first, here's a 20-minute call: [Book a time].
A stuck reply about a specific, high-stakes person is often the strongest call candidate, and helping first makes the call Dana's choice.
Path C: not ready
Chris (illustrative) replies: "I'm not a manager yet. Team lead interview next month, downloaded to get ahead."
Good luck with the interview. Page 3's questions double as interview prep, since asking how a team likes to get feedback is fair for any panel. I'll keep you on the monthly newsletter, and if you get the role, reply here and we'll plan your first round of 1:1s.
Skip the call here, since it would be about a problem Chris doesn't have yet. Tag the contact future-manager instead.
Readiness signals
| In the reply | Likely meaning | Response |
|---|---|---|
| A named person and situation | A live problem | Help, then a call offer |
| A date or deadline | Urgency | Call offer early |
| "How do you work?" or a price question | Buying research | Plain answer and the call link |
| Mentions a training budget or their manager | Possibly employer-funded | Call, plus a 1-page summary they can forward |
| Thanks, with no question | Satisfied for now | Thank them, no pitch |
| Not in the role yet | Future fit | Tag and newsletter |
Convert lead magnet subscribers into clients: offer a call and record the outcome
Offer a call when a reply shows a live problem your paid work handles, and describe it plainly: length, what you'll cover and what can happen after. Then log every request, reply, call and outcome against its source, so after 30 days you can see which content brings people who want help.
The call invitation
If you haven't offered a call yet:
Would a 20-minute call help? We'd look at [their situation, in their words] and plan the next 2 weeks. If my 12-week program turns out to fit, I'll explain how it works, and either way you'll leave with a plan. [Book a time]
On the booking form, ask 4 short questions: role and team size, the main goal for the next 90 days, the biggest thing in the way, and whether support would be self-funded or employer-funded. In HighLevel, a calendar's custom form appears after the visitor picks a slot, and its answers save to the contact only when the booking completes and each field is mapped to a custom field (calendar forms).
The source-to-call tracker
Give each person 1 row. HighLevel's Source field is separate from its attribution data (Source field), so test which one your embed records. Write Unknown when you can't trace someone; a guessed source makes the table tidier and less useful.
Keep Call and Outcome to fixed lists so the month adds up. Call is none, offered, held or no-show; Outcome is client, proposal sent, later, not a fit or no next step, with a short note in parentheses.
7 illustrative rows from Leah's month:
| Contact | Source | Requested | Consent | Path | Replied | Call | Outcome |
|---|---|---|---|---|---|---|---|
| S.K. | LinkedIn post | Oct 2 | Yes | A | Oct 6 | Held | Proposal sent (to her employer) |
| D.M. | Newsletter | Oct 3 | Yes | B | Oct 7 | Held | Client (12-week program) |
| C.R. | Article | Oct 4 | Yes | C | Oct 8 | None | Later (tagged future-manager) |
| A.P. | Article | Oct 6 | No | None | No | None | No next step (delivery only) |
| M.B. | LinkedIn Featured | Oct 9 | Yes | B | Oct 13 | Offered | Later (asked for November) |
| C.W. | Newsletter | Oct 11 | Yes | A | Oct 15 | No-show | Later (1 rebooking offer sent) |
| U.N. | Unknown | Oct 14 | Yes | A | Oct 18 | None | No next step (no live problem) |
Illustrative 30-day totals by source:
| Source | Requests | Ticked box | Replies | Calls held | Clients |
|---|---|---|---|---|---|
| LinkedIn posts | 21 | 16 | 6 | 2 | 0 |
| Newsletter | 9 | 9 | 4 | 2 | 1 |
| Articles | 14 | 7 | 1 | 0 | 0 |
| LinkedIn Featured | 3 | 2 | 1 | 0 | 0 |
| Unknown | 1 | 1 | 1 | 0 | 0 |
| Total | 48 | 35 | 13 | 4 | 1 |
Reading the month
- The newsletter matched LinkedIn posts on held calls from under half the requests, which fits people who already read Leah every month.
- LinkedIn posts bring the most requests and steady replies, mostly from path A.
- Articles bring requests with little follow-through: 14 requests and 1 reply, from someone not yet managing. Leah treats that as an audience question, the kind worked through in the guide on content that gets views but few inquiries.
At 48 requests and 1 client, the sample's too small to rank sources with confidence. Treat month 1 as proof the pipes work, and compare sources again at 90 days.
The Download-to-Call Follow-Up Planner has the day-4 email, all 3 paths and this tracker, totals included.
Your next step is the day-4 question. Add it to your sequence this week, answer every reply within 2 working days and log each one in the tracker. At 30 days, check that every step works; at 90 days, move content toward the sources that produce calls.