KoltrixAsking customers for a research call without being annoying
A short call with a customer teaches more than a survey, but a clumsy request gets ignored. Who to ask, what to write, how to schedule it and how to say thanks.
On this page(12 sections)
Half an hour with a real customer can change what a small team builds next. People explain what they were trying to do, where they got stuck and what they actually value, in a way no dashboard or survey shows.
Getting that half hour is harder than it sounds. Customers are busy, they get a lot of email and a research request looks like every other message that wants their time. A clumsy ask is ignored, and a pushy one costs goodwill. This guide covers how to ask, whom to ask and how to make the call worth the customer's time. It focuses on the email side of the process.
Why ask for a call at all
Support email tells you what went wrong. A conversation tells you why. Calls are good for:
- Understanding goals. What are they trying to achieve, and what does success look like?
- Seeing real workflows. How do they work today, including the tools around yours?
- Finding the missing pieces. Features they need but never asked for.
- Testing ideas. Reactions to a design or a plan, early and cheaply.
- Building trust. Customers like being heard.
Calls are not a substitute for data, and they are not a place for selling. Decide which kind of conversation you want before you write.
Pick the right people
Not everyone is a good candidate.
| Good candidates | Avoid |
|---|---|
| People who recently used the feature you are studying | Someone in the middle of an unresolved problem |
| Customers who contacted support and were helped | Anyone who just had a bad experience, unless the call is to repair it |
| A mix: new, long-term and one who churned | Only your friendliest users |
| People in the role you are designing for | People who cannot decide or influence anything |
Look at your support history before choosing. Someone who wrote a thoughtful bug report or a detailed feature request is already telling you they have views. See handling feature requests by email and getting reproducible bug reports.
Ask a small number at a time. Five conversations teach you more than fifty surveys, and you can handle the follow-up.
Check you may email them
Before sending, make sure the request is appropriate.
- Existing customers you have an ongoing relationship with can usually be contacted about the service they use. Keep it relevant and short.
- People who opted out of marketing mail should not receive a research invitation framed as marketing. Respect their choice.
- Prospects and strangers are a different matter. See cold email basics for consent and identity rules, and ask a lawyer if you operate in several countries.
- Offer an easy way out. Unsubscribe pages that do not annoy people apply to any bulk or repeated asks.
Send from a real person at your company, not a no-reply address.
Write the request
A good request is short, specific and easy to say yes or no to. It has five parts:
- Who you are, in one line.
- Why them, specifically. Mention something they did.
- What you want: a call of a stated length, about a stated topic.
- What is in it for them: be honest. A thank-you, early access or simply a chance to shape the product.
- How to say yes: a booking link or two proposed times, and a plain way to decline.
An example:
Subject: 20 minutes on how you use shared mailboxes?
Hi Priya,
I'm Sam, I run support at Acme. I noticed you set up three shared
mailboxes last month, which is more than most teams do, and I'd like
to understand how you use them.
Could we talk for 20 minutes this week or next? I'd mostly listen: how
your team handles email today and what gets in the way. I'm not selling
anything. As a thank-you I'll give you a year of the Team plan free
(not conditional on what you say).
You can pick a time here: [booking link]. If this is not a good moment,
no problem at all, just say so and I won't ask again.
Thanks,
SamGet the subject line right
- Be specific: "20 minutes on how you use shared mailboxes?" beats "Quick chat?".
- Say the length.
- Avoid urgency tricks and fake "Re:" prefixes.
- Keep it under about 60 characters.
Make saying yes easy
- Offer a booking link and also two or three specific times, with the time zone. See handling meeting requests in a shared inbox for ideas on reducing back-and-forth.
- Allow different formats: video, phone or even a written reply to three questions for people who dislike calls.
- Keep it short. 20 or 30 minutes. Stick to it.
- Be flexible about timing. Offer early mornings and late afternoons in their zone.
- Write plainly. If your customer reads English as a second language, use clear sentences. See support email in plain English.
Follow up once
If there is no reply after about a week, send one short reminder. Then stop.
Hi Priya, just a quick note in case my last message got buried. If a
call is not possible, no worries, and I won't ask again. Thanks either
way, Sam.A second reminder starts to feel like pressure, and it makes the next request harder.
Reward their time
People are giving you time, so respect it.
- Offer something fair: credit, a gift card where allowed, early access or a donation to a cause they choose. Say what it is up front and give it regardless of what they say.
- Do not make it conditional on praise.
- Follow the tax and gift rules in your country if you give money or gifts.
- Thank them the same day, by email, and say what you learned.
Run the call well
- Start by explaining the purpose and asking permission to take notes or record.
- Ask about their goals and what they did last time, not what they think they would do.
- Listen more than you talk. Silence is fine.
- Do not sell or defend. If they criticise the product, thank them and ask for an example.
- End on time.
After the call
- Send a thank-you within a day, with the reward if you promised one.
- Share what changed, later, if something does. "You mentioned X. We shipped Y." This builds loyalty and makes the next request easier.
- Record notes in one place, tag them by topic and look for patterns across calls.
- Keep their data safe. Store notes and recordings securely and delete them when no longer needed.
- Follow up on any support issue they raised, so the conversation does not become a way to avoid fixing it.
Common mistakes
- Sending a template to hundreds of people at once.
- Hiding a sales pitch inside a research request.
- Asking for an hour.
- Asking someone who has an open problem, without addressing it first.
- Promising a reward and forgetting it.
- Never sharing what you did with the feedback.
Key takeaways
- A short call with a real customer teaches what surveys and dashboards cannot.
- Choose a few relevant people, respect opt-outs and write a specific, honest, short request.
- Make it easy to say yes or no, follow up once and then stop.
- Reward their time fairly and thank them straight away.
- Share what you learned and what changed.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
