You need feedback from your customers. Real, specific feedback - not the polished version they give on a support call. So you send an email asking for a 15-minute interview, and you get silence.
The problem isn't that customers don't want to help. It's that your request looks like every other request they get - vague, low-friction-to-ignore, and asking for something without giving them a reason to prioritize it.
Customer interview requests are actually one of the easiest cold email campaigns to get responses from, because you're asking for something people generally want to do. They want to be heard. They want to help shape your product. You're just asking wrong.
The Structure That Gets Responses
A working customer interview request does three specific things:
- It references something specific about them or their use case
- It frames why their feedback matters (not "help us", but what you'll actually do with it)
- It removes friction by being explicit about what the interview involves
Here's the template that gets consistent replies:
Subject: Quick question about [specific feature/use case they use] Hi [Name], I noticed you've been using [specific thing] for [timeframe]. I'm looking to understand how [specific outcome they care about] is working for teams like yours. Would you be open to a quick 15-min call next week? I'm specifically trying to learn [one clear thing], so this would actually be useful for you if you care about [outcome]. Tuesday or Wednesday work better for me - either day at 2pm or 3pm EST? [Your name]
Let's break down why this works:
"I noticed you've been using [specific thing]" - This shows you've actually looked at their account. Not "we want feedback from a few customers." You picked them deliberately. This alone gets your open rate above 35% because it's clearly not a template.
"I'm specifically trying to learn [one clear thing]" - People want to know what you're asking before they commit. When they see you want feedback on "user onboarding" instead of just "how's the product", they can mentally prepare. It takes 2 seconds to read, so friction drops.
"So this would actually be useful for you if you care about [outcome]" - This is the key line. You're not asking them to help you. You're saying "here's what I'm learning about, and I suspect this matters to you too." If they're using that specific feature, they probably care about the outcome. You just connected the dots for them.
Specific times instead of "let me know what works" - You offer two days, two times each. That's four total options. This removes the friction of "I have to think about when I'm free." It also dramatically increases acceptance because you've already done the scheduling work. Yes, you'll need to follow up if they suggest something else, but most will pick from what you offered.
What to Reference: Getting Specific Without Creeping Them Out
The difference between "personalized" and "creepy" is specificity grounded in their actual behavior, not their personal life.
Good references:
- "I see you created 12 custom reports last month" - behavior in your product
- "You've been on the platform for 8 months" - tenure data
- "Your team uses the API integration with [tool]" - specific feature usage
Bad references:
- "I saw you went to [conference]" - feels like stalking
- "Congrats on your promotion" - if you got it from LinkedIn, it's weird in an email
- Anything from their personal Twitter/Instagram
Pull data from your own product analytics. If you're a SaaS tool, you have this. If you're a service business, reference their contract date, the service they bought, or outcomes you've tracked. That's always fair game and never feels invasive.
Subject Line Specifics
Customer interview requests have the best subject line performance when you lead with curiosity, not a request.
Quick question about your dashboard setup
This beats "Can I interview you?" or "Customer feedback request" by about 40% in open rate because it doesn't signal "this is sales." It signals "I'm confused about something you do" or "I'm genuinely curious." Both get opens.
Avoid subject lines that make it look like you're asking for time before they even open the email. "Need 15 minutes" in a subject line? People skip it. They need to read your reasoning first.
Follow-Up Matters More Than You Think
About 30% of people who will say yes to an interview request won't reply to the first email. Not because they're not interested - they just didn't see it, or they meant to reply and forgot.
Send a follow-up 5 days later. Keep it short:
Hey [Name], Just circling back on the interview request about your dashboard setup. Still think this would be valuable to learn from you. Let me know if either of those times work.
That's it. Don't apologize. Don't explain why you're following up. Just remind them it exists and that you meant it.
How to Actually Use What You Learn
The follow-up work matters too. When they do agree to an interview, send a calendar invite within 2 hours. Don't make them confirm again. You offered specific times - just pick one and send the invite. This is how you avoid the 20% no-show rate on interviews.
During the call, take notes. After the call, send them a one-liner about what you learned that's relevant to them: "Really helpful to hear that onboarding is a bottleneck for your team. I'm definitely looking at how we can improve that process." This takes 30 seconds and makes them feel heard, which matters when you want to do follow-up interviews later.
For scale, this approach works if you're running it yourself or if you're sending a few dozen per week. If you need to be interviewing 20+ customers per month at a consistent pace while also managing your business, the infrastructure and templating gets complex fast - you need to track who you've already interviewed, map out follow-ups in advance, and make sure no one falls through the cracks. That's where the logistics start eating time.