Table of Contents
- Before you send anything
- Step 1 — Build the question set
- Step 2 — Send the invite (no calendar link)
- Step 3 — Let them answer on their phone
- Step 4 — Remind once, then stop
- Step 5 — Turn answers into a draft
- Step 6 — Get permission before you publish
- What "done" looks like
- Where people get stuck
- Doing this with Testimonial
- Wrapping up
Image URL
Do not index
Do not index
AI summary
Run case‑study interviews asynchronously by sending six well‑crafted questions via email or a form, allowing typed or voice answers without a calendar link; follow up with a single reminder, draft the case study using the respondents’ exact words, obtain separate permissions for name, title, company and image, and then publish—this streamlined process eliminates scheduling calls, speeds up collection, and maintains legal compliance.
Title
How to Run a Case Study Interview Without Scheduling a Call
Date
Description
A case study interview does not need a Zoom. Build six questions, send them with no calendar link, collect typed or voice answers, remind once, and write from what they said.
Status
In progress
Current Column
In the queue
Person
Writer
They said yes.
You sent three time slots.
None of them stuck.
That is not a writing problem. It is a scheduling problem wearing an interview costume.
A case study interview is six questions that return a before, an after, and a number a stranger can check. You do not need a Zoom for that. You need answers — typed or spoken on their phone, on a Thursday night, without finding an hour that works for both of you.
This page is the how-to. For the rest of the system — pick, write, approve, use — start with how to run case studies without the interview call. Here you only run the interview itself.
Before you send anything
Three decisions. Make them once, then stop fussing.
- One name. Someone who already talked — a support thread, a QBR, a tweet, a testimonial in the inbox. You are asking them to extend something they already said, not invent a narrative from a blank calendar invite.
- Six questions, not fifteen. Fifteen turns a favour into homework. People who said yes to a case study did not say yes to a survey.
- Type, voice, or either. Voice is worth offering. People say things out loud they will not type. You still have to trim it — they will not.
You do not need a product for any of this. An email with six questions is enough. A Google Form is enough. The steps below work either way.
Step 1 — Build the question set
Each question is built to return a specific kind of sentence. If the pairing is "a mood", cut it.
These are the same six from our guide to customer case studies. Do not invent a second set. The short-form four that produce a publishable testimonial live on questions to ask. Do not send both.
1. Who are you, and what do you actually do day to day?
Designed to return: a name, a role, and a sentence a stranger can place. "[Name], marketing" is not enough. "[Name], the person who owns outbound at a 12-person agency" is.
2. What were you doing about [task] before [Product], and what was broken about it?
Designed to return: the before. Without it the rest is praise. Name the task for them or they will write "things were fine."
3. What almost stopped you picking us?
Designed to return: the objection a prospect is having right now. Put that sentence next to the pricing button.
4. What does [task] look like now, on a normal Tuesday?
Designed to return: a workflow, a number of tabs, a meeting that disappeared. Not "how has it helped."
5. What has it got you — and if you can put a number on it, do?
Designed to return: time, cost, volume, errors. If they cannot share a number, a named task that stopped happening is the honest substitute. Do not invent one for them, and do not write one in after.
6. Who should skip this?
Designed to return: the limitation. I would rather publish "skip this if you need [X]" than a third "highly recommend."
Save the set. Reuse it. The next customer gets the same six with their name swapped in — not a fresh brainstorm every time.
Step 2 — Send the invite (no calendar link)
Do not send Calendly. A calendar link turns a yes into a meeting. Send the questions.
The social half of the ask — how well you know them, how not to make it weird — is how to ask for a testimonial. The wording below is just the vehicle.
Subject: six questions, no call — whenever you have twenty minutes
Hi [Name] —
[The specific moment: the launch, the ticket, the thing they said in Slack.]
Would you answer six questions I can turn into a customer case study?
No call. Type or talk, on your phone is fine. Skip any number you cannot share.
If you'd rather I draft from what you already told me and you edit, say so.
Either works.
[Link, or: just reply to this.]
— [Your name]"I'll draft, you edit" is the escape hatch. Some people will not fill a form and will happily redline a paragraph. That still beats a cancelled Zoom.
Do not attach a 40-minute deck about "the case study process". You are asking for twenty minutes of answers, not onboarding them into a programme.
Step 3 — Let them answer on their phone
They open the link — or the email — on a commute, after dinner, between meetings. That is the point.
If they type: leave room. A one-line box on question 4 returns "it saved time." A multi-line box returns the Tuesday. Do not require every field. A blank on question 5 is better than a number they invent to get past the form.
If they talk: one prompt at a time. A two-minute voice note on question 4 is often the whole story. Keep the original audio if you can; transcription is a drafting aid, not the source of truth. They will ramble. You trim.
If they disappear mid-way: that is normal. Auto-save and resume (if your form supports it) beats a second "start over" email that makes them feel behind.
The manual path: paste the six into an email and ask them to reply under each. Or a Google Form. Or a Notion page you share. The answers are the asset. The tool is optional.
Step 4 — Remind once, then stop
A yes that never books is the call-era failure mode. Async has its twin: a link that sits.
Send one reminder. Something like: "Still happy to take the six questions whenever — no rush, and no call." Then stop. A second reminder starts to sound like nagging, and the yes goes cold the same way a twice-moved Zoom does.
I do not have a platform number for "remind after N days," so I will not invent one. Pick a gap that matches how your customers actually work — a week is a reasonable default for a favour, not a law.
If they still do not answer, move to the next name. Do not salvage a cold yes with a "quick 15-minute call." That is how you reintroduce the calendar problem you just removed.
Step 5 — Turn answers into a draft
Do not open a blank doc and "find the narrative". You already have the narrative. Map the answers onto seven slots:
- Headline with an outcome. A number, or a named change, in one line.
- Who. Name, role, company, size if they gave it.
- Before. Question 2, almost verbatim.
- Why you. Question 3.
- What changed. Question 4 — Tuesday, not "the platform".
- The number, or the proxy. Question 5. If they skipped it, say so in the draft you send back.
- The quote. Usually a sentence from 4 or 6, in their words.
If an answer is thin, one written follow-up. Not a new call. "You said it saved time — can you say what that looks like on a Tuesday?" If they still shrug, cut that slot. A case study with six honest pieces beats seven with one you guessed.
For how a sales team actually uses the finished page — skimmed on a phone, pasted into an email — see case study formats.
We do not publish async completion rates or scheduled-call show rates here. We do not have those numbers, and I will not invent them. The test is simpler: did this name produce answers you can turn into a draft without a calendar?
Step 6 — Get permission before you publish
A completed interview is not consent to put their name on the homepage.
Get permission in writing. Be specific about where it will appear — site, sales deck, and paid ads are different questions. Ask separately for the name, the job title, the company, and the face. Plenty of people will give you the words and not the photo.
If anything changed hands — a discount, a free month, a gift card — the connection has to be disclosed. That is a legal requirement in several jurisdictions, not a nicety. The legal side of testimonials is the primer. Check your own jurisdiction rather than treating that page as advice.
If they will not let you name the company, you do not have a case study. You have an anecdote. I would not publish it as one.
What "done" looks like
- You have attributed answers for six questions (or five honest ones and one blank you owned).
- The draft uses their words for the before, the Tuesday, and the quote.
- An approval email is out — or already back — covering name, title, company, and face as separate yeses.
- Nobody's calendar was involved.
That is a finished interview. Writing and publishing are the next jobs, not this one.
Where people get stuck
Fifteen questions. You turned a favour into a survey. Cut to six. If one answer is thin, rewrite that question once — do not add twelve more.
Calendly in the invite. You asked for a meeting. They have to find an hour. Remove the link. Send the questions.
Inventing the metric. They skipped question 5. You wrote "approximately 3x" because it felt true. Delete it. Use the named proxy they actually said, or leave the slot empty.
Calling after a thin typed answer. You reintroduced the calendar. Send one written follow-up. Then live with what you have, or pick the next name.
Where async breaks on purpose. You cannot ask the third follow-up in the room. Flagship logos whose legal team wants a conversation, and stories that are a 40-minute mess, still earn a call. Not the other seven names on the list.
Doing this with Testimonial
The six questions and the email above work without us. You do not need a product for the interview.
What async case-study interviews change is the gap between "they said yes" and "you have answers".
You build a question set — 5–10 questions, saved as a reusable template — and send each customer their own link. No signup. They type, or they talk; voice is transcribed with ElevenLabs Scribe and dropped into the box as editable text. Original audio stays for playback. Answers arrive pre-attributed in the inbox. You can resend, remind, or revoke from one place.
If someone scores 9 or 10 on an NPS survey, they can get the case-study invite automatically. That is a routing rule, not a new ask you have to remember.
Case Study is on Ultimate +. As of October 2026 that is $95/month/space, or $1,140 a year. Ultimate and Ultimate + are priced per space. The plans and pricing page is the live list.
Where it breaks, including for us. The builder will let you write ten questions. Completion falls off because you turned a favour into homework. I would put six and stop. The product will not stop you. A reminder helps a link that sits; it does not create time they do not have. And nothing in the tool clears legal for you — approval is still a human email.
If you have one customer, they will hop on a Zoom, and you are happy to write from a transcript, do the Zoom. The tool earns its place when the backlog is eight names and you cannot keep booking around them.
Wrapping up
Six questions. No call. One reminder. Write from the answers. Get permission for the name, the company, and the face as separate yeses.
If you only do one thing this week, pick the next customer who already said something nice, and send them the six questions with no calendar link.
Stuck on which of the six will come back empty for your product? Reply with the draft — I will tell you which one to cut.
Written by
