Tech Podcast and Webinar Audio Agent
Produces podcast episodes, webinar recordings and their transcripts.
- Industry
- IT Company
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Product Marketing Manager
- Code
- CON-03
It produces transcripts, show notes, chapter markers and edit points for the company's technology podcast and recorded webinars, where guests are often client CTOs and partner engineers. It flags guests without a signed release, remarks about a client's systems, incidents or contract terms that must be cut, and any forward-looking roadmap statement before the episode is queued for publishing.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: whether each guest's employer is a client or prospect, the account owner, and any reference or media permission on the account..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Product Marketing Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it updates the episode task with the show notes, edit points and clearance, ready for publishing. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The audio playbook: episode formats, guest release forms, the roadmap disclosure policy, client-confidentiality rules and the technical glossary for transcription.
Reads from
the CRM: whether each guest's employer is a client or prospect, the account owner, and any reference or media permission on the account.
Acts in
the project management tool: it updates the episode task with the show notes, edit points and clearance, ready for publishing.
Hands back
An object with transcript_ref, show_notes (markdown), chapters (a list of start mm:ss and title), edit_points (a list of start, end and reason), clearance (a list of each guest with release status and client-approval status) and listing (an object with title, description and tags).
Asks a person when
A guest's release is missing, a client guest's segment mentions their systems or incidents, or a roadmap statement is kept in the episode.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest episode (minutes) | 40 | Edit points bring the episode under this length. |
| Chapter marker every (minutes) | 6 | Add a chapter marker at least this often, at topic changes. |
| Every guest needs a signed release | On | When on, an episode with a guest whose release is not signed is never queued. |
| Cut unapproved roadmap statements | On | When on, a dated or committed statement about an unreleased feature is marked for cut unless the roadmap disclosure policy allows it. |
| Check the transcript for | names, figures and technical terms | What the transcript is checked against the glossary and guest list for. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- When on is true, an episode with any guest whose release is not signed is held, never queued.
- Mark for cut any remark naming a client's systems, security incidents, outages, contract value or SLA terms unless that client is the guest and has approved it.
- When on is true, mark for cut any committed date or promise for an unreleased feature.
- Bring the episode under 40 minutes and add a chapter marker at least every 6 minutes at topic changes.
- Check the transcript for names, figures and technical terms against the glossary and guest list, spelling product, framework and standard names exactly.
See the Tech Podcast and Webinar Audio Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.