How to Get on Customer Experience Podcasts

To get on a customer experience podcast, pitch one CX decision you handled directly and use the route the show publishes. Match the idea to recent episodes and state your evidence and trade-offs. Keep editorial applications separate from general contact. Treat invitations separately too, and do not combine sponsorship with paid media. A guest interview alone does not prove that cold pitches are welcome.

Start with a customer decision, not a CX biography

"Customer experience leader" describes a role. It gives a producer little reason to book a conversation. A workable episode begins with the customer problem and the decision behind it, plus the person who can explain what happened under questioning.

Good premises often come from disputed or imperfect work. You might explain why a support policy created more customer effort and how research overturned an internal assumption, including where an automation needed a human handoff. A useful story can also cover ownership between service and customer success alongside the connection between employee conditions and repeat failures. It can instead focus on a measurement problem that never produced clean attribution.

Write the premise before building a show list. Name the intended listener and the decision. State your direct role and the constraint, then identify the evidence you may discuss publicly. Add one trade-off. A producer can test that proposal. "I want to discuss customer centricity" offers no comparable shape.

Build a short list from current first-party sources

The Convokast podcast directory and management podcast category can surface candidates. Open each show's own site and feed to confirm its audience, recent subjects, format and submission route.

Current first-party sources show several access states across CX podcasts:

Read the source as well as checking its status code. An active feed can prove that outside experts appear, while the site may still provide no permission for unsolicited proposals. An old feed can teach you how a host framed interviews without supporting current outreach.

Keep every access route in its own column

Use separate fields in your research sheet for explicit application, stated producer contact, invitation-only, and general contact. Keep sponsorship, paid media, interview evidence, and historical interview evidence in their own fields too.

An explicit application asks prospective guests to submit a show-specific form. Yanique Grant's podcast provides that route and says its team reviews requests for audience fit. Doing CX Right lets candidates who meet its editorial criteria submit for consideration. Neither page promises acceptance merely because someone completes the form.

A stated producer contact only counts when the show identifies that address or person for guest proposals. The same podcast names one inbox for guest requests and follow-ups. It also uses that inbox for sponsorship and other show matters. A company-wide contact page has a broader job. Sales, support, press, speaker, and partnership forms should remain labeled as general contact unless the podcast directs applicants there.

Invitation-only also needs direct evidence. The absence of a form does not prove that a show books solely by invitation. It leaves the public submission status unconfirmed. If a producer privately invites an idea, save the message and follow the scope given. An invitation to propose a topic still does not promise recording or publication.

Sponsorship and paid media belong in commercial fields. The Yanique Grant podcast describes optional sponsorship for extra promotion after presenting its application process. Doing CX Right presents editorial consideration for qualified candidates and paid media collaborations for people outside those criteria. Ask for written scope before buying anything. Confirm labeling and editorial control. Check distribution and cancellation terms, then establish what the fee guarantees.

The guest-access guide gives a fuller test for these route labels. Apply the label supported by the publisher, even when a more optimistic label would make the outreach list look larger.

Read recent episodes for the editorial pattern

A show's title cannot settle fit. Read several current episode pages or feed entries and note the listener and guest role. Record the problem and level of detail too. Look for whether the host prefers operating cases or research. Then distinguish leadership stories from tactical methods. Note broad commentary separately.

That podcast currently covers service leadership and human support. Its subjects also include customer success and organizational change, along with the boundary between automation and human judgment. Doing CX Right emphasizes customer and employee experience. It also covers leadership, culture, and results. CX Insider spans enterprise settings and contact centers. Its episodes also address technology and sector-specific practice. Customer Confidential connects loyalty and customer behavior to business decisions.

Use audience overlap as the filter. A customer support automation story may share vocabulary with every show on the list, yet only some serve leaders making that decision. Write one sentence that connects your proposed lesson to a pattern in the show's current work. If the sentence could accompany any business podcast pitch, the research has not reached the useful detail.

Historical episodes require a different treatment. The CX Leader Podcast and The Customer Experience Podcast preserve interviews with CX practitioners, but their first-party feeds show older runs rather than current booking activity. Those archives can help with topic research and host-style analysis. Keep them out of an active outreach queue until a first-party restart or new submission instruction appears.

Give the producer a premise they can question

Open the proposal with the customer problem and the decision. Then state your role and the constraint. Explain the evidence available and the lesson that fits this audience. Keep the biography to details that establish authority on that subject.

Evidence may include a public case or approved research. It may instead be a process document you can describe or a result your organization has cleared for discussion. Explain what each item supports. Separate documented facts from your interpretation. If attribution remained messy, say so rather than assigning the whole outcome to one CX change.

Include the trade-off or failed attempt. A new support policy may have reduced one kind of effort while shifting work to another team. A self-service change may have helped routine cases and frustrated customers with unusual needs. Those limits give the host questions and help the proposal avoid sounding like a product demonstration.

Disclose commercial interests in the first message. A software founder or consultant can bring useful knowledge, as can an agency leader or author, but the producer should know what the guest sells and how that relationship touches the story. Customer names and employee examples need permission before outreach. Internal figures and client results do too.

Submit once and prepare for the promised conversation

Follow the published application instructions. Answer the fields directly and adapt the premise to the show. Do not send the same request through the application, company contact form, sponsor, and personal social accounts. Repetition cannot repair weak fit.

For interview-evidence-only shows, seek a relevant introduction or monitor the official page for a route. A past guest who knows your work can ask whether the topic would help the audience. That introduction creates permission for a conversation, not a claim on the calendar.

If booked, prepare the sequence of events and rejected options. Identify the affected teams and evidence, then set disclosure boundaries. Bring examples rather than rehearsed speeches. The host may find the most useful part in a constraint you treated as background. Stay inside what you can support and what your organization has approved.

When your premise and evidence are ready, confirm the route, then use the podcast pitch generator to draft a concise customer experience proposal around one decision.