Weekly customer feedback digest from tl;dv to Slack and Google Sheets

Every Friday at 4pm in my local timezone, run an agent that synthesizes the past week of customer calls from tl;dv into a single product feedback digest. Use a cron trigger on a weekly Friday 4pm schedule.

Step 1: Call tl;dv List Meetings to pull every meeting from the last seven days. Filter out internal meetings using the title and template, so anything that looks like a standup, retro, planning, all-hands, 1:1, or interview is skipped. Keep only customer-facing calls (discovery, demo, onboarding, success check-in, renewal, churn, win-back, support escalation, etc.).

Step 2: For each remaining meeting, call tl;dv Get Meeting Notes to retrieve the structured AI notes (topics plus markdown summary). Capture the meeting title, date, attendees or customer name, the meeting link, and the notes.

Step 3: Cluster the notes across all meetings into recurring themes. Default buckets are: feature requests, complaints and bugs, churn risks, competitor mentions, and pricing pushback. Allow new themes to emerge if multiple customers raised the same topic. For each theme, pick a representative verbatim quote from the notes, list the source meetings (with links), and count the number of distinct customers (not raw mentions) who raised it. Rank themes by distinct-customer count, breaking ties by severity (churn risk and pricing pushback ranked higher).

Step 4: Send the ranked digest to Slack. Use Slack Send a Message to post into the #product-insights channel. The message should include the week range at the top, a ranked list of themes with the count of distinct customers, the representative quote, and links to the source meetings. Use Slack formatting (bold headings, bullet lists). Keep it scannable; if the message is long, post the headline summary in the channel and put the per-theme detail in a thread reply.

Step 5: Append one row per theme to a running Google Sheets tracker so trends accumulate. Use Google Sheets Append Values against a sheet I will configure. Columns: week (ISO week or Friday's date), theme, distinct customer count, severity (low / medium / high), and source meeting links (comma-separated). One row per theme, in the same ranked order as the Slack post.

Other notes: if there are no customer calls in the window, post a short Slack message saying so and skip the spreadsheet write. Make the customer-meeting filter, the Slack channel, the spreadsheet ID and tab name, and the theme buckets easy to edit at the top of the agent instructions so I can tune them later without rewriting the workflow.

Additional information

What does this prompt do?

Pulls every customer-facing meeting from tl;dv from the last seven days and skips internal standups and team syncs.
Reads the AI notes for each call and clusters them into recurring themes like feature requests, complaints, churn risks, competitor mentions, and pricing pushback.
Posts a ranked digest to a Slack channel with a representative quote and meeting links for each theme.
Adds one row per theme to a Google Sheets tracker so you can see how feedback trends shift week over week.

What do I need to use this?

A tl;dv account with customer calls being recorded.
A Slack workspace and a channel where the digest should land, like #product-insights.
A Google account with a spreadsheet you want to use as the running insights tracker.

How can I customize it?

Change the schedule (for example, Monday morning instead of Friday afternoon) or the rolling window (7, 14, or 30 days).
Tune the rules for which meetings count as customer calls, like skipping titles with standup, sync, or 1:1.
Adjust the theme buckets to match how your team thinks about feedback, or add tags like onboarding friction or integration gaps.
Pick the Slack channel that receives the digest and the spreadsheet that captures the long-term trend log.

Frequently asked questions

Will this work if I only record some of my customer calls in tl;dv?

Yes. The agent only looks at meetings that exist in tl;dv. Anything you do not record is simply not included in the digest.

How does the agent know which meetings are customer calls versus internal standups?

It uses the meeting title and the tl;dv template to filter out things like standups, retros, and 1:1s. You can refine the rules in the prompt to match how your team names meetings.

Where do the quotes in the Slack digest come from?

Each theme is paired with a representative line pulled from the structured notes of the calls in that cluster, along with a link back to the source meeting so anyone can verify the context.

Can I send the digest to more than one Slack channel?

Yes. You can ask the agent to post to multiple channels, or to send a richer thread to a product channel and a shorter version to leadership.

Can I track severity or customer segment in the spreadsheet?

Yes. The default tracker logs week, theme, mention count, severity, and source meetings, and you can add columns for plan tier, account size, or owner without rebuilding the workflow.