Turn live Q&A transcripts into standalone social posts

Extract raw speaker answers from live event transcripts and turn them into three standalone social formats. Use this after webinars, AMAs, or streams to repurpose spoken advice.

Prompt

Prompt
Act as a social media copywriter. Review the raw Q&A transcript excerpt pasted below and extract the single most valuable answer to transform into three distinct social media post formats.

Follow these rules:
- Format 1: A narrative LinkedIn post (under 175 words) focused on a practical lesson with line breaks for readability.
- Format 2: A punchy 4-part X thread summarizing the core concept with zero filler words.
- Format 3: A brief quote-card graphic concept with an accompanying 40-word community caption.
- Strip out spoken verbal tics (like, you know, um, kind of) and tighten sentences without altering the original meaning.
- Never invent statistics or examples not present in the transcript.

Output format:
Present each format clearly under its own header: 'Format 1: LinkedIn Narrative', 'Format 2: X Micro-Thread', and 'Format 3: Quote Card & Caption'.

Here is the transcript excerpt:

Example output

Example for: transcript answer discussing how founders should hire their first customer support lead

Format 1: LinkedIn Narrative

Most founders hire support reps to clear their inbox.

That is a mistake.

Your first customer support hire is not an administrative shield. They are your fastest product feedback engine.

When we hired our first support lead at 200 customers, we changed the job description:

  • 50% answering tickets within 15 minutes.
  • 50% categorizing why the ticket occurred in the first place.

Every Friday, that rep presented the top three friction points directly to engineering. If five users asked how to reset a password, we did not write a better support macro—we redesigned the login flow.

Stop hiring support to manage problems.

Hire support to eliminate them.

Format 2: X Micro-Thread

1/ Stop hiring customer support just to clear tickets. Your first support rep is your most important product researcher.

2/ The playbook: split their role 50/50. Half their time goes to solving user issues. The other half goes to tagging the root cause in your backlog.

3/ Every Friday, bring support and engineering into one room. If ten users stumble over the same button, fix the UI instead of writing a help desk article.

4/ The best support teams do not boast about high ticket volume. They boast about bugs that never happen twice.

Format 3: Quote Card & Caption
  • Graphic visual: Dark slate background, bold white typography: 'Do not hire customer support to manage tickets. Hire them to help engineering eliminate the root problem.'
  • Caption: When was the last time your product team sat in your support queue? Your inbox holds your best product roadmap if you take time to categorize the noise. What is your team's top support inquiry this month?
Written by AI from this prompt. Your results will vary.

Paste your raw live event transcript or interview audio export right after this prompt in ChatGPT, Claude, or Gemini. As a follow-up, ask the model to draft two poll questions based on the topic to keep conversation going.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Social Media