A useful podcast call to action gives listeners a specific task, a destination, and a reason to respond. “Tell us what you think” leaves too much unstated. “What would you ask our next guest? Send a question through the link in these episode notes” gives them somewhere to start.
Decide what a successful response looks like
A follow, a poll vote, and a usable recording are different outcomes. If you need a listener-question segment, measure relevant questions—not follows. If you need a story in someone’s own voice, a vote will not supply it.
GOV.UK’s content-design guidance (opens in a new tab) starts with the user’s task. Apply that principle by making the next step clear. One primary request is a useful editorial discipline, not a proven conversion rule.
Build the invitation from four parts
Include a specific prompt, a response format, a destination, and an expectation. For a fictional episode about changing careers:
What surprised you most in your first week at a new job? Leave a voice message of up to one minute at [URL]. We may play selected stories in our follow-up episode; tell us what name you would like us to use.
Shorten the on-air version if necessary, but keep the duration, intended use, and any promise of a reply on the destination page.
Make the page agree with the spoken invitation
A two-minute invitation cannot work with a one-minute recorder. whatayarn’s recording settings allow one minute on Free and up to ten on Creator; check the configured page before publishing.
Follow W3C’s labels and instructions guidance (opens in a new tab): explain required inputs and constraints before someone starts. Offer a written route where your process permits it, with the same clarity about publication.
Choose the response channel before the wording
- Voice suits stories where the listener’s own telling matters. Allow time for listening, selection, and file handling.
- Comments suit short questions and discussion. Spotify’s current documentation (opens in a new tab) covers replies, reactions, and moderation; comments should not be treated as private messages.
- Polls suit a limited choice. Spotify permits one per episode, with two to seven answers and optional multiple selection; its poll guide (opens in a new tab) explains the mobile-app experience.
- Email or a form suits corrections, written detail, or attachments. Explain who reads submissions and ask only for information you will use.
Name the platform when an action is Spotify-only, or offer a destination for people using other listening apps.
24 podcast CTA examples you can copy
Replace placeholders and check every date, URL, limit, and promise. For audio submissions, explain intended publication on the destination page and discourage unnecessary private details. These are adaptable scripts, not performance benchmarks.
Listener questions
- A question for the next guest: “What would you ask [guest] about [topic]? Send one question at [URL] by [date]. We will choose a few for the interview.”
- The confusing step: “Which part of [process] still feels unclear? Leave a short voice question through the link in these episode notes. We may answer it in next week’s Q&A.”
- A practical follow-up: “Are you trying this yourself? Tell us where you got stuck at [URL]. One specific situation will help us plan a useful follow-up.”
- A recurring question segment: “Our next listener-question episode is about [topic]. Send a question of up to one minute at [URL], and tell us what name to use if we play it.”
Listener stories
- The first attempt: “What happened the first time you tried [activity]? Send a one-minute story at [URL]. We may include selected recordings in our next episode.”
- A moment that changed your mind: “Was there a moment that changed how you think about [topic]? Tell us what happened at [URL]. Please leave out other people’s private details.”
- A small lesson: “What’s one thing you wish you had known before [experience]? Leave a short voice message at [URL]. We are collecting lessons for a follow-up.”
- A specific memory: “Can you remember your first [relevant experience]? Share the moment, rather than your whole history, at [URL]. Tell us whether we can use your first name on air.”
Responses and disagreement
- A different experience: “Did today’s advice match your experience? Tell us one way it differed at [URL]. We will review responses before our follow-up episode.”
- The missing perspective: “Whose perspective was missing from this conversation? Send your suggestion and why it matters at [URL]. We will use the responses when planning future guests.”
- A respectful challenge: “Which argument would you challenge, and why? Leave a short response at [URL]. Focus on the idea rather than the person.”
- A real-world example: “Have you seen this work differently in practice? Share one example at [URL]. Please tell us if you are happy for us to discuss it on the show.”
Choosing what comes next
- A platform poll: “Listening on Spotify? Vote in this episode’s poll for the topic you want next. We will share the result in [episode or update].”
- A written topic suggestion: “What should we explain next about [subject]? Add one suggestion in this episode’s Spotify comments. We will read them while planning the next series.”
- A choice through your own page: “Would you rather hear about [A] or [B] next? Choose one at [URL] by [date]. That will help us set the next episode’s focus.”
- A guest question before booking: “Who could help us understand [problem]? Suggest a guest at [URL] and tell us what you would ask them. We cannot promise a booking, but we will review the ideas.”
Following, sharing, and reviews
- Follow a continuing series: “The next part of this story is out on [day]. Follow the show in your podcast app if you want to find it when it is released.”
- Share with a relevant person: “Know someone working through [situation]? Send them this episode using your app’s share option. It may be a useful starting point for your conversation.”
- Ask for a specific review: “If this show has helped you, consider leaving an honest review on Apple Podcasts. Tell a new listener what kind of episode they should start with.”
- Save a practical episode: “If you are not ready to try this today, save or download the episode in your app so you can return to the steps when you need them.”
Written feedback and corrections
- Correct a factual detail: “Spotted a detail we should check? Send the episode number, the point in question, and a source to [email or URL]. We will review it.”
- Choose a useful level of detail: “Was this explanation too basic, too detailed, or about right? Tell us at [URL], with one example of what you wanted more of.”
- Give feedback without an audio recording: “Prefer to write your question? Use the text option at [URL]. We may read selected questions on the show under the name you choose.”
- Respond to an experiment: “We tried a different format today. Tell us at [URL] which part you would keep and which you would change. We will read the feedback before recording the next one.”
Ask for honest reviews, not an invented ranking boost. Apple’s chart guidance (opens in a new tab) says ratings and reviews are not factors in its Top Shows and Trending Episodes ranking algorithm.
Adapt the invitation to where someone encounters it
Spotify’s audience-engagement guide (opens in a new tab) suggests tying invitations to the episode and mentioning them in intros or outros. That is platform advice, not proof of a universally best timestamp.
In the introduction
Give listeners something to notice:
As you listen, think about one thing you would ask our guest. The question link is in these episode notes.
After the relevant discussion
Ask while the context is clear:
We have heard one version of that experience. What happened when you tried it? Share a short story at [URL].
In the outro
Restate the task and destination:
Before next week’s episode, send us one question about [topic]. Use the question link in these episode notes; we may play selected recordings.
If there is a deadline, state it and update the page when collection closes.
In show notes and social posts
Use descriptive links such as “Send a question for our next guest,” with the prompt nearby. Our sharing guide covers placing collection links where listeners encounter the show.
Keep a clickable link alongside any QR code: someone already reading on their phone needs a usable route.
Measure the response you actually asked for
Track completed responses, relevant answers, and usable contributions separately. If your tracking supports a consistent denominator, calculate page completion as submissions divided by eligible page visits.
Apple’s listener analytics (opens in a new tab) measure aggregated Apple Podcasts listening—not your entire audience or proof that someone heard the CTA. Keep listening and submission data distinct unless you can reliably connect them.
A worked example, not a benchmark
A fictional seven-day campaign receives 80 eligible page visits, eight submissions, and five usable contributions. That is a 10% page submission rate and a 62.5% usable share of submissions. Neither is a target or prediction.
If the episode also had 1,000 downloads, report that separately. Downloads do not establish how many people heard the invitation. At small volumes, review the messages alongside percentages; one extra reply can change a rate substantially.
Review one change at a time and report back
Record the prompt, placement, channel, observation window, and useful replies. Changing everything at once makes differences hard to interpret; even one-change episode comparisons remain observational because topics and audiences vary.
Investigate friction rather than assuming a cause: visits without submissions could reflect an unclear task or a technical problem. Honour the publication expectations you gave listeners, and only promise replies or on-air features you can deliver.
Try the workflow with one episode
Choose a script, replace its placeholders, and submit a test from your phone. Check that the page’s limits, fields, and completion message match the invitation. For audio contributions, create a whatayarn page, test it, then publish the prompt and review replies after the stated window.