Customer discovery: a question-led email sequence

This sequence invites a conversation about a real workflow. It does not hide a product pitch inside a request for help.

The founder and research topic are fictional. Use it with a contact group whose expectations fit the invitation, such as people who agreed to be contacted about interviews. Do not infer that agreement from a publicly listed email address.

State the research context before sending

The example asks how a small service team hands a new client from sales to delivery. It uses one merge field, firstName, with a readable fallback.

Replace the sender identity and research purpose. Only promise a short summary if you intend to produce it and the participant wants it. If your invitation includes a demo or commercial discussion, disclose that clearly.

Message 1: ask about a recent event

Initial subject: Question about your client handover

Hi {{firstName | there}},

You agreed to be contacted about workflow interviews. I am exploring how small service teams hand a new client from sales into delivery, and I am building a product in this area.

What happened the last time your team made that handover? I am interested in the steps you actually took, including anything that needed chasing.

A short email answer is welcome. If a conversation is easier, let me know and we can agree a time.

Thanks,
Sami

If you prefer no further research invitations, reply and I will stop.

Remove or replace the agreement statement unless it is true for every recipient. It is not decorative personalization.

Message 2: make answering easier

Send only if there has been no response and another invitation is appropriate.

Hi {{firstName | there}},

To make the question easier: where did your team keep the information needed for the most recent client handover?

One example is enough. I do not need client names or private documents.

If the question does not fit your work, no need to take part.

Sami

Reply if you do not want further invitations and I will stop.

This narrows the task without telling the person which answer you want. Do not add a booking demand to a message that promises an email answer is enough.

Message 3: finish recruitment

Hi {{firstName | there}},

I will end this invitation sequence here.

If you would like to share an example later, you can reply to this conversation. Otherwise there is nothing you need to do.

Thank you,
Sami

Ending the invitation is different from concluding the research. Do not claim enough interviews or established demand because the campaign finished.

Adapt the research question without suggesting the answer

Choose the question that matches the actual research purpose. Do not send all three to manufacture a survey.

After a relevant answer, a personal response could be:

Hi Alex,

Thank you. You mentioned that someone had to chase missing handover details.

What information was missing in that particular case, and what did your team do next? Please leave out client names or private documents.

Sami

Use that response only if the participant actually mentioned the missing details. It follows their evidence rather than inserting your preferred problem. A follow-up after silence has a different purpose from this continuation after an answer.

Adapt the conversation after a reply

A useful reply should get a specific human response. Do not send the second invitation after someone already supplied their example.

ColdMerge’s detected human replies stop the current campaign’s remaining follow-ups. Automatic replies do not. Record a request to stop as an opt-out rather than treating it only as an answered invitation. See Follow-up sequences and How unsubscribes work.

Follow-ups remain in the original thread and have no separate subject. Preview the fallback and all factual statements before launch.

Keep recruitment, findings and product decisions separate. Use the campaign-writing guide to write and save the campaign draft.

Check opt-out controls before launch

ColdMerge’s unsubscribe footer and one-click header start off. Review and enable the appropriate controls before sending. A reply asking to stop does not automatically suppress the address across campaigns: choose Mark as opted out manually. That suppression applies across the Organization. See How unsubscribes work for the configuration and recipient behavior.