Customer interview email templates: 3 invitations + follow-up

Decide what you need to learn before writing the subject line

Write one decision the conversation could change. For an agency approval tool, that might be whether delays come from finding the right reviewer or collecting all the files. A person who recently managed a review can describe that event; someone who merely likes startup tools may not.

Choose the participant by their responsibility and recent experience. You may need to speak with a user, a manager and a buyer separately. Do not assume a job title proves that a person does the work or can authorize a purchase. If their fit is unclear, ask a short qualifying question before proposing a call.

The examples below are original drafting aids, not messages from a customer campaign. Replace every bracket with a fact you can support. The suggested 15-minute conversation and one follow-up are small-scope choices, not proven response-rate formulas.

• Template 1: warm introduction
• Template 2: tailored invitation
• Template 3: early-user invitation
• Already have a participant? Open the interview script and notes

• Name the role, workflow and recent event you want to understand.
• Record why this person might fit and what remains unconfirmed.
• Explain who you are and your connection to the product or research.
• Choose a small, concrete ask and a truthful description of the session.
• Decide whether you can offer an incentive; state its terms without tying it to favorable feedback.

Template 1: ask a contact for a permissioned introduction

Subject: Do you know someone who handles [workflow]?

Hi [contact], I am building [brief product description] and trying to understand how [role] handles [specific event]. I remember you mentioned working with [relevant team or community].

Would you be comfortable asking whether someone who recently handled [event] would speak with me for 15 minutes? I want to learn about their current process. I will not ask you to share their details without checking with them first.

Here is a short note you can forward: [Your name] is researching [workflow] and would value a 15-minute conversation with someone who recently [event]. They are looking to understand the steps and current tools, rather than run a product demo. Would you like an introduction?

If nobody comes to mind, no problem. Thanks, [your name].

Template 2: invite someone whose work gives you a specific reason to ask

Subject: A question about [specific workflow]

Hi [name], I read your [public article or post] about [specific event]. You mentioned [accurate, relevant detail].

I am [name], the founder of [product], which helps [role] with [job]. I am researching how people currently handle [narrow part of the workflow], including when their existing tools work well.

Would you be open to a 15-minute conversation about the last time you [event]? I would ask about the steps and tools you used; this would not be a sales presentation. There is no need to share confidential files.

If you are interested, I can send a couple of times. If this is outside your work or you would rather not hear from me, just say so and I will leave it there. Thanks, [your name].

Template 3: ask an early user about one actual attempt

Subject: Could we discuss your experience with [task]?

Hi [name], thanks for trying [product]. [Accurate context from your conversation or product records] made me wonder how the experience went for you.

Would you have 15 minutes to walk me through what you were trying to do, where you got stuck and what you used next? An unfinished attempt would be useful to understand too. I am looking for an honest account, and your access to [product] does not depend on taking part.

[If applicable: We offer [incentive and clear terms] for your time, regardless of what you tell us.] If you are interested, reply and I will send a couple of times. No problem if you prefer to pass. Thanks, [your name].

Worked example: every personalized line needs a reason

ReviewQueue, its founder Maya and the participant Alex are fictional. In this example, Alex wrote a public account of a delayed client review. There has been no real email, interview or Soloop task. The table shows how to turn limited context into an invitation without making the missing facts sound certain.

Follow up once, then interpret the reply carefully

If the invitation is still relevant and the person has not declined, one brief follow-up after several business days is a reasonable starting rule. Choose the timing to suit the relationship. Avoid repeated reminders, invented urgency or moving to another channel to get around a refusal.

A follow-up to adapt: Hi [name], one follow-up on my invitation about [workflow]. I am trying to understand [specific question], including where the current process works well. If a short call is inconvenient, a brief reply about the last time this happened would also help. If you prefer to pass, I will close this out. Thanks, [name].

After that, stop unless the person invites further contact. Silence leaves the reason unknown: the timing, channel, request or audience may be wrong. It does not prove that the problem is unimportant.

Copy this invitation worksheet before you send

Keep one record per proposed participant. You can copy this table into your own notes and use it without Soloop. Store only the contact context you need, with access appropriate to the people doing the research.

Prepare the invitation in Soloop, then conduct the conversation yourself

Bring your product context, the learning question and evidence you may share. A starting request: Draft one customer interview invitation for [role] about [event], using only [checked context]. State who I am, ask for [duration], and flag missing facts instead of inventing personalization. Return a draft for review; do not send it.

Soloop's public manual describes outreach preparation, sending and replies through connected Gmail. A draft is not a sent message. Before any send, check the recipient, final wording, account permissions and approval mode shown in your workspace. Scheduling and automatic-send behavior depend on the task setup; this guide does not require either.

You arrange and conduct the interview, keep permissioned notes and decide what to do with the answers. Soloop is not presented here as a participant panel or an automatic interview service. The public entry link does not transfer this worksheet, so copy the brief yourself. Use the discovery questions and notes editor below when the conversation is booked.

Sources and example boundaries

Sources checked October 4, 2026. The templates, fictional example and worksheet are original editorial materials, not tested campaign results. Recheck the product manual when using account actions; no response-rate or revenue outcome is promised.